CVE-2019-14858

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.

Published: 2019-10-14 Last update: 2024-11-21 Assigner: [email protected] Source: [email protected]

Conclusion & alert: CVE-2019-14858 is rated Low Risk (30.2/100): CVSS Medium severity, with low exploitation likelihood (EPSS 0.08%). Mandatory action: Monitor for updates and reassess as exploit intelligence or EPSS changes.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2019-14858

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-01 0.04% 0.08% +0.04%
2 2026-04-21 0.06% 0.04% -0.02%
3 2026-01-06 0.06%

Full EPSS history (16 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2019-14858

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
5.5 3.1 MEDIUM
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:N)
Service keeps running; no real outage angle.
1.8 3.6 [email protected]
7.3 3.0 HIGH
CVSS:3.0/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:R)
A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
1.3 5.9 [email protected]
2.1 2.0 LOW
AV:L/AC:L/Au:N/C:P/I:N/A:N Click to expand
Access vector (AV:L)
Requires local access to the target system.
Access complexity (AC:L)
Exploitation conditions are straightforward and predictable.
Authentication (AU:N)
No authentication is required.
Confidentiality impact (C:P)
Partial confidentiality impact.
Integrity impact (I:N)
No integrity impact.
Availability impact (A:N)
No availability impact.
3.9 2.9 [email protected]

Weakness enumeration for CVE-2019-14858

GitHub Security Advisory for CVE-2019-14858

GHSA-h653-95qw-h2mp · Severity: medium · Ecosystem: pip — Ansible leaks sensitive information to logs when told not to

OS Trackers for CVE-2019-14858

vendor priority summary link
alpine medium CVE-2019-14858: 2 source package rows (ansible, ansible-base); 5 state rows across 5 repos (3.10-main, 3.11-main, 3.12-main, edge-community, edge-main); fixed 5, open 0. https://security.alpinelinux.org/vuln/CVE-2019-14858
debian not yet assigned CVE-2019-14858 not yet assigned priority: Debian including 1 source packages (ansible), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5. https://security-tracker.debian.org/tracker/CVE-2019-14858
redhat medium https://access.redhat.com/security/cve/CVE-2019-14858
suse low CVE-2019-14858 severity low: SUSE including 119 source package names (ansible-10-10.6.0-1.1, ansible-11-11.11.0-1.1, …), 250 product×package rows across 10 product lines (HPE Helion OpenStack 8, HPE Helion OpenStack Cloud 8, … (10 product lines)): Fixed 246, Known Not Affected 4. https://www.suse.com/security/cve/CVE-2019-14858/
ubuntu low CVE-2019-14858 low priority: Ubuntu including 1 source packages (ansible), 18 status rows across 18 suites (bionic, disco, eoan, focal, groovy, hirsute, impish, jammy, kinetic, lunar, mantic, noble, oracular, plucky, questing, trusty, upstream, xenial): not-affected 14, ignored 2, needed 1, released 1. https://ubuntu.com/security/CVE-2019-14858

Affected software / configurations for CVE-2019-14858

Vendor Product Version Raw CPE
redhat ansible_engine >= 2.0, <= 2.8.0 cpe:2.3:a:redhat:ansible_engine:*:*:*:*:*:*:*:*
redhat ansible_tower >= 3.0, <= 3.5.0 cpe:2.3:a:redhat:ansible_tower:*:*:*:*:*:*:*:*

References for CVE-2019-14858

cvelogic Threat Intelligence