[Snyk] Upgrade dompurify from 2.0.1 to 2.0.8 #1
Conversation
This file contains 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
Snyk has created this PR to upgrade dompurify from 2.0.1 to 2.0.8. See this package in NPM: https://www.npmjs.com/package/dompurify See this project in Snyk: https://app.snyk.io/org/rtuspzmvjsofpm92992/project/2e9ad2a6-4d0b-43fc-9ec0-b20e1459edaa?utm_source=github&utm_medium=upgrade-pr
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.
Snyk has created this PR to upgrade dompurify from 2.0.1 to 2.0.8.
ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.The recommended version fixes:
SNYK-JS-DOMPURIFY-474012
SNYK-JS-DOMPURIFY-468981
Release notes
Package name: dompurify
-
2.0.8 - 2020-02-03
- Fixed a bypass that can be abused in case
- Added new elements to whitelist, thanks @chris-morgan
- Added first layer of prototype poisoning protection, thanks @dejang
- Added better controls for
- Added demo for node removal, thanks @mikesnare
-
2.0.7 - 2019-10-21
- Fixed several mXSS vectors spotted , thanks @masatokinugawa 🙇♂️
- Fixed a minor crash affecting MSIE11, see #372
- Fixed some typos and adjusted the README
-
2.0.6 - 2019-10-10
- Enhanced the checks for SVG-/MathML-based mXSS
- Removed several obtrusive checks and guards that are not needed any longer
- Added better test coverage
- Added better handling of situations where element removal causes mXSS
- Added better handling of content type switches causing mXSS
-
2.0.5 - 2019-10-08
- Fixed a logical issue causing overly aggressive SVG removal spotted by @thorn0
-
2.0.4 - 2019-10-07
-
2.0.3 - 2019-09-25
- Fixed another mXSS variation affecting Chrome, Safari and Edge relating to HTML templates
- Fixed a bug in the config parser leading to unexpected results
-
2.0.2 - 2019-09-23
-
2.0.1 - 2019-09-19
- Fixed a bypass affecting latest Chrome, caused by a newly discovered Chrome mXSS vulnerability
- Added tests to cover implemented fixes
from dompurify GitHub release notesSAFE_FOR_JQUERYis used with jQuery 3.x, thanks @masatokinugawa 🙇♀️uponSanitizeAttribute, thanks @devinrhode2Another mXSS variation was spotted by @masatokinugawa and got addressed and fixed in this release.
The fixes were reviewed and no new bypasses could be spotted at the moment.
Thanks, @masatokinugawa 🙇♂️ 🙇♀️!
The sanitization logic for this kind of mXSS was changed to be less aggressive and still be able to spot all recent mXSS variations we know about right now - while also avoiding risky string matching.
Prayers and thoughts that this was the final variation. But better be on the lookout for more releases soon.
Credits for the bypass again go to Michał Bentkowski (@securityMB) of Securitum who spotted the bug in Chrome, turned it into another DOMPurify bypass, reported and helped verifying the fix 🙇♂️ 🙇♀️
Following the release of DOMPurify 2.0.1, a more thorough internal audit against Blink-based mXSS bugs was conducted. Several mXSS variations, spotted by @masatokinugawa were addressed and fixed. The fixes were reviewed and so far no new bypasses could be spotted.
This release manages to find what is believed to be a more holistic way to prevent mXSS bugs, specifically coming from HTML attributes and tags nested inside SVG and MathML.
Further, this release also addresses a DoS problem caused by sanitization of HTML tables when configured with potentially conflicting configuration settings.
Credits go to Michał Bentkowski (@securityMB) of Securitum who spotted the bug in Chrome, turned it into a DOMPurify bypass, reported and helped verifying the fix. 🙇
Commit messages
Package name: dompurify
Compare
Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information:
🧐 View latest project report
🛠 Adjust upgrade PR settings
🔕 Ignore this dependency or unsubscribe from future upgrade PRs