Skip to content
Noroxi
NVD / CVE Program· CNA redhat

CVE-2020-1733: 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 unprivi

Noroxi assessment

Priority: Monitor (action score 20/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.40% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. A user must open a link or visit a page. Special conditions such as timing or configuration are required.
  • Fixed version: ansible (Alpine:v3.10) 2.8.11-r0; ansible (Alpine:v3.11) 2.9.7-r0; ansible-base (Alpine:v3.13) 2.9.7-r0.

Low priority for now. Upgrade to ansible (Alpine:v3.10) 2.8.11-r0; ansible (Alpine:v3.11) 2.9.7-r0; ansible-base (Alpine:v3.13) 2.9.7-r0 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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'.

MediumCVSS 5.0 · v3.1—No exploit Fix available
Published
Mar 11, 2020
Updated
Jun 16, 2026
EPSS
0.4% · 34th percentile

Report tools

JSON

Action score

20

Monitor

Low priority for now.

CVSS
20 / 40 · 5.0 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.4%

CNA vs NVD score

NVD
5.0
CNA · redhat
5.0
agree

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2020-1733

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for redhat records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
redhatansible
redhatansible tower
redhatcloudforms management engine
redhatopenstack
fedoraprojectfedora
debiandebian linux

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • debian debian linux10.0
  • debian debian linux8.0
  • fedoraproject fedora30
  • fedoraproject fedora31
  • fedoraproject fedora32
  • redhat ansibleup to 2.7.16 inclusive
  • redhat ansible2.8.0 and later · before 2.8.8
  • redhat ansible2.9.0 and later · up to 2.9.5 inclusive
  • redhat ansible tower3.6.0 and later · up to 3.6.3 inclusive
  • redhat ansible tower3.5.0 and later · up to 3.5.5 inclusive
  • redhat ansible tower3.3.5 and later · up to 3.4.5 inclusive
  • redhat ansible towerup to 3.3.4 inclusive
  • redhat cloudforms management engine5.0
  • redhat openstack13

Versions reported by the vendor

Affected version ranges reported by the assigning authority (redhat). Independent of NVD's CPE analysis and usually ahead of it.

  • Red Hat Ansible

    • 2.7.17 and prior, 2.8.9 and prior, 2.9.6 and prioraffected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Alpine:v3.10ansiblefrom 2.8.0 · before 2.8.11-r02.8.11-r0
Alpine:v3.11ansiblefrom 2.8.0 · before 2.9.7-r02.9.7-r0
Alpine:v3.13ansible-basebefore 2.9.7-r02.9.7-r0
Alpine:v3.9ansiblefrom 2.8.0 · before 2.7.17-r02.7.17-r0
Debian:10ansiblebefore 2.7.7+dfsg-1+deb10u12.7.7+dfsg-1+deb10u1
Debian:12ansiblebefore 2.9.7+dfsg-12.9.7+dfsg-1
Debian:8ansiblebefore 1.7.2+dfsg-2+deb8u31.7.2+dfsg-2+deb8u3
openSUSE:Leap 15.3ansiblebefore 2.9.21-bp153.2.3.12.9.21-bp153.2.3.1
PyPIansiblefrom 2.8.0 · before 2.8.82.8.8
PyPIansiblefrom 2.8.0a1 · before 2.8.112.8.11
PyPIansiblefrom 2.9.0 · before 2.9.62.9.6
PyPIansiblefrom 2.9.0a1 · before 2.9.72.9.7
PyPIansiblebefore 2.7.172.7.17
Red Hat:ansible_engine:2.7::el7ansiblebefore 0:2.7.17-1.el7ae0:2.7.17-1.el7ae
Red Hat:ansible_engine:2.8::el7ansiblebefore 0:2.8.11-1.el7ae0:2.8.11-1.el7ae
Red Hat:ansible_engine:2.8::el8ansiblebefore 0:2.8.11-1.el8ae0:2.8.11-1.el8ae
Red Hat:ansible_engine:2.9::el7ansiblebefore 0:2.9.7-1.el7ae0:2.9.7-1.el7ae
Red Hat:ansible_engine:2.9::el7ansible-testbefore 0:2.9.7-1.el7ae0:2.9.7-1.el7ae
Red Hat:ansible_engine:2.9::el8ansiblebefore 0:2.9.7-1.el8ae0:2.9.7-1.el8ae
Red Hat:ansible_engine:2.9::el8ansible-testbefore 0:2.9.7-1.el8ae0:2.9.7-1.el8ae
SUSE:OpenStack Cloud 7ansiblebefore 2.2.3.0-17.22.2.3.0-17.2
SUSE:OpenStack Cloud 7crowbar-corebefore 4.0+git.1600767499.0615a418f-9.69.34.0+git.1600767499.0615a418f-9.69.3
SUSE:OpenStack Cloud 7crowbar-openstackbefore 4.0+git.1599037255.25b759234-9.74.44.0+git.1599037255.25b759234-9.74.4
SUSE:OpenStack Cloud 7grafanabefore 6.7.4-1.17.16.7.4-1.17.1

+30

Same product

redhat: all records

Other highest-scoring records for the same primary product.

  • CVE-2014-4678The safe_eval function in Ansible before 1.6.4 does not properly restrict the code subset, which allows remote attackers to execute arbitrar
    41Plan
  • CVE-2014-4657The safe_eval function in Ansible before 1.5.4 does not properly restrict the code subset, which allows remote attackers to execute arbitrar
    40Plan
  • CVE-2014-4967Multiple argument injection vulnerabilities in Ansible before 1.6.7 allow remote attackers to execute arbitrary code by leveraging access to
    40Plan

Published before and after this one in the same product

  • ← EarlierCVE-2014-4658Feb 20, 2020 · The vault subsystem in Ansible before 1.5.5 does not set the umask before creation or modification of a vault file, which allows local users
    22Monitor
  • ← EarlierCVE-2014-4659Feb 20, 2020 · Ansible before 1.5.5 sets 0644 permissions for sources.list, which might allow local users to obtain sensitive credential information in opp
    22Monitor
  • Later →CVE-2020-1739Mar 12, 2020 · A flaw was found in Ansible 2.7.16 and prior, 2.8.8 and prior, and 2.9.5 and prior when a password is set with the argument "password" of sv
    15Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
alpine:ansible2.8.11-r0 · Alpine:v3.10Package registry (OSV)
alpine:ansible-base2.9.7-r0 · Alpine:v3.13Package registry (OSV)
debian:ansible2.9.7+dfsg-1 · Debian:12Package registry (OSV)
opensuse:ansible2.9.21-bp153.2.3.1 · openSUSE:Leap 15.3Package registry (OSV)
PyPI:ansible2.7.17Package registry (OSV)
PyPI:ansible2.8.11Package registry (OSV)
PyPI:ansible2.8.8Package registry (OSV)
PyPI:ansible2.9.6Package registry (OSV)
PyPI:ansible2.9.7Package registry (OSV)
red hat:ansible0:2.9.7-1.el7ae · Red Hat:ansible_engine:2.9::el7Package registry (OSV)
red hat:ansible-test0:2.9.7-1.el7ae · Red Hat:ansible_engine:2.9::el7Package registry (OSV)
suse:ansible2.2.3.0-17.2 · SUSE:OpenStack Cloud 7Package registry (OSV)
suse:ansible2.9.21-bp153.2.3.1 · SUSE:Package Hub 15 SP3Package registry (OSV)
suse:crowbar-core4.0+git.1600767499.0615a418f-9.69.3 · SUSE:OpenStack Cloud 7Package registry (OSV)
suse:crowbar-openstack4.0+git.1599037255.25b759234-9.74.4 · SUSE:OpenStack Cloud 7Package registry (OSV)
suse:grafana6.7.4-1.17.1 · SUSE:OpenStack Cloud 7Package registry (OSV)
suse:grafana-natel-discrete-panel0.0.9-1.6.5 · SUSE:OpenStack Cloud 7Package registry (OSV)
suse:openstack-aodh3.0.5~dev2-2.11.2 · SUSE:OpenStack Cloud 7Package registry (OSV)
suse:openstack-aodh-doc3.0.5~dev2-2.11.1 · SUSE:OpenStack Cloud 7Package registry (OSV)
suse:openstack-barbican3.0.1~dev9-2.12.4 · SUSE:OpenStack Cloud 7Package registry (OSV)
suse:openstack-barbican-doc3.0.1~dev9-2.12.2 · SUSE:OpenStack Cloud 7Package registry (OSV)
suse:openstack-cinder9.1.5~dev6-4.28.1 · SUSE:OpenStack Cloud 7Package registry (OSV)
suse:openstack-cinder-doc9.1.5~dev6-4.28.1 · SUSE:OpenStack Cloud 7Package registry (OSV)
suse:openstack-gnocchi3.0.7~dev1-2.8.2 · SUSE:OpenStack Cloud 7Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • A user must open a link or visit a page.
  • Special conditions such as timing or configuration are required.

If successful

Confidentiality
low · data can be read
Integrity
low · data or configuration can be modified
Availability
low · the service can be disrupted

Impact can extend beyond the vulnerable component (scope changes).

Attack vector
Local
Attack complexity
High
Privileges required
Low
User interaction
Required
Scope
Changed
Confidentiality impact
Low
Integrity impact
Low
Availability impact
Low

Weakness class (CWE)

CWE-377 · Insecure Temporary File

CVSS vector

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

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

ATT&CK techniques

—

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (6 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records