Ansible exposes sensitive data in log files and on the terminal
Moderate severity
GitHub Reviewed
Published
Oct 10, 2018
to the GitHub Advisory Database
•
Updated Sep 4, 2024
Package
Affected versions
>= 2.5.0a1, < 2.5.5
>= 2.4.0.0, < 2.4.5.0
Patched versions
2.5.5
2.4.5.0
Description
Published by the National Vulnerability Database
Jul 3, 2018
Published to the GitHub Advisory Database
Oct 10, 2018
Reviewed
Jun 16, 2020
Last updated
Sep 4, 2024
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.
References