Upgrade snakeyaml from 1.33 to 2.0 fixing CVE-2022-1471 #2266
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.
Snakeyaml 2.0 has a fix for the CVE-2022-1471 Arbitrary Code Execution vulnerability:
https://nvd.nist.gov/vuln/detail/CVE-2022-1471
https://bitbucket.org/snakeyaml/snakeyaml/wiki/Changes
Karate is not affected by this vulnerability, but other code might be so that Karate should be compatible with Snakeyaml 2.0 and by default should ship with Snakeyaml 2.0.
The JsonUtils code change is required for 2.0 but also works in 1.33 so that projects that use latest Karate may manually downgrade Snakeyaml from 2.0 to 1.33 if needed.
Description