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.
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`](https://redirect.github.com/yaml/pyyaml/compare/5.3.1...5.4)
[Compare Source](https://redirect.github.com/yaml/pyyaml/compare/5.3.1...5.4)
### [`v5.3.1`](https://redirect.github.com/yaml/pyyaml/compare/5.3...5.3.1)
[Compare Source](https://redirect.github.com/yaml/pyyaml/compare/5.3...5.3.1)
### [`v5.3`](https://redirect.github.com/yaml/pyyaml/compare/5.2...5.3)
[Compare Source](https://redirect.github.com/yaml/pyyaml/compare/5.2...5.3)
### [`v5.2`](https://redirect.github.com/yaml/pyyaml/blob/HEAD/CHANGES#52-2019-12-02)
[Compare Source](https://redirect.github.com/yaml/pyyaml/compare/5.1.2...5.2)
- Repair incompatibilities introduced with 5.1. The default Loader was changed,
but several methods like add_constructor still used the old defa[https://github.com/yaml/pyyaml/pull/279](https://redirect.github.com/yaml/pyyaml/pull/279)pull/279 -- A more flexible fix for custom tag const[https://github.com/yaml/pyyaml/pull/287](https://redirect.github.com/yaml/pyyaml/pull/287)aml/pull/287 -- Change default loader for yaml.add_[https://github.com/yaml/pyyaml/pull/305](https://redirect.github.com/yaml/pyyaml/pull/305)/pyyaml/pull/305 -- Change default loader for add_implicit_resolver, add_path_resolver
- Make FullLoader safer by removing python/object/apply from the default FullLoader
[https://github.com/yaml/pyyaml/pull/347](https://redirect.github.com/yaml/pyyaml/pull/347)/347 -- Move constructor for object/apply to UnsafeConstructor
- Fix bug introduced in 5.1 where quoting went wrong on systems with sys.maxunicode <= 0xffff
[https://github.com/yaml/pyyaml/pull/276](https://redirect.github.com/yaml/pyyaml/pull/276)/276 -- Fix logic for quoting special characters
- Other PRs:
[https://github.com/yaml/pyyaml/pull/280](https://redirect.github.com/yaml/pyyaml/pull/280)/280 -- Update CHANGES for 5.1
### [`v5.1.2`](https://redirect.github.com/yaml/pyyaml/blob/HEAD/CHANGES#512-2019-07-30)
[Compare Source](https://redirect.github.com/yaml/pyyaml/compare/5.1.1...5.1.2)
- Re-release of 5.1 with regenerated Cython sources to build properly for Python 3.8b2+
### [`v5.1.1`](https://redirect.github.com/yaml/pyyaml/blob/HEAD/CHANGES#511-2019-06-05)
[Compare Source](https://redirect.github.com/yaml/pyyaml/compare/5.1...5.1.1)
- Re-release of 5.1 with regenerated Cython sources to build properly for Python 3.8b1
### [`v5.1`](https://redirect.github.com/yaml/pyyaml/blob/HEAD/CHANGES#512-2019-07-30)
[Compare Source](https://redirect.github.com/yaml/pyyaml/compare/3.13...5.1)
- Re-release of 5.1 with regenerated Cython sources to build properly for Python 3.8b2+
### [`v3.13`](https://redirect.github.com/yaml/pyyaml/blob/HEAD/CHANGES#313-2018-07-05)
[Compare Source](https://redirect.github.com/yaml/pyyaml/compare/3.12...3.13)
- Resolved issues around PyYAML working in Python 3.7.
Configuration
📅 Schedule: Branch creation - "" in timezone America/Lima, 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.
[ ] If you want to rebase/retry this PR, check this box
This PR contains the following updates:
==3.12
->==5.4
:warning: MAJOR MAJOR MAJOR :warning:
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-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`](https://redirect.github.com/yaml/pyyaml/compare/5.3.1...5.4) [Compare Source](https://redirect.github.com/yaml/pyyaml/compare/5.3.1...5.4) ### [`v5.3.1`](https://redirect.github.com/yaml/pyyaml/compare/5.3...5.3.1) [Compare Source](https://redirect.github.com/yaml/pyyaml/compare/5.3...5.3.1) ### [`v5.3`](https://redirect.github.com/yaml/pyyaml/compare/5.2...5.3) [Compare Source](https://redirect.github.com/yaml/pyyaml/compare/5.2...5.3) ### [`v5.2`](https://redirect.github.com/yaml/pyyaml/blob/HEAD/CHANGES#52-2019-12-02) [Compare Source](https://redirect.github.com/yaml/pyyaml/compare/5.1.2...5.2) - Repair incompatibilities introduced with 5.1. The default Loader was changed, but several methods like add_constructor still used the old defa[https://github.com/yaml/pyyaml/pull/279](https://redirect.github.com/yaml/pyyaml/pull/279)pull/279 -- A more flexible fix for custom tag const[https://github.com/yaml/pyyaml/pull/287](https://redirect.github.com/yaml/pyyaml/pull/287)aml/pull/287 -- Change default loader for yaml.add_[https://github.com/yaml/pyyaml/pull/305](https://redirect.github.com/yaml/pyyaml/pull/305)/pyyaml/pull/305 -- Change default loader for add_implicit_resolver, add_path_resolver - Make FullLoader safer by removing python/object/apply from the default FullLoader [https://github.com/yaml/pyyaml/pull/347](https://redirect.github.com/yaml/pyyaml/pull/347)/347 -- Move constructor for object/apply to UnsafeConstructor - Fix bug introduced in 5.1 where quoting went wrong on systems with sys.maxunicode <= 0xffff [https://github.com/yaml/pyyaml/pull/276](https://redirect.github.com/yaml/pyyaml/pull/276)/276 -- Fix logic for quoting special characters - Other PRs: [https://github.com/yaml/pyyaml/pull/280](https://redirect.github.com/yaml/pyyaml/pull/280)/280 -- Update CHANGES for 5.1 ### [`v5.1.2`](https://redirect.github.com/yaml/pyyaml/blob/HEAD/CHANGES#512-2019-07-30) [Compare Source](https://redirect.github.com/yaml/pyyaml/compare/5.1.1...5.1.2) - Re-release of 5.1 with regenerated Cython sources to build properly for Python 3.8b2+ ### [`v5.1.1`](https://redirect.github.com/yaml/pyyaml/blob/HEAD/CHANGES#511-2019-06-05) [Compare Source](https://redirect.github.com/yaml/pyyaml/compare/5.1...5.1.1) - Re-release of 5.1 with regenerated Cython sources to build properly for Python 3.8b1 ### [`v5.1`](https://redirect.github.com/yaml/pyyaml/blob/HEAD/CHANGES#512-2019-07-30) [Compare Source](https://redirect.github.com/yaml/pyyaml/compare/3.13...5.1) - Re-release of 5.1 with regenerated Cython sources to build properly for Python 3.8b2+ ### [`v3.13`](https://redirect.github.com/yaml/pyyaml/blob/HEAD/CHANGES#313-2018-07-05) [Compare Source](https://redirect.github.com/yaml/pyyaml/compare/3.12...3.13) - Resolved issues around PyYAML working in Python 3.7.Configuration
📅 Schedule: Branch creation - "" in timezone America/Lima, 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.