This repository has been archived by the owner on May 30, 2024. It is now read-only.
Bump SnakeYAML from 1.19 to 1.26 to address CVE-2017-18640 #207
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
gwhelanLD
changed the title
|
We'll put this out in the 5.0.5 release. To clarify for anyone taking a look at the PR, the SDK only parses YAML if the application has configured the SDK with a flag data file. It's unlikely CVE-2017-18640 would affect SDK usage as it requires configuration and access to a local file. Thanks for the PR, |
LaunchDarklyCI
pushed a commit
that referenced
this pull request
Sep 3, 2020
5.0: remove NewRelicReflector
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Requirements
Related issues
https://nvd.nist.gov/vuln/detail/CVE-2017-18640
Describe the solution you've provided
Snakeyaml has security vulnerability in 1.19 which is fixed in 1.26
Describe alternatives you've considered
Provide a clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context about the pull request here.