First published: Fri Jun 08 2018(Updated: )
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.
Credit: secalert@redhat.com secalert@redhat.com
Affected Software | Affected Version | How to fix |
---|---|---|
Redhat Ansible Engine | >=2.4<2.4.5 | |
Redhat Ansible Engine | >2.5<=2.5.5 | |
Redhat Ansible Engine | =2.0 | |
Redhat Cloudforms | =4.6 | |
Redhat Openstack | =13 | |
Redhat Virtualization | =4.0 | |
Debian Debian Linux | =9.0 | |
Redhat Openstack | =10 | |
Redhat Openstack | =12 | |
Canonical Ubuntu Linux | =16.04 | |
Canonical Ubuntu Linux | =18.04 | |
Canonical Ubuntu Linux | =19.04 | |
redhat/Ansible | <2.4.5 | 2.4.5 |
redhat/Ansible | <2.5.5 | 2.5.5 |
debian/ansible | 2.10.7+merged+base+2.10.17+dfsg-0+deb11u1 7.7.0+dfsg-3+deb12u1 10.1.0+dfsg-1 | |
pip/ansible | >=2.4.0.0<2.4.5.0 | 2.4.5.0 |
pip/ansible | >=2.5.0a1<2.5.5 | 2.5.5 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2018-10855 is a vulnerability in Ansible 2.5 and 2.4 that allows sensitive data to be exposed in log files and on the Ansible control machine.
CVE-2018-10855 has a severity rating of 5.9, which is considered medium.
Ansible versions prior to 2.5.5 and 2.4.5 are affected by CVE-2018-10855.
To fix CVE-2018-10855, update Ansible to versions 2.5.5 or 2.4.5.
More information about CVE-2018-10855 can be found on the Red Hat Bugzilla and Red Hat Access websites.