CVE-2020-10744: Exposure of Resource to Wrong Sphere and Insecure Temporary File in Ansible

CVE-2020-10744 · Severity: low · CVSS 3.1 · Published 2020-05-15

An incomplete fix was found for the fix of the flaw CVE-2020-1733 ansible: insecure temporary directory when running become_user from become directive. The provided fix is insufficient to prevent the race condition on systems using ACLs and FUSE filesystems. Ansible Engine 2.7.18, 2.8.12, and 2.9.9 as well as previous versions are affected and Ansible Tower 3.4.5, 3.5.6 and 3.6.4 as well as previous versions are affected.

Technologies: ansible (PyPI). Vendors: PyPI.

Quick answers

Is CVE-2020-10744 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2020-10744 being exploited in the wild.
How severe is CVE-2020-10744?
Low severity, with a CVSS score of 3.1, published 15 May 2020.
Which products and versions are affected?
ansible (PyPI) ECOSYSTEM:introduced=2.10.0a1,fixed=2.10.0rc1, ECOSYSTEM:introduced=2.7.0,fixed=2.8.0a1,introduced=2.8.0,fixed=2.8.13,introduced=2.9.0,fixed=2.9.10.
Is there a fix for CVE-2020-10744?
Yes. ansible (PyPI): upgrade to 2.10.0rc1, 2.9.10 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2020-10744?
Check whether you run ansible (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

  • ansible (PyPI): upgrade to 2.10.0rc1, 2.9.10 or later
    pip install "ansible>=2.10.0rc1"

Affected products

  • ansible (PyPI) ECOSYSTEM:introduced=2.10.0a1,fixed=2.10.0rc1, ECOSYSTEM:introduced=2.7.0,fixed=2.8.0a1,introduced=2.8.0,fixed=2.8.13,introduced=2.9.0,fixed=2.9.10

Identifiers

  • CVE-2020-10744
  • GHSA-vp9j-rghq-8jhh
  • PYSEC-2020-208

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