future-architect.github.io
future-architect.github.io copied to clipboard
Bump dompurify from 3.0.6 to 3.1.6
Bumps dompurify from 3.0.6 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-choDOMPurify 3.1.4
- Fixed an issue with the recently implemented
isNaNchecks, 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
nodeTypeproperty, 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_XMLto 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
@AlekseySolovey3TDOMPurify 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
4083a90Merge pull request #978 from cure53/main90a10a1fix: Fixed a typo on the README65df042chore: Preparing 3.1.6 release6e03334fix: Made sure that remove() is not called directly from node00fc06cfix: Fixed a DOM clobbering issue leading to an error being thrownf8c2ef5Merge pull request #977 from cure53/dependabot/npm_and_yarn/multi-99ca4f73d8e5112ecbuild(deps): bump ws and socket.io-adapter9978cecdocs: Added better security warning about SAFE_FOR_XML to READMEfa542dffix: Changed the order for attribute checks slightly for safer hooksb8b552cMerge pull request #975 from cure53/dependabot/npm_and_yarn/multi-2d3aef8690- Additional commits viewable in compare view
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) You can disable automated security fix PRs for this repo from the Security Alerts page.