A 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.
The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.
|Name||Vendor||Start Version||End Version|
|Red Hat Ansible Engine 2.7 for RHEL 7||RedHat||ansible-0:2.7.17-1.el7ae||*|
|Red Hat Ansible Engine 2.8 for RHEL 7||RedHat||ansible-0:2.8.11-1.el7ae||*|
|Red Hat Ansible Engine 2.8 for RHEL 8||RedHat||ansible-0:2.8.11-1.el8ae||*|
|Red Hat Ansible Engine 2.9 for RHEL 7||RedHat||ansible-0:2.9.7-1.el7ae||*|
|Red Hat Ansible Engine 2.9 for RHEL 8||RedHat||ansible-0:2.9.7-1.el8ae||*|
|Red Hat Ansible Engine 2 for RHEL 7||RedHat||ansible-0:2.9.7-1.el7ae||*|
|Red Hat Ansible Engine 2 for RHEL 8||RedHat||ansible-0:2.9.7-1.el8ae||*|
|Red Hat Ansible Tower 3.4 for RHEL 7||RedHat||ansible-tower-34/ansible-tower-memcached:1.4.15-28||*|
|Red Hat Ansible Tower 3.4 for RHEL 7||RedHat||ansible-tower-35/ansible-tower-memcached:1.4.15-28||*|
|Red Hat Ansible Tower 3.4 for RHEL 7||RedHat||ansible-tower-37/ansible-tower-memcached-rhel7:1.4.15-28||*|
|Red Hat Ansible Tower 3.5 for RHEL 7||RedHat||ansible-tower-35/ansible-tower:3.5.6-1||*|
There are many different kinds of mistakes that introduce information exposures. The severity of the error can range widely, depending on the context in which the product operates, the type of sensitive information that is revealed, and the benefits it may provide to an attacker. Some kinds of sensitive information include:
Information might be sensitive to different parties, each of which may have their own expectations for whether the information should be protected. These parties include:
Information exposures can occur in different ways:
It is common practice to describe any loss of confidentiality as an “information exposure,” but this can lead to overuse of CWE-200 in CWE mapping. From the CWE perspective, loss of confidentiality is a technical impact that can arise from dozens of different weaknesses, such as insecure file permissions or out-of-bounds read. CWE-200 and its lower-level descendants are intended to cover the mistakes that occur in behaviors that explicitly manage, store, transfer, or cleanse sensitive information.