PYSEC-2018-42: Medium severity Ansible Ansible vulnerability

Q: Who is exposed to this issue?

Users running affected Ansible versions are exposed when they use the no_log task flag to protect sensitive task data and the task fails. In that situation, the sensitive data can be displayed on the operator's terminal and written to log files.

Q: What does an attacker need to exploit this vulnerability?

The issue is triggered by a failed task that has no_log enabled; the affected behavior exposes the task's sensitive data through Ansible output and logs. The supplied vector indicates network reachability, no privileges, and no user interaction, but high attack complexity.

Q: How can I determine whether I am affected?

Check whether Ansible is earlier than 2.5.5 in the 2.5 release line or earlier than 2.4.5 in the 2.4 release line. Also review failed no_log task output and associated log files for sensitive values that may already have been exposed.

Published Jul 3, 2018

Updated

Ansible 2.5 prior to 2.5.5, and 2.4 prior to 2.4.5, do not honor the nolog task flag for failed tasks. When the nolog 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.

Affected Software

1 affected component

Ansible Ansible>=2.5<2.5.5, >=2.4<2.4.5

Event History

Jul 3, 2018

CVE Published

via OSV·01:29 AM

Data Sourced

via OSV·01:29 AM

DescriptionSeverity

Frequently Asked Questions

Who is exposed to this issue?

Users running affected Ansible versions are exposed when they use the no_log task flag to protect sensitive task data and the task fails. In that situation, the sensitive data can be displayed on the operator's terminal and written to log files.

What does an attacker need to exploit this vulnerability?

The issue is triggered by a failed task that has no_log enabled; the affected behavior exposes the task's sensitive data through Ansible output and logs. The supplied vector indicates network reachability, no privileges, and no user interaction, but high attack complexity.

How can I determine whether I am affected?

Check whether Ansible is earlier than 2.5.5 in the 2.5 release line or earlier than 2.4.5 in the 2.4 release line. Also review failed no_log task output and associated log files for sensitive values that may already have been exposed.

PYSEC-2018-42: Medium severity Ansible Ansible vulnerability

Affected Software

Event History

Frequently Asked Questions

Who is exposed to this issue?

What does an attacker need to exploit this vulnerability?

How can I determine whether I am affected?

Company

Resources

Contact

Frequently Asked Questions

Who is exposed to this issue?

What does an attacker need to exploit this vulnerability?

How can I determine whether I am affected?