{"answers":{"affected":"2 open source packages ship an affected version, including org.jenkins-ci.plugins:git-client. It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-58458 in the wild and no public exploit code.","fix":"Upgrade org.jenkins-ci.plugins:git-client to 6.3.3 or later.","what":"CVE-2025-58458 is a medium-severity vulnerability in Jenkins Git client Plugin, published on 3 Sep 2025. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-58458 and fix it if it is affected.\n\nWhat it is: CVE-2025-58458 is a medium-severity vulnerability in Jenkins Git client Plugin, published on 3 Sep 2025. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-58458 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- org.jenkins-ci.plugins:git-client (Maven): affected all versions; fixed in 6.3.3\n- org.jenkins-ci.plugins:git-client (Maven): affected all versions; fixed in 6.3.3\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-58458/ (Markdown: https://insights.sbomify.com/CVE-2025-58458/index.md)","id":"CVE-2025-58458","markdown":"https://insights.sbomify.com/CVE-2025-58458/index.md","name":"CVE-2025-58458","record":{"aliases":["GHSA-g2pq-9jr7-w6gv"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Jenkins Git client Plugin","requires_auth":"low_privilege","summary":"Attackers with read permissions can determine if specific file paths exist on the Jenkins controller via Git URL validation responses.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"jenkins","cpe":[{"product":"git_client","vendor":"jenkins"}],"cvss":{"score":4.3,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-538","name":"Insertion of Sensitive Information into Externally-Accessible File or Directory"},{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"In Jenkins Git client Plugin 6.3.2 and earlier, except 6.1.4 and 6.2.1, Git URL field form validation responses differ based on whether the specified file path exists on the controller when specifying `amazon-s3` protocol for use with JGit, allowing attackers with Overall/Read permission to check for the existence of an attacker-specified file path on the Jenkins controller file system.","ecosystems":["Maven"],"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":"Jenkins Git client Plugin file system information disclosure vulnerability","id":"CVE-2025-58458","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"information_disclosure","year":"2025"},"n_packages":2,"n_references":1,"next":{"headline":"Jenkins global-build-stats Plugin missing permission check can result in graph IDs being enumerated","id":"CVE-2025-58459"},"packages":[{"ecosystem":"Maven","fixed":["6.3.3"],"introduced":["0"],"last_affected":[],"package":"org.jenkins-ci.plugins:git-client","purl":null,"source":"GHSA-g2pq-9jr7-w6gv"},{"ecosystem":"Maven","fixed":["6.3.3"],"introduced":["0"],"last_affected":[],"package":"org.jenkins-ci.plugins:git-client","purl":"pkg:maven/org.jenkins-ci.plugins/git-client","source":"GHSA-g2pq-9jr7-w6gv"}],"prev":{"headline":"Apache ZooKeeper: Insufficient Permission Check in AdminServer Snapshot/Restore Commands","id":"CVE-2025-58457"},"products":["Jenkins Git client Plugin"],"published":"2025-09-03","related":[{"cvss_score":8.8,"headline":"Improper Neutralization of Special Elements used in an OS Command in Jenkins Git Client Plugin","id":"CVE-2019-10392","kev_date_added":null,"published":"2019-09-12"},{"cvss_score":8.1,"headline":"Jenkins Git client plugin 3.11.0 does not perform SSH host key verification","id":"CVE-2022-36881","kev_date_added":null,"published":"2022-07-27"},{"cvss_score":5,"headline":"Jenkins Git client Plugin has an OS command injection vulnerability on agents","id":"CVE-2026-57282","kev_date_added":null,"published":"2026-06-24"},{"cvss_score":5,"headline":"Jenkins Git client Plugin has an OS command injection vulnerability on agents in Git client Plugin","id":"CVE-2025-67640","kev_date_added":null,"published":"2025-12-10"},{"cvss_score":3.3,"headline":"Insecure temporary file usage in Jenkins Git Client Plugin","id":"CVE-2017-1000242","kev_date_added":null,"published":"2017-11-01"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-11-04","vendors":["Jenkins Project"]},"summary":"Attackers with read permissions can determine if specific file paths exist on the Jenkins controller via Git URL validation responses.","url":"https://insights.sbomify.com/CVE-2025-58458/"}