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.
| Product | Vendor Advisory | Solution File | Added | Published |
|---|---|---|---|---|
| Alpine Linux | — | Upgrade ansible | Sep 28, 2018 | Jul 2, 2018 |
| Debian | — | Upgrade ansible | Feb 20, 2019 | Jul 2, 2018 |
| Suse | — | Upgrade ansible | Feb 4, 2022 | Jul 2, 2018 |
| Ubuntu | — | Upgrade ansible | Jul 25, 2019 | Jul 2, 2018 |
With curated Threat Intelligence, you can see which vulnerabilities truly put you at risk, prioritize what matters most, and act before attackers do.
Explore Intelligence Hub