Stored XSS via unescaped parameter metadata
Published Apr 12, 2022 · Updated Aug 3, 2024
Stored XSS in Jenkins Subversion Plugin 2.15.3 and earlier allows remote authenticated users to execute scripts in another user's browser. List Subversion tags parameter names and descriptions are stored without output escaping and rendered by parameter-listing views. Exploitation requires Item/Configure permission, a page that lists the parameter, and user interaction with a view that lacks hardening; successful execution can read or modify data available to that browser session.
Summary
What happened
Stored XSS in Jenkins Subversion Plugin 2.15.3 and earlier allows remote authenticated users to execute scripts in another user's browser. List Subversion tags parameter names and descriptions are stored without output escaping and rendered by parameter-listing views. Exploitation requires Item/Configure permission, a page that lists the parameter, and user interaction with a view that lacks hardening; successful execution can read or modify data available to that browser session.
The record
- CVE
- CVE-2022-29046
- Published
- Apr 12, 2022
- Updated
- Aug 3, 2024
- Vendor
- Jenkins Project
- Product
- Jenkins Subversion Plugin
- Classifications
- CWE-79, T1203
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 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 <=2.15.3
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