Bump dompurify from 2.4.4 to 3.1.6
Bumps dompurify from 2.4.4 to 3.1.6.
Release notes
Sourced from dompurify's releases.
DOMPurify 3.1.6
- Fixed an issue with the execution logic of attribute hooks to prevent bypasses, thanks
@kevin-mizu
- Fixed an issue with element removal leading to uncaught errors through DOM Clobbering, thanks
@realansgar
- Fixed a minor problem with the bower file pointing to the wrong dist path
- Fixed several minor typos in docs, comments and comment blocks, thanks
@Rotzbua
- Updated several development dependencies
DOMPurify 3.1.5
- Fixed a minor issue with the dist paths in
bower.js
, thanks@HakumenNC
- Fixed a minor issue with sanitizing HTML coming from copy&paste Word content, thanks
@kakao-bishop-cho
DOMPurify 3.1.4
- Fixed an issue with the recently implemented
isNaN
checks, thanks@tulach
- Added several new popover attributes to allow-list, thanks
@Gigabyte5671
- Fixed the tests and adjusted the test runner to cover all branches
DOMPurify 3.1.3
- Fixed several mXSS variations found by and thanks to
@kevin-mizu
&@Ry0taK
- Added better configurability for comment scrubbing default behavior
- Added better hardening against Prototype Pollution attacks, thanks
@kevin-mizu
- Added better handling and readability of the
nodeType
property, thanks@ssi02014
- Fixed some smaller issues in README and other documentation
DOMPurify 3.1.2
- Addressed and fixed a mXSS variation found by
@kevin-mizu
- Addressed and fixed a mXSS variation found by Adam Kues of Assetnote
- Updated tests for older Safari and Chrome versions
DOMPurify 3.1.1
- Fixed an mXSS sanitiser bypass reported by
@icesfont
- Added new code to track element nesting depth
- Added new code to enforce a maximum nesting depth of 255
- Added coverage tests and necessary clobbering protections
Note that this is a security release and should be upgraded to immediately. Please also note that further releases may follow as the underlying vulnerability is apparently new and further variations may be discovered.
DOMPurify 3.1.0
- Added new setting
SAFE_FOR_XML
to enable better control over comment scrubbing- Updated README to warn about happy-dom not being safe for use with DOMPurify yet
- Updated the LICENSE file to show the accurate year number
- Updated several build and test dependencies
DOMPurify 3.0.11
- Fixed another conditional bypass caused by Processing Instructions, thanks
@Ry0taK
- Fixed the regex for HTML Custom Element detection, thanks
@AlekseySolovey3T
DOMPurify 3.0.10
- Fixed two possible bypasses when sanitizing an XML document and later using it in HTML, thanks
@Slonser
- Bumped up some build and test dependencies
... (truncated)
Commits
-
4083a90
Merge pull request #978 from cure53/main -
90a10a1
fix: Fixed a typo on the README -
65df042
chore: Preparing 3.1.6 release -
6e03334
fix: Made sure that remove() is not called directly from node -
00fc06c
fix: Fixed a DOM clobbering issue leading to an error being thrown -
f8c2ef5
Merge pull request #977 from cure53/dependabot/npm_and_yarn/multi-99ca4f73d8 -
e5112ec
build(deps): bump ws and socket.io-adapter -
9978cec
docs: Added better security warning about SAFE_FOR_XML to README -
fa542df
fix: Changed the order for attribute checks slightly for safer hooks -
b8b552c
Merge pull request #975 from cure53/dependabot/npm_and_yarn/multi-2d3aef8690 - Additional commits viewable in compare view
Dependabot commands
You can trigger Dependabot actions by commenting on this MR
-
$dependabot rebase
will rebase this MR -
$dependabot recreate
will recreate this MR rewriting all the manual changes and resolving conflicts