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

A vulnerability was found in Ansible engine 2.x up to 2.8 and Ansible tower 3.x up to 3.5.

A vulnerability was found in Ansible engine 2.x up to 2.8 and Ansible tower 3.x up to 3.5. When a module has an argument_spec with sub parameters marked as no_log, passing an invalid parameter name to the module will cause the task to fail before the no_log options in the sub parameters are processed. As a result, data in the sub parameter fields will not be masked and will be displayed if Ansible is run with increased verbosity and present in the module invocation arguments for the task.

MediumCVSS 5.5 · v3.1—No exploit Fix available
Published
Oct 14, 2019
Updated
Jun 16, 2026
EPSS
0.4% · 34th percentile
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

Report tools

JSON

Action score

22

Monitor

Low priority for now.

CVSS
22 / 40 · 5.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.4%

CNA vs NVD score

NVD
5.5
CNA · redhat
7.3
1.8 point gap

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

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

Affected systems

VendorProduct
redhatansible engine
redhatansible tower

Affected versions

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

  • redhat ansible engine2.0 and later · up to 2.8.0 inclusive
  • redhat ansible tower3.0 and later · up to 3.5.0 inclusive

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

    • ansible_engine-2.x up to 2.8, ansible_tower-3.x up to 3.5affected

Package-level exposure

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

EcosystemPackageAffected rangeFix
Alpine:v3.10ansiblebefore 2.8.6-r02.8.6-r0
Alpine:v3.13ansible-basebefore 2.8.6-r02.8.6-r0
Alpine:v3.8ansiblebefore 2.6.20-r02.6.20-r0
Alpine:v3.9ansiblebefore 2.7.14-r02.7.14-r0
Debian:12ansiblebefore 2.8.6+dfsg-12.8.6+dfsg-1
openSUSE:Leap 15.1ansiblebefore 2.9.6-lp151.2.7.12.9.6-lp151.2.7.1
openSUSE:Tumbleweedansible-10before 10.6.0-1.110.6.0-1.1
openSUSE:Tumbleweedansible-11before 11.11.0-1.111.11.0-1.1
openSUSE:Tumbleweedansible-12before 12.2.0-1.112.2.0-1.1
openSUSE:Tumbleweedansible-13before 13.7.0-1.113.7.0-1.1
openSUSE:Tumbleweedansible-9before 9.8.0-1.19.8.0-1.1
PyPIansiblefrom 2.0 · before 2.6.202.6.20
PyPIansiblefrom 2.0 · before 2.8.12.8.1
PyPIansiblefrom 2.7.0a1 · before 2.7.142.7.14
PyPIansiblefrom 2.8.0a1 · before 2.8.62.8.6
PyPIansiblefrom 2.9.0a1 · before 2.9.0rc42.9.0rc4
Red Hat:ansible_engine:2.6::el7ansiblebefore 0:2.6.20-1.el7ae0:2.6.20-1.el7ae
Red Hat:ansible_engine:2.7::el7ansiblebefore 0:2.7.14-1.el7ae0:2.7.14-1.el7ae
Red Hat:ansible_engine:2.8::el7ansiblebefore 0:2.8.6-1.el7ae0:2.8.6-1.el7ae
Red Hat:ansible_engine:2.8::el8ansiblebefore 0:2.8.6-1.el8ae0:2.8.6-1.el8ae
SUSE:Package Hub 15 SP1ansiblebefore 2.9.6-bp151.3.6.12.9.6-bp151.3.6.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.6-r0 · Alpine:v3.10Package registry (OSV)
alpine:ansible-base2.8.6-r0 · Alpine:v3.13Package registry (OSV)
debian:ansible2.8.6+dfsg-1 · Debian:12Package registry (OSV)
opensuse:ansible2.9.6-lp151.2.7.1 · openSUSE:Leap 15.1Package registry (OSV)
opensuse:ansible-1010.6.0-1.1 · openSUSE:TumbleweedPackage registry (OSV)
opensuse:ansible-1111.11.0-1.1 · openSUSE:TumbleweedPackage registry (OSV)
opensuse:ansible-1212.2.0-1.1 · openSUSE:TumbleweedPackage registry (OSV)
opensuse:ansible-1313.7.0-1.1 · openSUSE:TumbleweedPackage registry (OSV)
opensuse:ansible-99.8.0-1.1 · openSUSE:TumbleweedPackage registry (OSV)
PyPI:ansible2.6.20Package registry (OSV)
PyPI:ansible2.7.14Package registry (OSV)
PyPI:ansible2.8.1Package registry (OSV)
PyPI:ansible2.8.6Package registry (OSV)
PyPI:ansible2.9.0rc4Package registry (OSV)
red hat:ansible0:2.6.20-1.el7ae · Red Hat:ansible_engine:2.6::el7Package 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.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
none
Availability
none
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
None
Availability impact
None

CVSS vector

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

nvd-primary

Noroxi analysis

No Noroxi analysis for this record yet

We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

We use this product, ask for help

Change log

  1. Fix✗ → ✓

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

References

All records