Homepage

org.webjars.npm:dompurify@3.4.7

  • latest version

    3.4.11

  • latest non vulnerable version

    3.4.11

  • first published

    8 years ago

  • latest version published

    6 days ago

  • licenses detected

  • package registry

    View on Maven Central Repository
    • Go back to all versions of this package
    Report a new vulnerability Found a mistake?

    Direct Vulnerabilities

    Known vulnerabilities in the org.webjars.npm:dompurify package. This does not include vulnerabilities belonging to this package’s dependencies.

    Fix vulnerabilities automatically

    Snyk's AI Trust Platform automatically finds the best upgrade path and integrates with your development workflows. Secure your code at zero cost.

    Fix for free
    VulnerabilityVulnerable Version
    • M
    Improper Initialization

    org.webjars.npm:dompurify is a DOM-only XSS sanitizer for HTML, MathML and SVG.

    Affected versions of this package are vulnerable to Improper Initialization in the DOMPurify.setConfig() API when an uponSanitizeAttribute hook is registered that mutates allowedAttributes. An attacker can cause persistent modification of the attribute allowlist by submitting specially crafted content, resulting in unauthorized attributes being permitted in all subsequent sanitization calls.

    How to fix Improper Initialization?

    Upgrade org.webjars.npm:dompurify to version 3.4.11 or higher.

    [,3.4.11)
    • L
    Protection Mechanism Failure

    org.webjars.npm:dompurify is a DOM-only XSS sanitizer for HTML, MathML and SVG.

    Affected versions of this package are vulnerable to Protection Mechanism Failure through the clearConfig function. An attacker can execute arbitrary scripts in a Trusted Types sink by influencing a previously supplied TRUSTED_TYPES_POLICY on a reused instance and later triggering output with RETURN_TRUSTED_TYPE: true.

    Note:

    This is only exploitable if a DOMPurify instance is reused across trust boundaries and a less-trusted integration or attacker has previously set an unsafe Trusted Types policy.

    How to fix Protection Mechanism Failure?

    Upgrade org.webjars.npm:dompurify to version 3.4.9 or higher.

    [,3.4.9)
    • M
    Cross-site Scripting (XSS)

    org.webjars.npm:dompurify is a DOM-only XSS sanitizer for HTML, MathML and SVG.

    Affected versions of this package are vulnerable to Cross-site Scripting (XSS) in the SAFE_FOR_TEMPLATES function. An attacker can inject template expressions that survive sanitization inside <template> element content by splitting malicious expressions across adjacent text nodes, which are not properly scrubbed. This allows execution of arbitrary code or exfiltration of sensitive data if a downstream template engine evaluates the merged content.

    This is only exploitable if both SAFE_FOR_TEMPLATES: true and either RETURN_DOM: true, RETURN_DOM_FRAGMENT: true, or IN_PLACE: true are explicitly set, and the application processes <template>.content with a template engine.

    How to fix Cross-site Scripting (XSS)?

    Upgrade org.webjars.npm:dompurify to version 3.4.8 or higher.

    [3.0.1,3.4.8)
    • M
    Cross-site Scripting (XSS)

    org.webjars.npm:dompurify is a DOM-only XSS sanitizer for HTML, MathML and SVG.

    Affected versions of this package are vulnerable to Cross-site Scripting (XSS) in the IN_PLACE process when attacker-controlled live DOM nodes are sanitized. An attacker can execute arbitrary scripts in the context of the application by passing a manipulated DOM node with a spoofed nodeName property, causing malicious script elements to be retained and executed upon insertion into the document.

    How to fix Cross-site Scripting (XSS)?

    Upgrade org.webjars.npm:dompurify to version 3.4.8 or higher.

    [,3.4.8)
    Go back to all versions of this package