Stored XSS via unescaped parameter name
Published Feb 12, 2020 · Updated Aug 4, 2024
Stored XSS in Jenkins Git Parameter Plugin 0.9.11 and earlier allows remote authenticated users to run script in another user's browser. The GitParameterDefinition index.jelly view places the attacker-controlled parameter name into an entry title without HTML escaping. Job/Configure permission is required, and execution occurs when another user views the parameter UI, enabling access or actions within that user's Jenkins session.
Summary
What happened
Stored XSS in Jenkins Git Parameter Plugin 0.9.11 and earlier allows remote authenticated users to run script in another user's browser. The GitParameterDefinition index.jelly view places the attacker-controlled parameter name into an entry title without HTML escaping. Job/Configure permission is required, and execution occurs when another user views the parameter UI, enabling access or actions within that user's Jenkins session.
The record
- CVE
- CVE-2020-2112
- Published
- Feb 12, 2020
- Updated
- Aug 4, 2024
- Vendor
- Jenkins Project
- Product
- Jenkins Git Parameter Plugin
- Classifications
- CWE-79, T1203
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 12, 2020CVE publishedPublication date reported by the CVE source.
- Aug 4, 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.9.4 <unspecified
- Affected versionversion=unspecified <=0.9.11
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