CVE-2022-46687: XSS
First published: Wed Dec 07 2022(Updated: )
Jenkins Spring Config Plugin 2.0.0 and earlier does not escape build display names shown on the Spring Config view, resulting in a stored cross-site scripting (XSS) vulnerability exploitable by attackers able to change build display names.
Credit: jenkinsci-cert@googlegroups.com jenkinsci-cert@googlegroups.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| <2.0.1 | ||
| Jenkins Spring Config | <2.0.1 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Frequently Asked Questions
What is the severity of CVE-2022-46687?
CVE-2022-46687 is classified as a medium severity vulnerability due to its potential for stored cross-site scripting (XSS).
How do I fix CVE-2022-46687?
To fix CVE-2022-46687, update the Jenkins Spring Config Plugin to version 2.0.2 or later, which addresses the XSS vulnerability.
Who is affected by CVE-2022-46687?
CVE-2022-46687 affects all users of Jenkins Spring Config Plugin versions 2.0.0 and earlier.
What is the impact of exploiting CVE-2022-46687?
Exploiting CVE-2022-46687 allows attackers to execute arbitrary JavaScript in the context of the user's session through stored XSS.
Is CVE-2022-46687 a common vulnerability?
CVE-2022-46687 presents a common security concern within applications that fail to properly sanitize user input, specifically related to JavaScript execution.
- collector/nvd-index
- agent/type
- agent/weakness
- agent/references
- agent/severity
- agent/first-publish-date
- agent/description
- agent/author
- agent/event
- agent/softwarecombine
- agent/source
- agent/tags
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- collector/nvd-api
- source/NVD
- vendor/jenkins