Use SafeLoader in yaml.load()
Calls
#432
Closed
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 codemod hardens all
yaml.load()
calls against attacks that could result from deserializing untrusted data.The fix uses a safety check that already exists in the
yaml
module, replacing unsafe loader class withSafeLoader
.The changes from this codemod look like this:
The codemod will also catch if you pass in the loader argument as a kwarg and if you use any loader other than
SafeLoader
,including
FullLoader
andUnsafeLoader
.More reading
I have additional improvements ready for this repo! If you want to see them, leave the comment:
... and I will open a new PR right away!
Powered by: pixeebot (codemod ID: pixee:python/harden-pyyaml)