This repository has been archived by the owner on Oct 23, 2024. It is now read-only.
chore(deps): update dependency pyyaml to v5 [security] #3362
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 contains the following updates:
==3.13
->==5.4
Warning
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
GitHub Vulnerability Alerts
CVE-2020-14343
A vulnerability was discovered in the PyYAML library in versions before 5.4, where it is susceptible to arbitrary code execution when it processes untrusted YAML files through the full_load method or with the FullLoader loader. Applications that use the library to process untrusted input may be vulnerable to this flaw. This flaw allows an attacker to execute arbitrary code on the system by abusing the python/object/new constructor. This flaw is due to an incomplete fix for CVE-2020-1747.
CVE-2020-1747
A vulnerability was discovered in the PyYAML library in versions before 5.3.1, where it is susceptible to arbitrary code execution when it processes untrusted YAML files through the full_load method or with the FullLoader loader. Applications that use the library to process untrusted input may be vulnerable to this flaw. An attacker could use this flaw to execute arbitrary code on the system by abusing the python/object/new constructor.
CVE-2017-18342
In PyYAML before 4.1, the
yaml.load()
API could execute arbitrary code. In other words,yaml.safe_load
is not used.Release Notes
yaml/pyyaml (PyYAML)
v5.4
Compare Source
v5.3.1
Compare Source
v5.3
Compare Source
v5.2
Compare Source
but several methods like add_constructor still used the old defahttps://github.com/yaml/pyyaml/pull/279pull/279 -- A more flexible fix for custom tag consthttps://github.com/yaml/pyyaml/pull/287aml/pull/287 -- Change default loader for yaml.add_https://github.com/yaml/pyyaml/pull/305/pyyaml/pull/305 -- Change default loader for add_implicit_resolver, add_path_resolver
https://github.com/yaml/pyyaml/pull/347/347 -- Move constructor for object/apply to UnsafeConstructor
https://github.com/yaml/pyyaml/pull/276/276 -- Fix logic for quoting special characters
https://github.com/yaml/pyyaml/pull/280/280 -- Update CHANGES for 5.1
v5.1.2
Compare Source
v5.1.1
Compare Source
v5.1
Compare Source
Configuration
📅 Schedule: Branch creation - "" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.