Secret extraction and SSRF via unsafe XML parsing
Published Nov 12, 2021 · Updated Aug 4, 2024
XXE in Jenkins OWASP Dependency-Check Plugin 5.1.1 and earlier allows attackers to extract controller secrets or trigger SSRF. ReportParser processes workspace dependency-check-report.xml files with an XML parser that does not reject DTDs or external entities. Attackers must control workspace contents; exploitation reads controller-accessible secrets or makes requests from the controller.
Summary
What happened
XXE in Jenkins OWASP Dependency-Check Plugin 5.1.1 and earlier allows attackers to extract controller secrets or trigger SSRF. ReportParser processes workspace dependency-check-report.xml files with an XML parser that does not reject DTDs or external entities. Attackers must control workspace contents; exploitation reads controller-accessible secrets or makes requests from the controller.
The record
- CVE
- CVE-2021-43577
- Published
- Nov 12, 2021
- Updated
- Aug 4, 2024
- Vendor
- Jenkins Project
- Product
- OWASP Dependency-Check Jenkins Plugin
- Classifications
- CWE-611, T1005
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Nov 12, 2021CVE publishedPublication date reported by the CVE source.
- Aug 4, 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 <=5.1.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