CriticalGHSA-3pqx-4fqf-j49fCVE-2019-20477PYSEC-2020-176

Deserialization of Untrusted Data in PyYAML

Published 20 Apr 2021 · Updated 25 Oct 2024

Is your project on an affected pyyaml?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Python apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Affected package

pyyamlPyPI
Affected
>=5.1 <5.2
Fixed in
5.2
Update to the fixed version for your release line, for example:pip install 'pyyaml>=5.2'

Details

PyYAML 5.1 through 5.1.2 has insufficient restrictions on the load and load_all functions because of a class deserialization issue, e.g., Popen is a class in the subprocess module. NOTE: this issue exists because of an incomplete fix for CVE-2017-18342.

Is GHSA-3pqx-4fqf-j49f in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected pyyaml, and gives you the command that fixes it.

More advisories for pyyaml

  • CriticalCVE-2020-1747Improper Input Validation in PyYAML · 20 Apr 2021
  • CriticalCVE-2020-14343Improper Input Validation in PyYAML · 25 Mar 2021
  • CriticalCVE-2017-18342PyYAML insecurely deserializes YAML strings leading to arbitrary code execution · 4 Jan 2019
pyyaml security overview

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.