Summary
Ansible leaks sensitive information to logs when told not to
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.
Impact
CVE-2019-14858 has a CVSS score of 5.5 (Medium). The vector is requires local access, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (2.9.0rc4, 2.8.6, 2.7.14, 2.6.20); upgrading removes the vulnerable code path.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
ansible to 2.9.0rc4 or later; ansible to 2.8.6 or later; ansible to 2.7.14 or later; ansible to 2.6.20 or later
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is CVE-2019-14858? CVE-2019-14858 is a medium-severity security vulnerability in ansible (pip), affecting versions >= 2.9.0a1, < 2.9.0rc4. It is fixed in 2.9.0rc4, 2.8.6, 2.7.14, 2.6.20.
- How severe is CVE-2019-14858? CVE-2019-14858 has a CVSS score of 5.5 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
- Which versions of ansible are affected by CVE-2019-14858? ansible (pip) versions >= 2.9.0a1, < 2.9.0rc4 is affected.
- Is there a fix for CVE-2019-14858? Yes. CVE-2019-14858 is fixed in 2.9.0rc4, 2.8.6, 2.7.14, 2.6.20. Upgrade to this version or later.
- Is CVE-2019-14858 exploitable, and should I be worried? Whether CVE-2019-14858 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2019-14858 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2019-14858?
- Upgrade
ansibleto 2.9.0rc4 or later - Upgrade
ansibleto 2.8.6 or later - Upgrade
ansibleto 2.7.14 or later - Upgrade
ansibleto 2.6.20 or later
- Upgrade