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.
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2019-14858US | medium5.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 inval… | ||||
references
External citations — patches, advisories, analysis.
- http://lists.opensuse.org/opensuse-security-announce/2020-04/msg00021.htmlWEB
- http://lists.opensuse.org/opensuse-security-announce/2020-04/msg00026.htmlWEB
- https://access.redhat.com/errata/RHSA-2019:3201WEB
- https://access.redhat.com/errata/RHSA-2019:3202WEB
- https://access.redhat.com/errata/RHSA-2019:3203WEB
- https://access.redhat.com/errata/RHSA-2019:3207WEB
- https://access.redhat.com/errata/RHSA-2020:0756WEB
- https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2019-14858WEB
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan