Stored XSS via unsanitized coverage names
Published Mar 23, 2023 · Updated Feb 25, 2025
Stored XSS in Jenkins Project JaCoCo Plugin 3.3.2 and earlier allows attackers to run scripts via crafted coverage input files. AbstractReport.setName stores class and method names from coverage data without neutralizing HTML metacharacters before those names appear in the Jenkins UI. An attacker must control input files for the post-build action, and script execution occurs when a user views the generated coverage UI.
Summary
What happened
Stored XSS in Jenkins Project JaCoCo Plugin 3.3.2 and earlier allows attackers to run scripts via crafted coverage input files. AbstractReport.setName stores class and method names from coverage data without neutralizing HTML metacharacters before those names appear in the Jenkins UI. An attacker must control input files for the post-build action, and script execution occurs when a user views the generated coverage UI.
The record
- CVE
- CVE-2023-28669
- Published
- Mar 23, 2023
- Updated
- Feb 25, 2025
- Vendor
- Jenkins Project
- Product
- JaCoCo Plugin
- Classifications
- CWE-79, T1059.007
- Attack vector
- network
- Privileges
- authenticated
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 <=3.3.2
What conditions does exploitation require?
What is affected?
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