🚨 [security] Update dompurify 2.0.7 → 3.4.13 (major) - #147
Open
depfu[bot] wants to merge 1 commit into
Open
Conversation
|
Tick the box to add this pull request to the merge queue (same as
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
🚨 Your current dependencies have known security vulnerabilities 🚨
This dependency update fixes known security vulnerabilities. Please see the details below and assess their impact carefully. We recommend to merge and deploy this as soon as possible!
Here is everything you need to know about this upgrade. Please take a good look at what changed and the test results before merging this pull request.
What changed?
✳️ dompurify (2.0.7 → 3.4.13) · Repo
Security Advisories 🚨
🚨 DOMPurify: IN_PLACE hook removal leaves a detached subtree executable, causing XSS
🚨 DOMPurify: `CUSTOM_ELEMENT_HANDLING` bypasses `afterSanitizeElements` for allowed custom elements.
🚨 DOMPurify: Permanent `ALLOWED_ATTR` pollution via `setConfig()` bypassing the hook clone-guard (incomplete fix of the 3.4.7 hook-pollution patch)
🚨 DOMPurify IN_PLACE Sanitization Bypass via Attached Shadow Root Inside .content
🚨 DOMPurify: Hook mutation of `data.allowedTags` / `data.allowedAttributes` permanently pollutes `DEFAULT_ALLOWED_TAGS` / `DEFAULT_ALLOWED_ATTR`
🚨 DOMPurify: Cross-realm IN_PLACE sanitization leaves executable markup intact via realm-bound `instanceof` checks
🚨 DOMPurify: IN_PLACE mode preserves attributes of a clobbered root element, allowing XSS via attacker-controlled root DOM
🚨 DOMPurify: Trusted Types policy survives `clearConfig()` and can poison later `RETURN_TRUSTED_TYPE` output
🚨 DOMPurify: SAFE_FOR_TEMPLATES bypass - template expressions survive sanitization inside content when using DOM output modes
🚨 DOMPurify XSS via selectedcontent re-clone
🚨 DOMPurify has a SAFE_FOR_TEMPLATES bypass in RETURN_DOM mode
🚨 DOMPurify: FORBID_TAGS bypassed by function-based ADD_TAGS predicate (asymmetry with FORBID_ATTR fix)
🚨 DOMPurify: Prototype Pollution to XSS Bypass via CUSTOM_ELEMENT_HANDLING Fallback
🚨 DOMPurify's ADD_TAGS function form bypasses FORBID_TAGS due to short-circuit evaluation
🚨 DOMPurify USE_PROFILES prototype pollution allows event handlers
🚨 DOMPurify ADD_ATTR predicate skips URI validation
🚨 DOMPurify is vulnerable to mutation-XSS via Re-Contextualization
🚨 DOMPurify contains a Cross-site Scripting vulnerability
🚨 DOMPurify contains a Cross-site Scripting vulnerability
🚨 DOMPurify contains a Cross-site Scripting vulnerability
🚨 DOMPurify allows Cross-site Scripting (XSS)
🚨 DOMPurify vulnerable to tampering by prototype polution
🚨 DOMpurify has a nesting-based mXSS
🚨 DOMpurify has a nesting-based mXSS
🚨 DOMPurify allows tampering by prototype pollution
🚨 DOMPurify allows tampering by prototype pollution
🚨 Cross-site Scripting in dompurify
Release Notes
Too many releases to show here. View the full release notes.
Commits
See the full diff on Github. The new version differs by more commits than we can show here.
🆕 @types/trusted-types (added, 2.0.7)
Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with
@depfu rebase.All Depfu comment commands