GHSA-H6P3-P4VX-WR8Q

Vulnerability from github – Published: 2023-01-11 23:47 – Updated: 2023-01-11 23:47
VLAI
Summary
dompurify vulnerable to Cross-site Scripting
Details

dompurify prior to version 2.2.3 is vulnerable to a cross-site scripting problem caused by nested headlines.

Show details on source website

{
  "affected": [
    {
      "package": {
        "ecosystem": "PyPI",
        "name": "dompurify"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "2.2.3"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "aliases": [],
  "database_specific": {
    "cwe_ids": [],
    "github_reviewed": true,
    "github_reviewed_at": "2023-01-11T23:47:24Z",
    "nvd_published_at": null,
    "severity": "MODERATE"
  },
  "details": "dompurify prior to version 2.2.3 is vulnerable to a cross-site scripting problem caused by nested headlines.",
  "id": "GHSA-h6p3-p4vx-wr8q",
  "modified": "2023-01-11T23:47:24Z",
  "published": "2023-01-11T23:47:24Z",
  "references": [
    {
      "type": "PACKAGE",
      "url": "https://github.com/cure53/DOMPurify"
    },
    {
      "type": "WEB",
      "url": "https://github.com/cure53/DOMPurify/releases/tag/2.2.3"
    },
    {
      "type": "WEB",
      "url": "https://security.snyk.io/vuln/SNYK-JS-DOMPURIFY-2863266"
    },
    {
      "type": "WEB",
      "url": "https://www.vidocsecurity.com/blog/hacking-swagger-ui-from-xss-to-account-takeovers"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [],
  "summary": "dompurify vulnerable to Cross-site Scripting"
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

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.

Loading…

Detection rules are retrieved from Rulezet.

Loading…

Loading…