GHSA-C33W-PM52-MQVF

Vulnerability from github – Published: 2022-10-25 20:22 – Updated: 2022-10-25 20:22
VLAI?
Summary
@dependencytrack/frontend vulnerable to Persistent Cross-Site-Scripting via Vulnerability Details
Details

Description

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.

Impact

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
  • References

The payload will be executed for users with the VIEW_PORTFOLIO permission when browsing to the modified vulnerability's page, for example: 

https://dtrack.example.com/vulnerabilities/INTERNAL/INT-jd8u-e8tl-8lwu

Alternatively, 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.

Note The Vulnerability Details element of the Audit Vulnerabilities tab in the project view is not affected.

Patches

The issue has been fixed in frontend version 4.6.1.

Credit

Thanks to GitHub user Waterstraal for finding and responsibly disclosing the issue.

Severity ?
5.4 (Medium)
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
Show details on source website
To clipboard 

{
  "affected": [
    {
      "package": {
        "ecosystem": "npm",
        "name": "@dependencytrack/frontend"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "4.6.1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "aliases": [
    "CVE-2022-39350"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-79"
    ],
    "github_reviewed": true,
    "github_reviewed_at": "2022-10-25T20:22:01Z",
    "nvd_published_at": "2022-10-25T17:15:00Z",
    "severity": "MODERATE"
  },
  "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\u0027s-XSS-Vulnerability-(and-how-to-mitigate-it)), and versions before 4.6.1 of the Dependency-Track frontend did not encode or sanitize Showdown\u0027s 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\u0027s 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\u003e **Note**\n\u003e 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.",
  "id": "GHSA-c33w-pm52-mqvf",
  "modified": "2022-10-25T20:22:01Z",
  "published": "2022-10-25T20:22:01Z",
  "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\u0027s-XSS-Vulnerability-(and-how-to-mitigate-it)"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N",
      "type": "CVSS_V3"
    }
  ],
  "summary": "@dependencytrack/frontend vulnerable to  Persistent Cross-Site-Scripting via Vulnerability Details"
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.




Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.



Detection rules are retrieved from Rulezet.