Skip to content
Fencer Intel
medium 5.0

CVE-2020-10744 json

Exposure of Resource to Wrong Sphere and Insecure Temporary File in Ansible

published 6y ago modified 4mo ago also GHSA-vp9j-rghq-8jhh , PYSEC-2020-208 , EUVD-2020-0020

cvss
5.0
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.3%
EPSS 0.3% chance of exploitation in 30 days, percentile 17%
public exploits
0
none known

Summary

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.

Patch / fix

  • pypi ansible 2.8.0a1, 2.8.13, 2.9.10, 2.9.12, 2.10.0rc1
  • ansible Debian 14, Debian 13, Debian 12 2.9.13+dfsg-1

debian advisories DEBIAN-CVE-2020-10744

  • ansible Ubuntu Pro 16.04 LTS 2.0.0.2-2ubuntu1.3+esm1
  • ansible Ubuntu Pro 18.04 LTS 2.5.1+dfsg-1ubuntu0.1+esm1
  • ansible Ubuntu Pro 20.04 LTS 2.9.6+dfsg-1ubuntu0.1~esm1

ubuntu advisories UBUNTU-CVE-2020-10744

Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

  • ansible openSUSE Leap 15.5, Manager Proxy Module 4.3, Manager Client Tools 15 2.9.27-150000.1.17.2
  • grafana Manager Client Tools 15 9.5.18-150000.1.63.2
  • spacecmd openSUSE Leap 15.5, Manager Client Tools 15 4.3.27-150000.3.116.2
  • mgr-daemon Manager Client Tools 15 4.3.9-150000.1.47.2
  • spacewalk-koan Manager Client Tools 15 4.3.6-150000.3.33.2
  • dracut-saltboot openSUSE Leap 15.5, Manager Client Tools for SLE Micro 5, Manager Client Tools 15 0.1.1710765237.46af599-150000.1.53.2
  • POS_Image-JeOS7 openSUSE Leap 15.5, Manager Client Tools 15 0.1.1710765237.46af599-150000.1.21.2
  • uyuni-common-libs Manager Client Tools 15 4.3.10-150000.1.39.2

suse advisories SUSE-SU-2024:1509-1SUSE-SU-2020:3309-1SUSE-SU-2020:2911-1

Is CVE-2020-10744 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2020-10744 updated cvss 5.0

ansible: incomplete fix for CVE-2020-1733

  • Red Hat Ansible Engine 2 ansible, ansible-test
    affected: workaround, no fix available “Currently, there is no mitigation for this issue.”
  • Red Hat Ansible Tower 3 ansible Red Hat Ceph Storage 2 ansible Red Hat Ceph Storage 3 ansible Red Hat OpenStack Platform 10 (Newton) ansible Red Hat OpenStack Platform 13 (Queens) ansible Red Hat Storage 3 ansible
    affected: workaround, no fix planned “Currently, there is no mitigation for this issue.”

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

0.26% chance of exploitation in the next 30 days, higher than 17% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CNA 3.1 5.0 CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:C/C:L/I:L/A:L
NVD 3.1 5.0 CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:C/C:L/I:L/A:L
NVD 2.0 3.7 AV:L/AC:H/Au:N/C:P/I:P/A:P
GitHub 3.1 5.0 CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:C/C:L/I:L/A:L

Affected packages

ecosystem package affected fixed in
pypi ansible
>=2.10.0a1, <2.10.0rc1
<2.9.12
>=2.7.0, <2.8.0a1
>=2.8.0, <2.8.13
>=2.9.0, <2.9.10
2.10.0rc1
2.9.12
2.8.0a1
2.8.13
2.9.10

Affected products

  • Red Hat ansible

Classification

Weakness
  • CWE-377 DEPRECATED: Insecure Temporary File
  • CWE-362 Concurrent Execution using Shared Resource with Improper Synchronization
  • CWE-668 Exposure of Resource to Wrong Sphere

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.