Stored XSS via unescaped Failure Cause names
Published Sep 20, 2023 · Updated Sep 24, 2024
Stored XSS in Jenkins Build Failure Analyzer Plugin 2.4.1 and earlier allows remote authenticated users to execute script in log viewers. The plugin inserts attacker-controlled Failure Cause names into build logs without HTML escaping, so a rendered name becomes executable page content. Exploitation requires permission to create or update Failure Causes and a user to view a build log; script runs in that viewer's Jenkins session.
Summary
What happened
Stored XSS in Jenkins Build Failure Analyzer Plugin 2.4.1 and earlier allows remote authenticated users to execute script in log viewers. The plugin inserts attacker-controlled Failure Cause names into build logs without HTML escaping, so a rendered name becomes executable page content. Exploitation requires permission to create or update Failure Causes and a user to view a build log; script runs in that viewer's Jenkins session.
The record
- CVE
- CVE-2023-43499
- Published
- Sep 20, 2023
- Updated
- Sep 24, 2024
- Vendor
- Jenkins Project
- Product
- Build Failure Analyzer Plugin
- Classifications
- CWE-79, T1189
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 20, 2023CVE publishedPublication date reported by the CVE source.
- Sep 24, 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=0 <=2.4.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