[Snyk] Upgrade @xmldom/xmldom from 0.8.2 to 0.8.6 #1155
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Snyk has created this PR to upgrade @xmldom/xmldom from 0.8.2 to 0.8.6. See this package in npm: https://www.npmjs.com/package/@xmldom/xmldom See this project in Snyk: https://app.snyk.io/org/thomaschampagne/project/bfb9c345-ce01-4680-a310-f23d7201d1c0?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
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Snyk has created this PR to upgrade @xmldom/xmldom from 0.8.2 to 0.8.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 fixes:
SNYK-JS-XMLDOMXMLDOM-3042243
Why? Has a fix available, CVSS 8.5
SNYK-JS-XMLDOMXMLDOM-3092934
Why? Has a fix available, CVSS 8.5
(*) Note that the real score may have changed since the PR was raised.
Release notes
Package name: @xmldom/xmldom
-
0.8.6 - 2022-11-05
- Properly check nodes before replacement
-
0.8.5 - 2022-10-31
- fix: Restore ES5 compatibility
-
0.8.4 - 2022-10-29
- Security: Prevent inserting DOM nodes when they are not well-formed
-
0.8.3 - 2022-10-11
-
0.8.2 - 2022-04-05
from @xmldom/xmldom GitHub release notesCommits
Fixed
#457/#455/#456Thank you, @ edemaine, @ pedro-l9, for your contributions
Commits
Fixed
#452/#453Thank you, @ fengxinming, for your contributions
Commits
Fixed
CVE-2022-39353In case such a DOM would be created, the part that is not well-formed will be transformed into text nodes, in which xml specific characters like
<and>are encoded accordingly.In the upcoming version 0.9.0 those text nodes will no longer be added and an error will be thrown instead.
This change can break your code, if you relied on this behavior, e.g. multiple root elements in the past. We consider it more important to align with the specs that we want to be aligned with, considering the potential security issues that might derive from people not being aware of the difference in behavior.
Related Spec: https://dom.spec.whatwg.org/#concept-node-ensure-pre-insertion-validity
Thank you, @ frumioj, @ cjbarth, @ markgollnick for your contributions
Commit messages
Package name: @xmldom/xmldom
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