Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Snyk] Upgrade dompurify from 2.0.17 to 2.5.6 #56

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

NOUIY
Copy link
Owner

@NOUIY NOUIY commented Jul 26, 2024

snyk-top-banner

Snyk has created this PR to upgrade dompurify from 2.0.17 to 2.5.6.

ℹ️ 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 is 42 versions ahead of your current version.

  • The recommended version was released on 21 days ago.

Issues fixed by the recommended upgrade:

Issue Score Exploit Maturity
medium severity Cross-site Scripting (XSS)
SNYK-JS-DOMPURIFY-1035544
539 No Known Exploit
medium severity Cross-site Scripting (XSS)
SNYK-JS-DOMPURIFY-2863266
539 Proof of Concept
medium severity Template Injection
SNYK-JS-DOMPURIFY-6474511
539 Proof of Concept
Release notes
Package name: dompurify
  • 2.5.6 - 2024-07-05
    • Fixed an issue with the execution logic of attribute hooks to prevent bypasses, thanks @ kevin-mizu
    • Fixed a minor problem with the bower file pointing to the wrong dist path
    • Updated several development dependencies
  • 2.5.5 - 2024-05-31
    • 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
  • 2.5.4 - 2024-05-20
    • Fixed a bug with latest isNaN checks affecting MSIE, thanks @ tulach
    • Fixed the tests for MSIE and fixed related test-runner
  • 2.5.3 - 2024-05-11
    • 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
    • Fixed some smaller issues in README and other documentation
  • 2.5.2 - 2024-04-30
    • 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
  • 2.5.1 - 2024-04-26
  • 2.5.0 - 2024-04-07
  • 2.4.9 - 2024-03-21
  • 2.4.8 - 2024-03-19
  • 2.4.7 - 2023-07-11
  • 2.4.6 - 2023-07-10
  • 2.4.5 - 2023-03-01
  • 2.4.4 - 2023-02-13
  • 2.4.3 - 2023-01-06
  • 2.4.2 - 2023-01-05
  • 2.4.1 - 2022-11-10
  • 2.4.0 - 2022-08-24
  • 2.3.12 - 2022-08-23
  • 2.3.11 - 2022-08-23
  • 2.3.10 - 2022-07-18
  • 2.3.9 - 2022-07-11
  • 2.3.8 - 2022-05-13
  • 2.3.7 - 2022-05-11
  • 2.3.6 - 2022-02-16
  • 2.3.5 - 2022-01-26
  • 2.3.4 - 2021-12-07
  • 2.3.3 - 2021-09-20
  • 2.3.2 - 2021-09-15
  • 2.3.1 - 2021-08-13
  • 2.3.0 - 2021-07-06
  • 2.2.9 - 2021-06-01
  • 2.2.8 - 2021-04-28
  • 2.2.7 - 2021-03-12
  • 2.2.6 - 2020-12-18
  • 2.2.5 - 2020-12-18
  • 2.2.4 - 2020-12-15
  • 2.2.3 - 2020-12-07
  • 2.2.2 - 2020-11-02
  • 2.2.1 - 2020-11-02
  • 2.2.0 - 2020-10-21
  • 2.1.1 - 2020-09-25
  • 2.1.0 - 2020-09-23
  • 2.0.17 - 2020-09-20
from dompurify GitHub release notes

Important

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

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:

Snyk has created this PR to upgrade dompurify from 2.0.17 to 2.5.6.

See this package in npm:
dompurify

See this project in Snyk:
https://app.snyk.io/org/nexuscompute/project/dbfe8f52-87e9-4dec-a761-0171c172494e?utm_source=github&utm_medium=referral&page=upgrade-pr
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