🚨 [security] Update dompurify 2.4.1 → 2.4.9 (patch) #103
Conversation
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
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #103 +/- ##
=========================================
Coverage 100.00% 100.00%
=========================================
Files 5 5
Lines 134 134
Branches 28 28
=========================================
Hits 134 134 ☔ View full report in Codecov by Sentry. |
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 update. Please take a good look at what changed and the test results before merging this pull request.
What changed?
✳️ dompurify (2.4.1 → 2.4.9) · Repo
Security Advisories 🚨
🚨 DOMPurify vulnerable to tampering by prototype polution
Release Notes
2.4.9
2.4.8
2.4.7
2.4.6
2.4.4
2.4.3
2.4.2
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 30 commits:
chore: Preparing 2.4.9 releasefix: Merged relevant changes from main for 2.4.9chore: Preparing 2.4.8 releasechore: Preparing 2.4.8. releasefix: cherry-picked fixes for XML & CE bypasschore: Preparing 2.4.7. releasechore: Preparing 2.4.6 releaseFix: addressed a bypass on jsdom 22 when noframes tag is allowedchore: preparing 2.4.5 releasechore: preparing 2.4.4 releasesee #767test: Added 2.x tag to 2.x branch actionsSee #761Merge pull request #750 from cure53/dependabot/npm_and_yarn/json5-1.0.2chore: Prepare 2.4.3, final feature release compatible w. MSIE10/11build(deps): bump json5 from 1.0.1 to 1.0.2fix: merged from latest mainUpdate README.mdchore: Preparing 2.4.2 releasefix: Fixed a prototype pollution bug reported by @kevin_mizuMerge pull request #748 from tosmolka/tosmolka/747Fix formattingFix Trusted Types Sink violation with empty input and NAMESPACEMerge pull request #745 from cure53/dependabot/npm_and_yarn/qs-and-body-parser-6.11.0build(deps): bump qs and body-parserMerge pull request #737 from cure53/dependabot/npm_and_yarn/engine.io-and-socket.io-6.2.1build(deps): bump engine.io and socket.ioMerge pull request #732 from Pomierski/patch-1fixchore: fix allowCustomizedBuiltInElements comment in readmeDepfu 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