Is CVE-2020-1733 being actively exploited?

It is not currently in CISA's KEV catalog. Its EPSS exploitation probability is 0%.

What products does CVE-2020-1733 affect?

Tracked products affected include Ansible. Check the version you run to see whether it is affected.

How do I fix CVE-2020-1733?

Apply the vendor fix in your normal patch cycle. Upgrade affected products to a fixed version.

CVE-2020-1733

Q: What is CVE-2020-1733?

CVE-2020-1733 is a medium-severity software vulnerability (CWE-377) with a CVSS score of 5. A race condition flaw was found in Ansible Engine 2.7.17 and prior, 2.8.9 and prior, 2.9.6 and prior when running a playbook with an unprivileged become user. When Ansible needs to run a module with become user, the temporary directory is c

MEDIUM severity · CVSS 5 · CWE-377

5CVSS MEDIUM

Summary

A race condition flaw was found in Ansible Engine 2.7.17 and prior, 2.8.9 and prior, 2.9.6 and prior when running a playbook with an unprivileged become user. When Ansible needs to run a module with become user, the temporary directory is created in /var/tmp. This directory is created with "umask 77 && mkdir -p <dir>"; this operation does not fail if the directory already exists and is owned by another user. An attacker could take advantage to gain control of the become user as the target directory can be retrieved by iterating '/proc/<pid>/cmdline'.

Impact & exploitability

Attack vectorLocal

Attack complexityHigh

Privileges requiredLow

User interactionRequired

Confidentiality impactLow

Integrity impactLow

Availability impactLow

Exploit probability (EPSS)0%

CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:C/C:L/I:L/A:L

Affected products we track (1)

Ansible

Recommendation

Apply the vendor fix in your normal patch cycle. Open any affected product above for its exact safe version.

CVE-2020-1733

Summary

Impact & exploitability

Affected products we track (1)

Recommendation

Additional information