CVE-2025-58458
BaseFortify
Publication date: 2025-09-03
Last updated on: 2025-11-04
Assigner: Jenkins Project
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| jenkins | git_client | to 6.1.3 (inc) |
| jenkins | git_client | From 6.3.0 (inc) to 6.3.2 (inc) |
| jenkins | git_client | 6.2.0 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-200 | The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. |
| CWE-538 | The product places sensitive information into files or directories that are accessible to actors who are allowed to have access to the files, but not to the sensitive information. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability exists in Jenkins Git client Plugin 6.3.2 and earlier. It occurs because the Git URL field form validation behaves differently depending on whether a specified file path exists on the Jenkins controller when using the amazon-s3 protocol with JGit. This difference allows attackers who have Overall/Read permission to determine if a specific file path exists on the Jenkins controller's file system.
How can this vulnerability impact me? :
An attacker with Overall/Read permission can exploit this vulnerability to check for the existence of arbitrary file paths on the Jenkins controller file system. This can lead to information disclosure about the file system structure, which may aid further attacks or reconnaissance.