CVE-2019-14858
published 2019-10-14CVE-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…
PriorityP424medium5.5CVSS 3.1
AVLACLPRLUINSUCHINAN
EPSS
0.43%
34.6th percentile
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.
Affected
13 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | ansible | < ansible 2.8.6+dfsg-1 (bookworm) | ansible 2.8.6+dfsg-1 (bookworm) |
| red_hat | ansible | — | — |
| red_hat | ansible | — | — |
| redhat | ansible | >= 0 < 2.8.6+dfsg-1 | 2.8.6+dfsg-1 |
| redhat | ansible | >= 0 < 2.8.6+dfsg-1 | 2.8.6+dfsg-1 |
| redhat | ansible | >= 0 < 2.8.6+dfsg-1 | 2.8.6+dfsg-1 |
| redhat | ansible | >= 0 < 2.8.6+dfsg-1 | 2.8.6+dfsg-1 |
| redhat | ansible | >= 2.0 < 2.6.20 | 2.6.20 |
| redhat | ansible | >= 2.7.0a1 < 2.7.14 | 2.7.14 |
| redhat | ansible | >= 2.8.0a1 < 2.8.6 | 2.8.6 |
| redhat | ansible | >= 2.9.0a1 < 2.9.0rc4 | 2.9.0rc4 |
| redhat | ansible_engine | 2.0 – 2.8.0 | — |
| redhat | ansible_tower | 3.0 – 3.5.0 | — |
CVSS provenance
nvdv3.15.5MEDIUMCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
nvdv3.07.3HIGHCVSS:3.0/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H
nvdv2.02.1LOWAV:L/AC:L/Au:N/C:P/I:N/A:N
osv5.5MEDIUM
vendor_debian5.5MEDIUM
vendor_redhat5.5MEDIUM
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
Red Hat
ansible: sub parameters marked as no_log are not masked in certain failure scenarios
vendor_redhat·2019-10-11·CVSS 5.5
CVE-2019-14858 [MEDIUM] CWE-215 ansible: sub parameters marked as no_log are not masked in certain failure scenarios
ansible: sub parameters marked as no_log are not masked in certain failure scenarios
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.
A flaw was found in ansible. 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 para
Debian
CVE-2019-14858: ansible - A vulnerability was found in Ansible engine 2.x up to 2.8 and Ansible tower 3.x ...
vendor_debian·2019·CVSS 5.5
CVE-2019-14858 [MEDIUM] CVE-2019-14858: ansible - A vulnerability was found in Ansible engine 2.x up to 2.8 and Ansible tower 3.x ...
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.
Scope: local
bookworm: resolved (fixed in 2.8.6+dfsg-1)
bullseye: resolved (fixed in 2.8.6+dfsg-1)
forky: resolved (fixed in 2.8.6+dfsg-1)
sid: resolved (fixed in 2.8.6+dfsg-1)
trixie: resolved (fixed in 2.8.6+dfsg-1)
OSV
Ansible leaks sensitive information to logs when told not to
osv·2022-05-24
CVE-2019-14858 [MEDIUM] Ansible leaks sensitive information to logs when told not to
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.
GHSA
Ansible leaks sensitive information to logs when told not to
ghsa·2022-05-24
CVE-2019-14858 [MEDIUM] CWE-532 Ansible leaks sensitive information to logs when told not to
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.
OSV
CVE-2019-14858: A vulnerability was found in Ansible engine 2
osv·2019-10-14·CVSS 5.5
CVE-2019-14858 [MEDIUM] CVE-2019-14858: A vulnerability was found in Ansible engine 2
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.
No detection rules found.
No public exploits indexed.
Bugzilla
CVE-2019-14858 ansible: sub parameters marked as no_log are not masked in certain failure scenarios [openstack-rdo]
bugzilla·2019-10-29·CVSS 5.5
CVE-2019-14858 [MEDIUM] CVE-2019-14858 ansible: sub parameters marked as no_log are not masked in certain failure scenarios [openstack-rdo]
CVE-2019-14858 ansible: sub parameters marked as no_log are not masked in certain failure scenarios [openstack-rdo]
This is an automatically created tracking bug! It was created to ensure
that one or more security vulnerabilities are fixed in affected versions
of openstack-rdo.
For comments that are specific to the vulnerability please use bugs filed
against the "Security Response" product referenced in the "Blocks" field.
For more information see:
http://fedoraproject.org/wiki/Security/TrackingBugs
When submitting as an update, use the fedpkg template provided in the next
comment(s). This will include the bug IDs of this tracking bug as well as
the relevant top-level CVE bugs.
Please also mention the CVE IDs being fixed in the RPM changelog and the
fedpkg commit message.
Discussion
Bugzilla
CVE-2019-14858 ansible: sub parameters marked as no_log are not masked in certain failure scenarios
bugzilla·2019-10-10·CVSS 5.5
CVE-2019-14858 [MEDIUM] CVE-2019-14858 ansible: sub parameters marked as no_log are not masked in certain failure scenarios
CVE-2019-14858 ansible: sub parameters marked as no_log are not masked in certain failure scenarios
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.
Discussion:
Acknowledgments:
Name: Sam Doran (Red Hat)
---
Do you have an upstream reference on this issue?
---
Upstream fix is: https://github.com/ansible/ansible/pull/63405
Note that the code has changed quite a bit here so some of the backprots will be very different looking.
---
Th
http://lists.opensuse.org/opensuse-security-announce/2020-04/msg00021.htmlhttp://lists.opensuse.org/opensuse-security-announce/2020-04/msg00026.htmlhttps://access.redhat.com/errata/RHSA-2019:3201https://access.redhat.com/errata/RHSA-2019:3202https://access.redhat.com/errata/RHSA-2019:3203https://access.redhat.com/errata/RHSA-2019:3207https://access.redhat.com/errata/RHSA-2020:0756https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2019-14858http://lists.opensuse.org/opensuse-security-announce/2020-04/msg00021.htmlhttp://lists.opensuse.org/opensuse-security-announce/2020-04/msg00026.htmlhttps://access.redhat.com/errata/RHSA-2019:3201https://access.redhat.com/errata/RHSA-2019:3202https://access.redhat.com/errata/RHSA-2019:3203https://access.redhat.com/errata/RHSA-2019:3207https://access.redhat.com/errata/RHSA-2020:0756https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2019-14858
2019-10-14
Published