CVE-2022-39350: @dependencytrack/frontend vulnerable to Persistent Cross-Site-Scripting via Vulnerability Details
First published: Tue Oct 25 2022(Updated: )
@dependencytrack/frontend is a Single Page Application (SPA) used in Dependency-Track, an open source Component Analysis platform that allows organizations to identify and reduce risk in the software supply chain. Due to the common practice of providing vulnerability details in markdown format, the Dependency-Track frontend renders them using the JavaScript library Showdown. Showdown does not have any XSS countermeasures built in, and versions before 4.6.1 of the Dependency-Track frontend did not encode or sanitize Showdown's output. This made it possible for arbitrary JavaScript included in vulnerability details via HTML attributes to be executed in context of the frontend. Actors with the `VULNERABILITY_MANAGEMENT` permission can exploit this weakness by creating or editing a custom vulnerability and providing XSS payloads in any of the following fields: Description, Details, Recommendation, or References. The payload will be executed for users with the `VIEW_PORTFOLIO` permission when browsing to the modified vulnerability's page. Alternatively, malicious JavaScript could be introduced via any of the vulnerability databases mirrored by Dependency-Track. However, this attack vector is highly unlikely, and the maintainers of Dependency-Track are not aware of any occurrence of this happening. Note that the `Vulnerability Details` element of the `Audit Vulnerabilities` tab in the project view is not affected. The issue has been fixed in frontend version 4.6.1.
Credit: security-advisories@github.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| OWASP Dependency-Track | <4.6.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.
Reference Links
- https://docs.dependencytrack.org/changelog/
- https://github.com/DependencyTrack/frontend/security/advisories/GHSA-c33w-pm52-mqvf
- https://github.com/showdownjs/showdown/wiki/Markdown's-XSS-Vulnerability-(and-how-to-mitigate-it)
- https://github.com/showdownjs/showdown/wiki/Markdown%27s-XSS-Vulnerability-%28and-how-to-mitigate-it%29
Frequently Asked Questions
What is CVE-2022-39350?
@dependencytrack/frontend is a Single Page Application (SPA) used in Dependency-Track, an open source Component Analysis platform that allows organizations to identify and reduce risk in the software supply chain. Due to the common practice of providing vulnerability details in markdown format, the SPA is vulnerable to a cross-site scripting (XSS) attack.
What is the severity of CVE-2022-39350?
The severity of CVE-2022-39350 is medium, with a CVSS score of 5.4.
How does CVE-2022-39350 affect @dependencytrack/frontend?
CVE-2022-39350 affects @dependencytrack/frontend version up to exclusive 4.6.1.
How can I mitigate the vulnerability in @dependencytrack/frontend?
To mitigate the vulnerability in @dependencytrack/frontend, update to a version beyond 4.6.1, as the vulnerability has been fixed in later versions.
Where can I find more information about CVE-2022-39350?
You can find more information about CVE-2022-39350 in the OWASP Dependency-Track documentation and the GitHub security advisory mentioned in the references.
- agent/type
- agent/softwarecombine
- collector/mitre-cve
- source/MITRE
- agent/weakness
- agent/last-modified-date
- agent/author
- agent/references
- agent/title
- agent/severity
- agent/description
- agent/first-publish-date
- agent/event
- agent/source
- agent/tags
- collector/nvd-index
- agent/software-canonical-lookup-request
- vendor/owasp
- canonical/owasp dependency-track