CVE-2019-14858

What it is

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.

At a glance

Exploitability

Can be exploited locally on the machine with a low-privilege account. High risk of data exposure.

Exploit odds

0.4% chance of exploitation in the next 30 days (EPSS).

Fix

No patch or advisory is linked yet. Look at mitigations or restrict exposure.

Timeline

1. 2019-10-14 15:15 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-06-17 02:19 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 0.4% in the next 30 days (EPSS).
• Severity: 5.5 MEDIUM (CVSS).
• Fix: none linked yet, which raises it.

Details

Published

2019-10-14 15:15 UTC

Last modified

2026-06-17 02:19 UTC

Exploit probability

0.4% · EPSS, next 30 days

Weakness

CWE-117

Record status

Modified

Affected

• Redhat Ansible Engine ≤ 2.8.0
• Redhat Ansible Tower ≤ 3.5.0

Attack profile CVSS 3.1 · 5.5

Attack vector

Local

Complexity

Low

Privileges needed

Low

User interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

None

Availability

None

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2019-14858.md and follow it. Check whether this project is affected by CVE-2019-14858. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge