SCM data disclosure via controller-local checkout
Published May 17, 2022 · Updated Aug 3, 2024
Information disclosure in Jenkins Git Plugin 4.11.1 and earlier allows remote attackers to obtain limited SCM data. GitSCM accepts local paths and file URLs for controller-side checkouts without rejecting repositories on the controller file system. The attacker must be able to configure a pipeline, and exposure is limited to information obtainable from other projects' SCM contents.
Summary
What happened
Information disclosure in Jenkins Git Plugin 4.11.1 and earlier allows remote attackers to obtain limited SCM data. GitSCM accepts local paths and file URLs for controller-side checkouts without rejecting repositories on the controller file system. The attacker must be able to configure a pipeline, and exposure is limited to information obtainable from other projects' SCM contents.
The record
- CVE
- CVE-2022-30947
- Published
- May 17, 2022
- Updated
- Aug 3, 2024
- Vendor
- Jenkins Project
- Product
- Jenkins Git Plugin
- Classifications
- T1005
- Attack vector
- network
- Privileges
- Unavailable
Timeline
How it unfolded
- May 17, 2022CVE publishedPublication date reported by the CVE source.
- Aug 3, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=unspecified <=4.11.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo