Inclusion of Sensitive Information in Log Files and Improper Output Neutralization for Logs in Ansible
Red Hat Ansible
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| ansible PyPI |
|
|
Red Hat Ansible
| Product | Affected | Fixed in |
|---|---|---|
| ansible PyPI |
|
|
2.9.1Ansible, versions 2.9.x before 2.9.1, 2.8.x before 2.8.7 and Ansible versions 2.7.x before 2.7.15, is not respecting the flag no_log set it to True when Sumologic and Splunk callback plugins are used send tasks results events to collectors. This would discloses and collects any sensitive data.
From the CVE record · redhat
Ansible does not honor no_log=True when the Sumologic or Splunk callback plugins send task-result events to collectors. Sensitive data can be disclosed to and collected by those collectors under those conditions; the input does not specify attacker access requirements or user interaction.
Check deployments of the PyPI ansible package on affected 2.7.x, 2.8.x, or 2.9.x versions before 2.7.15, 2.8.7, or 2.9.1, respectively.