Stored XSS via unescaped past-build parameters
Published Feb 24, 2021 · Updated Aug 3, 2024
Stored XSS in Jenkins Repository Connector Plugin 2.0.2 and earlier allows remote authenticated users to execute script in a viewer's browser. Past-build views render attacker-controlled parameter names and descriptions without escaping them. Item/Configure permission is required to store the payload, and a viewer must open the affected build page for browser-side code execution.
Summary
What happened
Stored XSS in Jenkins Repository Connector Plugin 2.0.2 and earlier allows remote authenticated users to execute script in a viewer's browser. Past-build views render attacker-controlled parameter names and descriptions without escaping them. Item/Configure permission is required to store the payload, and a viewer must open the affected build page for browser-side code execution.
The record
- CVE
- CVE-2021-21618
- Published
- Feb 24, 2021
- Updated
- Aug 3, 2024
- Vendor
- Jenkins Project
- Product
- Repository Connector Plugin
- Classifications
- CWE-79, T1059.007
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 24, 2021CVE 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 <=2.0.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