Stored XSS via unescaped badge metadata
Published Jan 12, 2022 · Updated Aug 3, 2024
Stored XSS in Jenkins Badge Plugin 1.9 and earlier allows remote authenticated users to run script in a viewer's browser via crafted badges. Badge creation neither escapes the supplied description nor restricts link URLs to allowed protocols, preserving attacker-controlled active content. Item/Configure permission is required to store the payload, and execution requires another user to view the affected badge.
Summary
What happened
Stored XSS in Jenkins Badge Plugin 1.9 and earlier allows remote authenticated users to run script in a viewer's browser via crafted badges. Badge creation neither escapes the supplied description nor restricts link URLs to allowed protocols, preserving attacker-controlled active content. Item/Configure permission is required to store the payload, and execution requires another user to view the affected badge.
The record
- CVE
- CVE-2022-23108
- Published
- Jan 12, 2022
- Updated
- Aug 3, 2024
- Vendor
- Jenkins Project
- Product
- Badge
- Classifications
- CWE-79, T1059.007
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 12, 2022CVE publishedPublication date reported by the CVE source.
- Aug 3, 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 <=1.9
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