Skip to content

[Snyk] Upgrade dompurify from 3.1.1 to 3.1.2 #63

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

Closed

Conversation

sunil-lakshman
Copy link
Contributor

This PR was automatically created by Snyk using the credentials of a real user.


Snyk has created this PR to upgrade dompurify from 3.1.1 to 3.1.2.

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

  • The recommended version was released 21 days ago, on 2024-04-30.

Release notes
Package name: dompurify
  • 3.1.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
  • 3.1.1 - 2024-04-26
    • 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.

from dompurify GitHub release notes
Commit messages
Package name: dompurify
  • 74664db chore: Updated package-lock.json with new release number
  • 5f17b27 chore: Preparing 3.1.2 release
  • 5d492ee test: Fixed the tests for older Chrome and Safari
  • 8075b37 fix: Adjusted the list of permitted SVG HTML integration points
  • 61b761f fix: Switched to using the getParentNode API for some calls
  • ee17313 docs: Added new mentions of honor to the readme

Compare


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:

🧐 View latest project report

🛠 Adjust upgrade PR settings

🔕 Ignore this dependency or unsubscribe from future upgrade PRs

Note: This is a default PR template raised by Snyk. Find out more about how you can customise Snyk PRs in our documentation.

Snyk has created this PR to upgrade dompurify from 3.1.1 to 3.1.2.

See this package in npm:
dompurify

See this project in Snyk:
https://app.snyk.io/org/sunil-lakshman/project/f3a2751a-cf7e-4c1b-98f1-273120b6bc4c?utm_source=github&utm_medium=referral&page=upgrade-pr
@sunil-lakshman sunil-lakshman requested a review from a team as a code owner May 21, 2024 10:45
Copy link

We regret to inform you that you are currently not able to merge your changes into the master branch due to restrictions applied by our SRE team. To proceed with merging your changes, we kindly request that you create a pull request from the next branch. Our team will then review the changes and work with you to ensure a successful merge into the master branch.

Copy link

Coverage report

St.
Category Percentage Covered / Total
🟢 Statements 98.86% 434/439
🟢 Branches 85.17% 333/391
🟢 Functions 100% 111/111
🟢 Lines 99.03% 410/414

Test suite run success

221 tests passing in 18 suites.

Report generated by 🧪jest coverage report action from f2be8fc

Copy link

Coverage report

St.
Category Percentage Covered / Total
🟢 Statements 98.86% 434/439
🟢 Branches 85.17% 333/391
🟢 Functions 100% 111/111
🟢 Lines 99.03% 410/414

Test suite run success

221 tests passing in 18 suites.

Report generated by 🧪jest coverage report action from f2be8fc

@reeshika-h
Copy link
Contributor

This package has been removed from the repository.
PR: #75

@reeshika-h reeshika-h closed this Jul 8, 2024
@aravindbuilt aravindbuilt deleted the snyk-upgrade-dfec8a8fa4d24b95b8c59ffff99ac10f branch October 28, 2024 12:13
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.

3 participants