# What is CVE-2022-39350? > CVE-2022-39350 is a medium-severity flaw (CVSS 5.4) in Dependency-Track Frontend from Owasp, published on 25 October 2022. It is not on the list of flaws known to be exploited today. The latest forecast puts its chance of use in the next 30 days at 0.7%. If you run an affected version, plan in the vendor’s fix. Canonical page: https://www.precursorintelligence.com/what-is/cve-2022-39350 ## At a glance - **Verdict:** Plan it in. No sign of exploitation and a low forecast. Patch it in your normal update cycle. - **Precursor Intelligence risk score:** 20 out of 100 (Low); action: Monitor. Kept up to date as the evidence changes. - **Severity:** Medium (CVSS 5.4 out of 10) - **Known to be exploited:** No, not on the list of flaws known to be exploited today - **Chance of use in the next 30 days:** 0.7% (latest exploit-likelihood forecast) - **Published:** 25 October 2022 - **Record last updated:** 7 November 2023 - **Main product:** Dependency-Track Frontend from Owasp - **Affected products:** 1 ## What is CVE-2022-39350? In plain terms It can be attacked from anywhere on the internet with an ordinary user account, but a person has to take an action first. If it works, the attacker can read some data and change some data. ### The official 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. ### What kind of flaw is it? - CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') ### How an attack on it works - Where an attacker can be: Anywhere on the internet - How hard it is to pull off: Easy: no special conditions - Login needed first: An ordinary user account - Does someone have to click: Yes, a person has to take an action - What an attacker gets: Can read some data and change some data Severity vector: `CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N` ## Is CVE-2022-39350 being exploited? Not that we know of It is not on the list of flaws known to be exploited today. The latest forecast puts the chance of it being used in the next 30 days at 0.7%. That can change at any time, which is why we keep watching. Exploit likelihood over the last 7 days: 0.7%, 0.7%, 0.7%, 0.7%, 0.7%, 0.7%, 0.7%. ### Timeline - 25 October 2022: Published - 7 November 2023: Record last updated ### How Precursor Intelligence ranks it CVE-2022-39350 scores **20 out of 100 (Low)**, with the action "Monitor". Every published flaw gets a risk score from 0 to 100, kept up to date as the evidence changes. Four things go into the score, from the one that counts most to the ones that count less: - Evidence it is being exploited: biggest factor - How severe it is: strong factor - How widely exposed it is: smaller factor - Threat activity around it: smaller factor 85 and above is Critical. Anything confirmed as exploited is always marked for an emergency patch, whatever its score. When this flaw matches software you track, it lands in your list with its score and the reasons behind it. ## Who is affected by CVE-2022-39350? The published record lists 1 product. Versions are as published: "before 4.6.1" means every version up to, but not including, 4.6.1. - [Dependency-Track Frontend](https://www.precursorintelligence.com/product/owasp/dependency-track_frontend) by [Owasp](https://www.precursorintelligence.com/vendors/owasp) (Application): before 4.6.1 ## How do I fix CVE-2022-39350? 1. **Check whether you run it.** Compare your versions with the affected products above. Not sure what you run? Precursor Intelligence can work it out from your public website, or you can pick it from a list. 2. **Apply the vendor’s fix.** Install the latest update from the vendor. The references list where the vendor has published details. 3. **If you can’t patch today.** Follow any mitigation the vendor publishes, and limit who can reach the affected system from the internet until the update is in. 4. **Keep an eye on it.** Track the product and we tell you as soon as we spot this flaw on the list of exploited flaws, or a jump in its exploit likelihood. ### References - [docs.dependencytrack.org](https://docs.dependencytrack.org/changelog/) (Release notes, Third-party advisory) - [github.com](https://github.com/DependencyTrack/frontend/security/advisories/GHSA-c33w-pm52-mqvf) (Third-party advisory) - [github.com](https://github.com/showdownjs/showdown/wiki/Markdown%27s-XSS-Vulnerability-%28and-how-to-mitigate-it%29) ## Questions ### What is CVE-2022-39350? CVE-2022-39350 is a medium-severity flaw in Dependency-Track Frontend from Owasp, published on 25 October 2022. It can be attacked from anywhere on the internet with an ordinary user account, but a person has to take an action first. If it works, the attacker can read some data and change some data. ### How serious is CVE-2022-39350? It scores 5.4 out of 10 on the CVSS severity scale, which is medium. Our risk score for CVE-2022-39350 is 20 out of 100, which is Low. Its action is "Monitor". No sign of exploitation and a low forecast. Patch it in your normal update cycle. ### Is CVE-2022-39350 being exploited? It is not on the list of flaws known to be exploited today. The latest forecast puts the chance of it being used in the next 30 days at 0.7%. That can change at any time, which is why we keep watching. ### Which versions does CVE-2022-39350 affect? For Dependency-Track Frontend from Owasp: before 4.6.1. ### How do I fix CVE-2022-39350? Install the update the vendor names in its advisory. If you can't patch today, follow the vendor's mitigation and limit who can reach the affected system from the internet. ## Does CVE-2022-39350 affect you? Precursor Intelligence keeps checking for you: - **Tell us what you run.** Pick your software from a list, or let us work it out from your website. - **We match it to every flaw.** Over 400,000 published flaws, checked against your list. - **Ranked by real-world risk.** Every flaw gets a 0 to 100 risk score, kept up to date, led by evidence criminals are using it. - **Told as soon as we know.** An alert by email, in the app or by webhook to your own tools. Start free (no card, nothing to install): https://www.precursorintelligence.com/register Book a demo: https://www.precursorintelligence.com/contact