Controller secret disclosure and SSRF via external entities
Published Mar 23, 2023 · Updated Feb 25, 2025
XXE in the XML report parser in Jenkins Project Crap4J Plugin 0.9 and earlier allows attackers to extract controller secrets via Crap Reports. The parser processes configured report.xml files without disabling external entities, so crafted declarations can read controller resources or trigger server-side requests. An attacker must control a Crap Report consumed by a configured freestyle job; access is limited to data readable or network locations reachable by the controller.
Summary
What happened
XXE in the XML report parser in Jenkins Project Crap4J Plugin 0.9 and earlier allows attackers to extract controller secrets via Crap Reports. The parser processes configured report.xml files without disabling external entities, so crafted declarations can read controller resources or trigger server-side requests. An attacker must control a Crap Report consumed by a configured freestyle job; access is limited to data readable or network locations reachable by the controller.
The record
- CVE
- CVE-2023-28680
- Published
- Mar 23, 2023
- Updated
- Feb 25, 2025
- Vendor
- Jenkins Project
- Product
- Crap4J Plugin
- Classifications
- CWE-611, T1005
- Attack vector
- network
- Privileges
- Unavailable
Timeline
How it unfolded
- Mar 23, 2023CVE publishedPublication date reported by the CVE source.
- Feb 25, 2025Record 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=0 <=0.9
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