Skip to content

[Snyk] Security upgrade dompurify from 2.0.12 to 3.2.7#22

Open
dexterinbk wants to merge 1 commit intomasterfrom
snyk-fix-b6297efd96f9289c5008303de791fcae
Open

[Snyk] Security upgrade dompurify from 2.0.12 to 3.2.7#22
dexterinbk wants to merge 1 commit intomasterfrom
snyk-fix-b6297efd96f9289c5008303de791fcae

Conversation

@dexterinbk
Copy link

snyk-top-banner

Snyk has created this PR to fix 1 vulnerabilities in the npm dependencies of this project.

Snyk changed the following file(s):

  • package.json
⚠️ Warning
Failed to update the package-lock.json, please update manually before merging.

Vulnerabilities that will be fixed with an upgrade:

Issue Score
medium severity Cross-site Scripting (XSS)
SNYK-JS-DOMPURIFY-15371386
  100  

Breaking Change Risk

Merge Risk: Medium

Notice: This assessment is enhanced by AI.


Important

  • Check the changes in this PR to ensure they won't cause issues with your project.
  • Max score is 1000. Note that the real score may have changed since the PR was raised.
  • This PR was automatically created by Snyk using the credentials of a real user.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.

For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic


Learn how to fix vulnerabilities with free interactive lessons:

🦉 Cross-site Scripting (XSS)

The following vulnerabilities are fixed with an upgrade:
- https://snyk.io/vuln/SNYK-JS-DOMPURIFY-15371386
@dexterinbk
Copy link
Author

Merge Risk: Medium

This major version upgrade of DOMPurify from v2.0.12 to v3.2.7 introduces significant changes, primarily related to browser support and third-party library interactions.

Breaking Changes:

  • Internet Explorer (MSIE) Support Dropped: Support for MSIE was removed after version 2.5.8. If your application still needs to support Internet Explorer, you should not upgrade beyond the 2.x branch.
  • Removal of jQuery Vulnerability Mitigation: A workaround for a jQuery vulnerability (CVE-2020-11022) was present in DOMPurify 2.x but was removed in version 3.0.0. Developers are now responsible for ensuring they are using a secure, updated version of jQuery (>= 3.5.0) if it's used in conjunction with DOMPurify.

Recommendation:

Verify that your project's browser support requirements do not include Internet Explorer. If you are using jQuery, confirm that you are on a version that is not vulnerable to CVE-2020-11022.

Source: DOMPurify GitHub Repository

Notice 🤖: This content was augmented using artificial intelligence. AI-generated content may contain errors and should be reviewed for accuracy before use.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants