CVE-2020-1747: Improper Input Validation in PyYAML

CVE-2020-1747 · Severity: low · CVSS 3.1 · Published 2020-03-24

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.

Technologies: PyYAML (PyPI). Vendors: PyPI.

Quick answers

Is CVE-2020-1747 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2020-1747 being exploited in the wild.
How severe is CVE-2020-1747?
Low severity, with a CVSS score of 3.1, published 24 March 2020.
Which products and versions are affected?
PyYAML (PyPI) ECOSYSTEM:introduced=5.1,fixed=5.3.1, ECOSYSTEM:introduced=5.1b7,fixed=5.3.1.
Is there a fix for CVE-2020-1747?
Yes. PyYAML (PyPI): upgrade to 5.3.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2020-1747?
Check whether you run PyYAML (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • PyYAML (PyPI): upgrade to 5.3.1 or later
    pip install "PyYAML>=5.3.1"

Affected products

  • PyYAML (PyPI) ECOSYSTEM:introduced=5.1,fixed=5.3.1, ECOSYSTEM:introduced=5.1b7,fixed=5.3.1

Identifiers

  • CVE-2020-1747
  • GHSA-6757-jp84-gxfx
  • PYSEC-2020-96

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.