Skip to content
Noroxi
NVD / CVE Program· CNA redhat

CVE-2020-10684: A flaw was found in Ansible Engine, all versions 2.7.x, 2.8.x and 2.9.x prior to 2.7.17, 2.8.9 and 2.9.6 respectively, when using ansible_fa

Noroxi assessment

Priority: Monitor (action score 28/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.33% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: ansible (Debian:10) 2.7.7+dfsg-1+deb10u1; ansible (Debian:12) 2.9.7+dfsg-1; ansible (openSUSE:Leap 15.3) 2.9.21-bp153.2.3.1.

Low priority for now. Upgrade to ansible (Debian:10) 2.7.7+dfsg-1+deb10u1; ansible (Debian:12) 2.9.7+dfsg-1; ansible (openSUSE:Leap 15.3) 2.9.21-bp153.2.3.1 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 flaw was found in Ansible Engine, all versions 2.7.x, 2.8.x and 2.9.x prior to 2.7.17, 2.8.9 and 2.9.6 respectively, when using ansible_facts as a subkey of itself and promoting it to a variable when inject is enabled, overwriting the ansible_facts after the clean. An attacker could take advantage of this by altering the ansible_facts, such as ansible_hosts, users and any other key data which would lead into privilege escalation or code injection.

HighCVSS 7.1 · v3.1—No exploit Fix available
Published
Mar 24, 2020
Updated
Jun 16, 2026
EPSS
0.3% · 26th percentile

Report tools

JSON

Action score

28

Monitor

Low priority for now.

CVSS
28 / 40 · 7.1 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.3%

CNA vs NVD score

NVD
7.1
CNA · redhat
7.9
0.8 point gap

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

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-10684

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
redhatopenstack
debiandebian linux
fedoraprojectfedora

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
  • fedoraproject fedora30
  • fedoraproject fedora31
  • fedoraproject fedora32
  • redhat ansible2.7.0 and later · before 2.7.17
  • redhat ansible2.8.0 and later · before 2.8.9
  • redhat ansible2.9.0 and later · before 2.9.6
  • 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 towerup to 3.3.5 inclusive
  • redhat openstack10
  • 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

    • all Ansible 2.7.x versions prior to 2.7.17, all Ansible 2.8.x versions prior to 2.8.9, all Ansible 2.9.x versions prior to 2.9.6affected

Package-level exposure

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

EcosystemPackageAffected rangeFix
Debian:10ansiblebefore 2.7.7+dfsg-1+deb10u12.7.7+dfsg-1+deb10u1
Debian:12ansiblebefore 2.9.7+dfsg-12.9.7+dfsg-1
openSUSE:Leap 15.3ansiblebefore 2.9.21-bp153.2.3.12.9.21-bp153.2.3.1
PyPIansiblefrom 2.7.0 · before 2.7.172.7.17
PyPIansiblefrom 2.7.0a1 · before 2.7.172.7.17
PyPIansiblefrom 2.8.0 · before 2.8.92.8.9
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
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:Package Hub 15 SP3ansiblebefore 2.9.21-bp153.2.3.12.9.21-bp153.2.3.1

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-2020-1738Mar 16, 2020 · A flaw was found in Ansible Engine when the module package or service is used and the parameter 'use' is not specified.
    15Monitor
  • ← EarlierCVE-2020-1740Mar 16, 2020 · A flaw was found in Ansible Engine when using Ansible Vault for editing encrypted files.
    18Monitor
  • Later →CVE-2020-10744May 15, 2020 · An incomplete fix was found for the fix of the flaw CVE-2020-1733 ansible: insecure temporary directory when running become_user from become
    20Monitor

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
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.9Package 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.9.21-bp153.2.3.1 · SUSE:Package Hub 15 SP3Package 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.

No history yet (it accumulates with the daily EPSS job).

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.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
none
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
High
Availability impact
High

Weakness class (CWE)

CWE-94 · Improper Control of Generation of Code ('Code Injection')

CVSS vector

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

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.

Change log

  1. Fix✗ → ✓

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

References

Show all references (5 more)

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

All records