@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.
{"id": "CVE-2022-39350", "vendorId": null, "type": "cve", "bulletinFamily": "NVD", "title": "CVE-2022-39350", "description": "@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.", "published": "2022-10-25T17:15:00", "modified": "2022-10-28T19:24:00", "epss": [{"cve": "CVE-2022-39350", "epss": 0.00061, "percentile": 0.23901, "modified": "2023-06-03"}], "cvss": {"score": 4.9, "vector": "AV:N/AC:M/Au:S/C:P/I:P/A:N"}, "cvss2": {"cvssV2": {"version": "2.0", "vectorString": "AV:N/AC:M/Au:S/C:P/I:P/A:N", "accessVector": "NETWORK", "accessComplexity": "MEDIUM", "authentication": "SINGLE", "confidentialityImpact": "PARTIAL", "integrityImpact": "PARTIAL", "availabilityImpact": "NONE", "baseScore": 4.9}, "severity": "MEDIUM", "exploitabilityScore": 6.8, "impactScore": 4.9, "acInsufInfo": false, "obtainAllPrivilege": false, "obtainUserPrivilege": false, "obtainOtherPrivilege": false, "userInteractionRequired": false}, "cvss3": {"cvssV3": {"version": "3.1", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N", "attackVector": "NETWORK", "attackComplexity": "LOW", "privilegesRequired": "LOW", "userInteraction": "REQUIRED", "scope": "CHANGED", "confidentialityImpact": "LOW", "integrityImpact": "LOW", "availabilityImpact": "NONE", "baseScore": 5.4, "baseSeverity": "MEDIUM"}, "exploitabilityScore": 2.3, "impactScore": 2.7}, "href": "https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-39350", "reporter": "security-advisories@github.com", "references": ["https://github.com/DependencyTrack/frontend/security/advisories/GHSA-c33w-pm52-mqvf", "https://docs.dependencytrack.org/changelog/", "https://github.com/showdownjs/showdown/wiki/Markdown's-XSS-Vulnerability-(and-how-to-mitigate-it)"], "cvelist": ["CVE-2022-39350"], "immutableFields": [], "lastseen": "2023-06-03T14:59:12", "viewCount": 26, "enchantments": {"score": {"value": 1.1, "vector": "NONE"}, "dependencies": {"references": [{"type": "github", "idList": ["GHSA-C33W-PM52-MQVF"]}, {"type": "osv", "idList": ["OSV:GHSA-C33W-PM52-MQVF"]}]}, "twitter": {"counter": 6, "tweets": [{"link": "https://twitter.com/www_sesin_at/status/1585178407872208896", "text": "New post from https://t.co/9KYxtdZjkl (CVE-2022-39350 | DependencyTrack Frontend up to 4.6.0 cross site scripting (GHSA-c33w-pm52-mqvf)) has been published on https://t.co/tUkQb7EFHI", "author": "www_sesin_at", "author_photo": "https://pbs.twimg.com/profile_images/958100963822329858/fb_N8h5n_400x400.jpg"}, {"link": "https://twitter.com/WolfgangSesin/status/1585178404961271809", "text": "New post from https://t.co/uXvPWJy6tj (CVE-2022-39350 | DependencyTrack Frontend up to 4.6.0 cross site scripting (GHSA-c33w-pm52-mqvf)) has been published on https://t.co/pLJ7bYMrGL", "author": "WolfgangSesin", "author_photo": "https://pbs.twimg.com/profile_images/957011635369054208/Om3jbj7z_400x400.jpg"}, {"link": "https://twitter.com/WolfgangSesin/status/1586123200920002563", "text": "New post from https://t.co/uXvPWJy6tj (CVE-2022-39350 (dependency-track_frontend)) has been published on https://t.co/OgtNW3ciDf", "author": "WolfgangSesin", "author_photo": "https://pbs.twimg.com/profile_images/957011635369054208/Om3jbj7z_400x400.jpg"}, {"link": "https://twitter.com/www_sesin_at/status/1586123202937458688", "text": "New post from https://t.co/9KYxtdZjkl (CVE-2022-39350 (dependency-track_frontend)) has been published on https://t.co/Yx36byaEMc", "author": "www_sesin_at", "author_photo": "https://pbs.twimg.com/profile_images/958100963822329858/fb_N8h5n_400x400.jpg"}]}, "affected_software": {"major_version": [{"name": "owasp dependency-track frontend", "version": 4}]}, "epss": [{"cve": "CVE-2022-39350", "epss": 0.00061, "percentile": 0.23807, "modified": "2023-05-02"}], "vulnersScore": 1.1}, "_state": {"score": 1685805531, "dependencies": 1685835658, "twitter": 0, "affected_software_major_version": 0, "epss": 0}, "_internal": {"score_hash": "d539bb424c7335d9fb4d341587110e5f"}, "cna_cvss": {"cna": "GitHub, Inc.", "cvss": {"3": {"vector": "CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N", "score": 5.4}}}, "cpe": [], "cpe23": [], "cwe": ["CWE-79"], "affectedSoftware": [{"cpeName": "owasp:dependency-track_frontend", "version": "4.6.1", "operator": "lt", "name": "owasp dependency-track frontend"}], "affectedConfiguration": [], "cpeConfiguration": {"CVE_data_version": "4.0", "nodes": [{"operator": "OR", "children": [], "cpe_match": [{"vulnerable": true, "cpe23Uri": "cpe:2.3:a:owasp:dependency-track_frontend:4.6.1:*:*:*:*:*:*:*", "versionEndExcluding": "4.6.1", "cpe_name": []}]}]}, "extraReferences": [{"url": "https://github.com/DependencyTrack/frontend/security/advisories/GHSA-c33w-pm52-mqvf", "name": "https://github.com/DependencyTrack/frontend/security/advisories/GHSA-c33w-pm52-mqvf", "refsource": "CONFIRM", "tags": ["Third Party Advisory"]}, {"url": "https://docs.dependencytrack.org/changelog/", "name": "https://docs.dependencytrack.org/changelog/", "refsource": "MISC", "tags": ["Release Notes", "Third Party Advisory"]}, {"url": "https://github.com/showdownjs/showdown/wiki/Markdown's-XSS-Vulnerability-(and-how-to-mitigate-it)", "name": "https://github.com/showdownjs/showdown/wiki/Markdown's-XSS-Vulnerability-(and-how-to-mitigate-it)", "refsource": "MISC", "tags": ["Exploit", "Mitigation", "Third Party Advisory"]}], "product_info": [{"vendor": "DependencyTrack", "product": "frontend"}], "solutions": [], "workarounds": [], "impacts": [], "problemTypes": [{"descriptions": [{"type": "CWE", "lang": "en", "description": "CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')", "cweId": "CWE-79"}]}], "exploits": []}
{"osv": [{"lastseen": "2022-10-25T20:52:43", "description": "### 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.", "cvss3": {}, "published": "2022-10-25T20:22:01", "type": "osv", "title": "@dependencytrack/frontend vulnerable to Persistent Cross-Site-Scripting via Vulnerability Details", "bulletinFamily": "software", "cvss2": {}, "cvelist": ["CVE-2022-39350"], "modified": "2022-10-25T20:22:01", "id": "OSV:GHSA-C33W-PM52-MQVF", "href": "https://osv.dev/vulnerability/GHSA-c33w-pm52-mqvf", "cvss": {"score": 0.0, "vector": "NONE"}}], "github": [{"lastseen": "2023-06-03T17:12:40", "description": "### 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.", "cvss3": {"exploitabilityScore": 2.3, "cvssV3": {"baseSeverity": "MEDIUM", "confidentialityImpact": "LOW", "attackComplexity": "LOW", "scope": "CHANGED", "attackVector": "NETWORK", "availabilityImpact": "NONE", "integrityImpact": "LOW", "privilegesRequired": "LOW", "baseScore": 5.4, "vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N", "version": "3.1", "userInteraction": "REQUIRED"}, "impactScore": 2.7}, "published": "2022-10-25T20:22:01", "type": "github", "title": "@dependencytrack/frontend vulnerable to Persistent Cross-Site-Scripting via Vulnerability Details", "bulletinFamily": "software", "cvss2": {"severity": "MEDIUM", "exploitabilityScore": 6.8, "obtainAllPrivilege": false, "userInteractionRequired": false, "obtainOtherPrivilege": false, "cvssV2": {"accessComplexity": "MEDIUM", "confidentialityImpact": "PARTIAL", "availabilityImpact": "NONE", "integrityImpact": "PARTIAL", "baseScore": 4.9, "vectorString": "AV:N/AC:M/Au:S/C:P/I:P/A:N", "version": "2.0", "accessVector": "NETWORK", "authentication": "SINGLE"}, "impactScore": 4.9, "acInsufInfo": false, "obtainUserPrivilege": false}, "cvelist": ["CVE-2022-39350"], "modified": "2023-01-30T05:02:58", "id": "GHSA-C33W-PM52-MQVF", "href": "https://github.com/advisories/GHSA-c33w-pm52-mqvf", "cvss": {"score": 4.9, "vector": "AV:N/AC:M/Au:S/C:P/I:P/A:N"}}]}
CVE-2022-39350
