Stored XSS via unescaped parameter metadata
Published Jun 30, 2022 · Updated Aug 3, 2024
Stored XSS in Jenkins Validating Email Parameter Plugin 1.10 and earlier allows remote authenticated users to run scripts in viewers' browsers. The plugin renders the parameter type's name and description without escaping and disables Jenkins hardening for the Build With Parameters and Parameters pages. Item/Configure permission is required to store a payload, and script execution occurs when another user views an affected page.
Summary
What happened
Stored XSS in Jenkins Validating Email Parameter Plugin 1.10 and earlier allows remote authenticated users to run scripts in viewers' browsers. The plugin renders the parameter type's name and description without escaping and disables Jenkins hardening for the Build With Parameters and Parameters pages. Item/Configure permission is required to store a payload, and script execution occurs when another user views an affected page.
The record
- CVE
- CVE-2022-34791
- Published
- Jun 30, 2022
- Updated
- Aug 3, 2024
- Vendor
- Jenkins Project
- Product
- Jenkins Validating Email Parameter Plugin
- Classifications
- CWE-79, T1203
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 30, 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.10
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