Cross-site scripting via tampered depth tracking
Published Sep 16, 2024 · Updated Sep 16, 2024
Cross-site scripting in Cure53 DOMPurify before 2.5.4 and 3.0.0 through 3.1.2 allows attackers to bypass HTML sanitization. The sanitizer trusts the mutable __depth property on DOM nodes, so prototype pollution can make it NaN and defeat both maximum-nesting comparisons. An application must sanitize attacker-controlled, specially nested markup and then render the result; surviving active content executes in that application's browser origin.
Summary
What happened
Cross-site scripting in Cure53 DOMPurify before 2.5.4 and 3.0.0 through 3.1.2 allows attackers to bypass HTML sanitization. The sanitizer trusts the mutable __depth property on DOM nodes, so prototype pollution can make it NaN and defeat both maximum-nesting comparisons. An application must sanitize attacker-controlled, specially nested markup and then render the result; surviving active content executes in that application's browser origin.
The record
- CVE
- CVE-2024-45801
- Published
- Sep 16, 2024
- Updated
- Sep 16, 2024
- Vendor
- Cure53
- Product
- DOMPurify
- Classifications
- CWE-1333, CWE-1321, T1059.007
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 16, 2024CVE publishedPublication date reported by the CVE source.
- Sep 16, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 2.5.4
- Affected versionversion=>=3.0.0, < 3.1.3
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo