Secret extraction and SSRF via external entities
Published Mar 21, 2023 · Updated Feb 26, 2025
XXE in Jenkins AbsInt a³ Plugin 1.1.0 and earlier allows attackers controlling APX files to extract controller secrets or cause SSRF. The APX project-file parser accepts crafted external-entity declarations without disabling their resolution, causing Jenkins to read local resources or issue outbound requests. Exploitation requires control of the configured Project File (APX) contents; the reported consequences are secret extraction and server-side request forgery.
Summary
What happened
XXE in Jenkins AbsInt a³ Plugin 1.1.0 and earlier allows attackers controlling APX files to extract controller secrets or cause SSRF. The APX project-file parser accepts crafted external-entity declarations without disabling their resolution, causing Jenkins to read local resources or issue outbound requests. Exploitation requires control of the configured Project File (APX) contents; the reported consequences are secret extraction and server-side request forgery.
The record
- CVE
- CVE-2023-28685
- Published
- Mar 21, 2023
- Updated
- Feb 26, 2025
- Vendor
- Jenkins Project
- Product
- AbsInt a³ Jenkins Plugin
- Classifications
- CWE-611, T1005
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 21, 2023CVE publishedPublication date reported by the CVE source.
- Feb 26, 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 <=1.1.0
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