Skip to content
Noroxi
CVE-2019-14905· NVD / CVE Program· CNA redhat

A vulnerability was found in Ansible Engine versions 2.9.x before 2.9.3, 2.8.x before 2.8.8, 2.7.x before 2.7.16 and earlier, where in Ansib

Noroxi assessment

Priority: Monitor (action score 22/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.71% (FIRST EPSS); higher than 52.6% of all records.
  • Someone with local access to the system can trigger it. Administrator privileges are required. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: ansible (Alpine:v3.10) 2.8.8-r0; ansible (Alpine:v3.11) 2.9.3-r0; ansible-base (Alpine:v3.13) 2.9.3-r0.

Low priority for now. Upgrade to ansible (Alpine:v3.10) 2.8.8-r0; ansible (Alpine:v3.11) 2.9.3-r0; ansible-base (Alpine:v3.13) 2.9.3-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 vulnerability was found in Ansible Engine versions 2.9.x before 2.9.3, 2.8.x before 2.8.8, 2.7.x before 2.7.16 and earlier, where in Ansible's nxos_file_copy module can be used to copy files to a flash or bootflash on NXOS devices. Malicious code could craft the filename parameter to perform OS command injections. This could result in a loss of confidentiality of the system among other issues.

MediumCVSS 5.6 · v3.1—No exploit Fix available
Published
Mar 31, 2020
Updated
Jun 16, 2026
EPSS
0.7% · 52th percentile

Report tools

JSON

Action score

22

Monitor

Low priority for now.

CVSS
22 / 40 · 5.6 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.7%

CNA vs NVD score

NVD
5.6
CNA · redhat
7.3
1.7 point gap

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

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-2019-14905

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.

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 engine
redhatansible tower
redhatceph storage
redhatcloudforms management engine
redhatopenstack
fedoraprojectfedora
opensusebackports sle
opensuseleap

Affected versions

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

  • fedoraproject fedora30
  • opensuse backports sle15.0
  • opensuse leap15.1
  • redhat ansible engine2.7.0 and later · before 2.7.16
  • redhat ansible engine2.8.0 and later · before 2.8.8
  • redhat ansible engine2.9.0 and later · before 2.9.3
  • redhat ansible tower3.0.0
  • redhat ceph storage3.0
  • 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.9.x before 2.9.3, 2.8.x before 2.8.8, 2.7.x before 2.7.16, 2.7.x and earlieraffected

Package-level exposure

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

EcosystemPackageAffected rangeFix
Alpine:v3.10ansiblebefore 2.8.8-r02.8.8-r0
Alpine:v3.11ansiblebefore 2.9.3-r02.9.3-r0
Alpine:v3.13ansible-basebefore 2.9.3-r02.9.3-r0
Alpine:v3.9ansiblebefore 2.7.16-r02.7.16-r0
Debian:12ansiblebefore 2.9.4+dfsg-12.9.4+dfsg-1
openSUSE:Leap 15.1ansiblebefore 2.9.6-lp151.2.7.12.9.6-lp151.2.7.1
PyPIansiblefrom 2.7.0 · before 2.7.162.7.16
PyPIansiblefrom 2.7.0a1 · before 2.7.162.7.16
PyPIansiblefrom 2.8.0 · before 2.8.82.8.8
PyPIansiblefrom 2.8.0a1 · before 2.8.82.8.8
PyPIansiblefrom 2.9.0 · before 2.9.32.9.3
PyPIansiblefrom 2.9.0a1 · before 2.9.32.9.3
Red Hat:ansible_engine:2.7::el7ansiblebefore 0:2.7.16-1.el7ae0:2.7.16-1.el7ae
Red Hat:ansible_engine:2.8::el7ansiblebefore 0:2.8.8-1.el7ae0:2.8.8-1.el7ae
Red Hat:ansible_engine:2.8::el8ansiblebefore 0:2.8.8-1.el8ae0:2.8.8-1.el8ae
Red Hat:ansible_engine:2.9::el7ansiblebefore 0:2.9.4-1.el7ae0:2.9.4-1.el7ae
Red Hat:ansible_engine:2.9::el7ansible-testbefore 0:2.9.4-1.el7ae0:2.9.4-1.el7ae
Red Hat:ansible_engine:2.9::el8ansiblebefore 0:2.9.4-1.el8ae0:2.9.4-1.el8ae
Red Hat:ansible_engine:2.9::el8ansible-testbefore 0:2.9.4-1.el8ae0:2.9.4-1.el8ae
SUSE:Package Hub 15 SP1ansiblebefore 2.9.6-bp151.3.6.12.9.6-bp151.3.6.1
SUSE:Package Hub 15 SP3ansiblebefore 2.9.21-bp153.2.3.12.9.21-bp153.2.3.1
SUSE:Package Hub 15 SP3ansiblebefore 2.9.21-bp153.2.3.12.9.21-bp153.2.3.1

Other highest-scoring records for the same primary product.

  • CVE-2021-20228A flaw was found in the Ansible Engine 2.9.18, where sensitive info is not masked by default and is not protected by the no_log feature when
    31Monitor
  • CVE-2020-1737A flaw was found in Ansible 2.7.17 and prior, 2.8.9 and prior, and 2.9.6 and prior when using the Extract-Zip function from the win_unzip mo
    31Monitor
  • CVE-2019-14846In Ansible, all Ansible Engine versions up to ansible-engine 2.8.5, ansible-engine 2.7.13, ansible-engine 2.6.19, were logging at the DEBUG
    31Monitor
  • CVE-2018-16837Ansible "User" module leaks any data which is passed on as a parameter to ssh-keygen.
    31Monitor
  • CVE-2018-10875A flaw was found in ansible.
    31Monitor
  • CVE-2018-10874In ansible it was found that inventory variables are loaded from current working directory when running ad-hoc command which are under attac
    31Monitor

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.8-r0 · Alpine:v3.10Package registry (OSV)
alpine:ansible-base2.9.3-r0 · Alpine:v3.13Package registry (OSV)
debian:ansible2.9.4+dfsg-1 · Debian:12Package registry (OSV)
opensuse:ansible2.9.21-bp153.2.3.1 · openSUSE:Leap 15.3Package registry (OSV)
opensuse:ansible2.9.6-lp151.2.7.1 · openSUSE:Leap 15.1Package registry (OSV)
PyPI:ansible2.7.16Package registry (OSV)
PyPI:ansible2.8.8Package registry (OSV)
PyPI:ansible2.9.3Package registry (OSV)
red hat:ansible0:2.9.4-1.el7ae · Red Hat:ansible_engine:2.9::el7Package registry (OSV)
red hat:ansible-test0:2.9.4-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)
suse:ansible2.9.6-bp151.3.6.1 · SUSE:Package Hub 15 SP1Package 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.

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

If successful

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

CVSS vector

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

nvd-primary

Change log

  1. Fix✗ → ✓

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

References

All records