fix(security): bump dompurify to patch XSS and prototype pollution issues#622
Open
hitesh-shetty-cstk wants to merge 1 commit into
Open
fix(security): bump dompurify to patch XSS and prototype pollution issues#622hitesh-shetty-cstk wants to merge 1 commit into
hitesh-shetty-cstk wants to merge 1 commit into
Conversation
…sues Upgrades dompurify from 3.4.1 to 3.4.12 to pick up upstream sanitization bypass and prototype pollution fixes released in the 3.4.x line. Co-Authored-By: Claude <noreply@anthropic.com>
🔒 Security Scan Results
⏱️ SLA Breach Summary
✅ BUILD PASSED - All security checks passed |
Coverage Report
File CoverageNo changed files found. |
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
2 participants
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.
What was the vulnerability
Our pinned
dompurifyversion (^3.4.1) is affected by several sanitization-bypass (XSS) and prototype-pollution advisories fixed in later 3.4.x patch releases (e.g. a sanitization bypass fixed in 3.4.5, and follow-up hardening in subsequent patches).dompurifyis used throughout the SDK to sanitize HTML before rendering, so a bypass in the sanitizer undermines that protection.What the fix does
Bumps the
dompurifydependency from^3.4.1to^3.4.12(the latest 3.4.x release) inpackage.jsonand regenerates the corresponding lockfile entry. No code changes were needed — this is a drop-in patch-level upgrade within the same major version.How it was verified
3.4.12is the latest published 3.4.x release on the npm registry.dompurifyentries inpackage.json/package-lock.jsonwith no other lockfile drift.dompurifywas already a direct dependency.🤖 Generated with Claude Code
Generated by Claude Code