Switch from snakeyaml to snakeyaml engine #5691
Merged
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.
We switched from snakeyaml to snakeyaml-engine in #5138.
One of the motivations for this was because of https://nvd.nist.gov/vuln/detail/CVE-2022-1471.
Since then, snakeyaml agreed to release 2.0 to address/quiet scanners: https://bitbucket.org/snakeyaml/snakeyaml/issues/561/cve-2022-1471-vulnerability-in#comment-64876314 (which is great).
Still probably a good idea to consolidate on snakeyaml-engine.
Btw, this doesn't remove
snakeyaml
from the classpath, sincejackson-dataformat-yaml
still usessnakeyaml
. They have updated tosnakeyaml-engine
inmaster
, but won't be released until 3.0 (https://github.com/FasterXML/jackson-dataformats-text/tree/master/yaml).