CVE-2022-39350: @dependencytrack/frontend @dependencytrack/frontend Vulnerable To Persistent Cross-Site-Scripting Vulnerability
MODERATECVE-2022-39350 is a MODERATE (CVSS 5.4) @dependencytrack/frontend vulnerable to persistent cross-site-scripting vulnerability (CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')) affecting @dependencytrack/frontend libraries in the npm ecosystem. The issue involves @dependencytrack/frontend vulnerable to persistent cross-site-scripting via vulnerability details. Remediation is available by upgrading affected packages to version 4.6.1.
CVE-2022-39350 at a Glance
Security Impact
CVSS: 5.4
The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N).
How to Fix CVE-2022-39350
To remediate this vulnerability, upgrade all affected @dependencytrack/frontend dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
npm install @dependencytrack/frontend@4.6.1
Run the following command in your project directory to verify that all resolved dependencies use the patched release:
npm ls @dependencytrack/frontend
How to Check if You Are Affected
To determine whether your Node.js application is affected by CVE-2022-39350, inspect your project dependencies using npm:
npm ls @dependencytrack/frontend
Analyze the terminal output to locate any version of @dependencytrack/frontend in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 4.6.1), your application is affected.
Note: The npm ls @dependencytrack/frontend command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.
Technical Details
Vulnerability Mechanism & Technical Analysis
This vulnerability is classified under CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting'), where the product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users. In @dependencytrack/frontend, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.
Source Advisory Statement
CVE-2022-39350 Affected @dependencytrack/frontend Versions
1 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
@dependencytrack/frontend
|
npm |
< 4.6.1
|
4.6.1
|
References
Frequently Asked Questions
What is CVE-2022-39350?
Which @dependencytrack/frontend versions are affected?
What version fixes CVE-2022-39350?
Is @dependencytrack/frontend affected?
What is the CVSS score of CVE-2022-39350?
What CWE is associated with CVE-2022-39350?
How can I check npm dependencies for CVE-2022-39350?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-c33w-pm52-mqvf",
"modified" : "2022-10-25T20:22:01Z",
"published" : "2022-10-25T20:22:01Z",
"aliases" : [ "CVE-2022-39350" ],
"summary" : "@dependencytrack/frontend vulnerable to Persistent Cross-Site-Scripting via Vulnerability Details",
"details" : "### Description\n\nDue to the common practice of providing vulnerability details in markdown format, the Dependency-Track frontend renders them using the JavaScript library [Showdown](https://github.com/showdownjs/showdown). Showdown [does not have any XSS countermeasures built in](https://github.com/showdownjs/showdown/wiki/Markdown's-XSS-Vulnerability-(and-how-to-mitigate-it)), 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.\n\n### Impact\n\nActors 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:\n\n* Description\n* Details\n* Recommendation\n* References\n\nThe payload will be executed for users with the `VIEW_PORTFOLIO` permission when browsing to the modified vulnerability's page, for example: \n\n```\nhttps://dtrack.example.com/vulnerabilities/INTERNAL/INT-jd8u-e8tl-8lwu\n```\n\nAlternatively, malicious JavaScript could be introduced via any of the vulnerability databases mirrored by Dependency-Track (NVD, GitHub Advisories, OSV, OSS Index, VulnDB). However, this attack vector is highly unlikely, and the team is not aware of any occurrence of this happening.\n\n> **Note**\n> The *Vulnerability Details* element of the *Audit Vulnerabilities* tab in the project view is **not** affected.\n\n### Patches\n\nThe issue has been fixed in frontend version 4.6.1.\n\n### Credit\n\nThanks to GitHub user **Waterstraal** for finding and responsibly disclosing the issue.",
"severity" : [ {
"type" : "CVSS_V3",
"score" : "CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "npm",
"name" : "@dependencytrack/frontend"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0"
}, {
"fixed" : "4.6.1"
} ]
} ]
} ],
"references" : [ {
"type" : "WEB",
"url" : "https://github.com/DependencyTrack/frontend/security/advisories/GHSA-c33w-pm52-mqvf"
}, {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2022-39350"
}, {
"type" : "WEB",
"url" : "https://docs.dependencytrack.org/changelog"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/DependencyTrack/frontend"
}, {
"type" : "WEB",
"url" : "https://github.com/showdownjs/showdown/wiki/Markdown's-XSS-Vulnerability-(and-how-to-mitigate-it)"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-79" ],
"severity" : "MODERATE",
"github_reviewed" : true,
"github_reviewed_at" : "2022-10-25T20:22:01Z",
"nvd_published_at" : "2022-10-25T17:15:00Z"
}
}