Address high severity issue by upgrading fast-xml-parser
#83
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
Upgrade fast-xml-parser from v3 to v4 in order to address a (according to npm) high severity vulnerability, namely CVE-2023-34104. I did not evaluate the impact of the CVE on this project, but upgrading is easy enough and avoids any potential problems. Plus, staying on the latest available version is always good :)
|
🎉 This PR is included in version 2.4.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
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.
Upgrade
fast-xml-parserfrom v3 to v4 in order to address a (according to npm) high severity vulnerability, namely CVE-2023-34104. I did not evaluate the impact of the CVE on this project, but upgrading is easy enough and avoids any potential problems. Plus, staying on the latest available version is always good :)