Exposure of Sensitive Information to an Unauthorized Actor in ansible
Red Hat ansible
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| ansible PyPI |
|
|
Red Hat ansible
| Product | Affected | Fixed in |
|---|---|---|
| ansible PyPI |
|
|
2.7.17A flaw was found in the Ansible Engine affecting Ansible Engine versions 2.7.x before 2.7.17 and 2.8.x before 2.8.11 and 2.9.x before 2.9.7 as well as Ansible Tower before and including versions 3.4.5 and 3.5.5 and 3.6.3 when the ldap_attr and ldap_entry community modules are used. The issue discloses the LDAP bind password to stdout or a log file if a playbook task is written using the bind_pw in the parameters field. The highest threat from this vulnerability is data confidentiality.
From the CVE record · redhat
Ansible Engine and Ansible Tower can disclose an LDAP bind password to stdout or a log file when the ldap_attr or ldap_entry module is used and a playbook task puts bind_pw in the parameters field. Anyone with access to that output could see the password; the input does not specify a network attack, authentication requirement, or user interaction.
Teams running Ansible Engine 2.7.x before 2.7.17, 2.8.x before 2.8.11, or 2.9.x before 2.9.7, or Ansible Tower versions up to and including 3.4.5, 3.5.5, or 3.6.3, should check their playbooks.