Ansible 2.5 prior to 2.5.5, and 2.4 prior to 2.4.5, do not honor the no_log task flag for failed tasks. When the no_log flag has been used to protect sensitive data passed to a task from being logged, and that task does not run successfully, Ansible will expose sensitive data in log files and on the terminal of the user running Ansible.
AI analysis not yet available
Plain-English explanation, risk summary, and remediation steps will appear here once AI analysis is complete.
No Fix Known
No patch has been released yet. Apply workarounds or mitigations where available.
| Vendor | Product | Versions | Fixed In |
|---|---|---|---|
| redhat | ansible_engine | 2.4 - 2.4.5 | - |
| redhat | ansible_engine | 2.5 - 2.5.5 | - |
| redhat | ansible_engine | - |
Published
CVE disclosed publicly
Last Modified
Most recent update
Indexed to CVEInsight
Added to this platform
AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
12
Affected Products
22
References
redhat / ansible_engine
| - |
| redhat | cloudforms | - | - |
| redhat | openstack | - | - |
| redhat | virtualization | - | - |
| debian | debian_linux | - | - |
| redhat | openstack | - | - |
| redhat | openstack | - | - |
| canonical | ubuntu_linux | - | - |
| canonical | ubuntu_linux | - | - |
| canonical | ubuntu_linux | - | - |
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
Exploitability
Impact