{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-50178 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2025-50178 is a medium-severity path traversal vulnerability in JuliaWeb GitForge.jl, published on 25 Jun 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-50178 and fix it if it is affected.\n\nWhat it is: CVE-2025-50178 is a medium-severity path traversal vulnerability in JuliaWeb GitForge.jl, published on 25 Jun 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-50178 in the wild and no public exploit code.\n\nAffected product: JuliaWeb GitForge.jl. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-50178/ (Markdown: https://insights.sbomify.com/CVE-2025-50178/index.md)","id":"CVE-2025-50178","markdown":"https://insights.sbomify.com/CVE-2025-50178/index.md","name":"CVE-2025-50178","record":{"aliases":["GHSA-g2xx-229f-3qjm","JLSEC-2025-3"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Julia Git forge library","requires_auth":"none","summary":"Attackers can exploit missing input validation in GitForge.jl to perform path traversal and access unintended API endpoints on GitHub.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":6.6,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:U","version":"4.0"},"cwes":[{"id":"CWE-22","name":"Improper Limitation of a Pathname to a Restricted Directory"},{"id":"CWE-20","name":"Improper Input Validation"}],"description":"GitForge.jl is a unified interface for interacting with Git \"forges.\" Versions prior to 0.4.3 lack input validation for user provided values in certain functions. In the `GitForge.get_repo` function for GitHub, the user can provide any string for the owner and repo fields. These inputs are not validated or safely encoded and are sent directly to the server. This means a user can add path traversal patterns like `../` in the input to access any other endpoints on api.github.com that were not intended. Version 0.4.3 contains a patch for the issue. No known workarounds are available.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"GitForge.jl lacks validation for user provided fields","id":"CVE-2025-50178","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"path_traversal","year":"2025"},"n_packages":0,"n_references":2,"next":{"headline":"Tuleap missing CSRF protection on tracker reports manipulation","id":"CVE-2025-50179"},"packages":[],"prev":{"headline":"Microsoft Message Queuing (MSMQ) Remote Code Execution Vulnerability","id":"CVE-2025-50177"},"products":["GitForge.jl"],"published":"2025-06-25","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-06-25","vendors":["JuliaWeb"]},"summary":"Attackers can exploit missing input validation in GitForge.jl to perform path traversal and access unintended API endpoints on GitHub.","url":"https://insights.sbomify.com/CVE-2025-50178/"}