Update PyYAML to 5.3.1 #6276
Merged
Update PyYAML to 5.3.1 #6276
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
AlexandreYang
approved these changes
Apr 7, 2020
ofek
approved these changes
Apr 7, 2020
mgarabed
pushed a commit
that referenced
this pull request
Apr 7, 2020
* Update PyYAML to 5.3.1 * Freeze deps
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.
This PR updates the PyYAML dependency from 5.3.0 to 5.3.1 to include a patch for CVE-2020-1747
This CVE allows arbitrary code execution when using the
full_loadmethod but because the Datadog Agent loads yaml safely the impact is minimal. For more details: #3089As documented here, the CVE patch is the only change between those two PyYAML versions.