Skip to content

[Security] Bump dompurify from 1.0.1 to 2.0.17#270

Open
dependabot-preview[bot] wants to merge 1 commit intodevelopfrom
dependabot/npm_and_yarn/dompurify-2.0.17
Open

[Security] Bump dompurify from 1.0.1 to 2.0.17#270
dependabot-preview[bot] wants to merge 1 commit intodevelopfrom
dependabot/npm_and_yarn/dompurify-2.0.17

Conversation

@dependabot-preview
Copy link

Bumps dompurify from 1.0.1 to 2.0.17. This update includes security fixes.

Vulnerabilities fixed

Sourced from The GitHub Security Advisory Database.

Cross-site Scripting in dompurify Cure53 DOMPurify before 2.0.17 allows mutation XSS. This occurs because a serialize-parse roundtrip does not necessarily return the original DOM tree, and a namespace can change from HTML to MathML, as demonstrated by nesting of FORM elements.

Affected versions: < 2.0.17

Sourced from The GitHub Security Advisory Database.

Cross-Site Scripting in dompurify Versions of dompurify prior to 2.0.7 are vulnerable to Cross-Site Scripting (XSS). It is possible to bypass the package sanitization through Mutation XSS, which may allow an attacker to execute arbitrary JavaScript in a victim's browser.

Recommendation

Upgrade to version 2.0.7 or later.

Affected versions: < 2.0.7

Sourced from The GitHub Security Advisory Database.

Cross-Site Scripting in dompurify DOMPurify before 2.0.1 allows XSS because of innerHTML mutation XSS (mXSS) for an SVG element or a MATH element, as demonstrated by Chrome and Safari.

Affected versions: < 2.0.3

Release notes

Sourced from dompurify's releases.

DOMPurify 2.0.17

  • Fixed another bypass causing mXSS by using MathML

DOMPurify 2.0.16

  • Fixed an mXSS-based bypass caused by nested forms inside MathML
  • Fixed a security error thrown on older Chrome on Android versions, see #470

Credits for the bypass 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 🙇‍♂️ 🙇‍♀️

DOMPurify 2.0.15

  • Added a renovated test suite, thanks @peernohell
  • Fixed some minor linter warnings

DOMPurify 2.0.14

  • Fixed a problem with the documentMode default value

DOMPurify 2.0.12

  • Fixed a minor bug when working with Trusted Types
  • Fixed some typos in a demo file
  • Fixed some wordings in code and docs

DOMPurify 2.0.11

  • Fixed faulty behavior for non breaking space characters
  • Added ADD_DATA_URI_TAGS directive to allow customizing Data URI tag behavior

DOMPurify 2.0.10

  • Fixed a dependency problem causing builds to break
  • Fixed a test in Chrome 83 covering Trusted Types

DOMPurify 2.0.9

  • Removed a meanwhile useless parser check
  • Added countless new attributes to whitelist
  • Added whole new build and system
  • Added license tag to compressed files
  • Updated README for more clarity

DOMPurify 2.0.8

  • Fixed a bypass that can be abused in case SAFE_FOR_JQUERY is used with jQuery 3.x, thanks @masatokinugawa 🙇‍♀️
  • Added new elements to whitelist, thanks @chris-morgan
  • Added first layer of prototype poisoning protection, thanks @dejang
  • Added better controls for uponSanitizeAttribute, thanks @devinrhode2
  • Added demo for node removal, thanks @mikesnare

DOMPurify 2.0.7

  • Fixed several mXSS vectors spotted , thanks @masatokinugawa 🙇‍♂️
  • Fixed a minor crash affecting MSIE11, see #372
  • Fixed some typos and adjusted the README

DOMPurify 2.0.6

  • Enhanced the checks for SVG-/MathML-based mXSS
Commits
  • f04574b chore: preparing 2.0.17 release
  • 02724b8 fix: attemtping to fix another mutation behavior
  • 63061bf chore: Preparing 2.0.16 release
  • 95b7ad2 See #470
  • ce22c8c fix: Attempting to fix a MathML-based mXSS pattern
  • c025bc8 chore: preparing 2.0.15 release
  • 10ed33f fix: changed the linter settings to be more tolerant
  • 5922db6 Merge branch 'main' of git@github.com:cure53/DOMPurify.git into main
  • 7f6dfe2 docs: added peernohell to list of contributors
  • 4743c0b Merge pull request #464 from peernohell/main
  • Additional commits viewable in compare view

Dependabot compatibility score

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 rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot ignore this major version will 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 version will 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 dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
  • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
  • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
  • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language
  • @dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot dashboard:

  • Update frequency (including time of day and day of week)
  • Pull request limits (per update run and/or open at any time)
  • Automerge options (never/patch/minor, and dev/runtime dependencies)
  • Out-of-range updates (receive only lockfile updates, if desired)
  • Security updates (receive only security updates, if desired)

Bumps [dompurify](https://github.com/cure53/DOMPurify) from 1.0.1 to 2.0.17. **This update includes security fixes.**
- [Release notes](https://github.com/cure53/DOMPurify/releases)
- [Commits](cure53/DOMPurify@1.0.1...2.0.17)

Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
@dependabot-preview dependabot-preview bot added dependencies Pull requests that update a dependency file security Pull requests that address a security vulnerability labels Dec 18, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file security Pull requests that address a security vulnerability

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants

Comments