CVE-2018-10855
Published: 3 July 2018
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.
Priority
Status
Package | Release | Status |
---|---|---|
ansible Launchpad, Ubuntu, Debian |
artful |
Ignored
(end of life)
|
bionic |
Released
(2.5.1+dfsg-1ubuntu0.1)
|
|
cosmic |
Not vulnerable
(2.6.1+dfsg-1)
|
|
disco |
Not vulnerable
(2.6.1+dfsg-1)
|
|
trusty |
Not vulnerable
(code not present)
|
|
upstream |
Released
(2.5.5+dfsg-1)
|
|
xenial |
Not vulnerable
(code not present)
|
Severity score breakdown
Parameter | Value |
---|---|
Base score | 5.9 |
Attack vector | Network |
Attack complexity | High |
Privileges required | None |
User interaction | None |
Scope | Unchanged |
Confidentiality | High |
Integrity impact | None |
Availability impact | None |
Vector | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N |