Description
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.
No analysis available yet.
Remediation
No remediation available yet.
Tracking
Sign in to view the affected projects.
Advisories
| Source | ID | Title |
|---|---|---|
Debian DSA |
DSA-4396-1 | ansible security update |
EUVD |
EUVD-2018-0015 | 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. |
Github GHSA |
GHSA-jwcc-j78w-j73w | Ansible exposes sensitive data in log files and on the terminal |
Ubuntu USN |
USN-4072-1 | Ansible vulnerabilities |
References
History
Sun, 13 Jul 2025 13:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
epss
|
epss
|
Status: PUBLISHED
Assigner: redhat
Published:
Updated: 2024-08-05T07:46:47.397Z
Reserved: 2018-05-09T00:00:00.000Z
Link: CVE-2018-10855
No data.
Status : Modified
Published: 2018-07-03T01:29:00.580
Modified: 2024-11-21T03:42:08.980
Link: CVE-2018-10855
OpenCVE Enrichment
No data.
Weaknesses
Debian DSA
EUVD
Github GHSA
Ubuntu USN