CVE-2020-1746: Exposure of Sensitive Information to an Unauthorized Actor in ansible

CVE-2020-1746 · Severity: low · CVSS 3.1 · Published 2020-05-12

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.

Technologies: ansible (PyPI). Vendors: PyPI.

Quick answers

Is CVE-2020-1746 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2020-1746 being exploited in the wild.
How severe is CVE-2020-1746?
Low severity, with a CVSS score of 3.1, published 12 May 2020.
Which products and versions are affected?
ansible (PyPI) ECOSYSTEM:introduced=2.7.0,fixed=2.7.17,introduced=2.8.0,fixed=2.8.11,introduced=2.9.0,fixed=2.9.7, ECOSYSTEM:introduced=2.8.0a1,fixed=2.8.11.
Is there a fix for CVE-2020-1746?
Yes. ansible (PyPI): upgrade to 2.8.11, 2.9.7 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2020-1746?
Check whether you run ansible (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • ansible (PyPI): upgrade to 2.8.11, 2.9.7 or later
    pip install "ansible>=2.9.7"

Affected products

  • ansible (PyPI) ECOSYSTEM:introduced=2.7.0,fixed=2.7.17,introduced=2.8.0,fixed=2.8.11,introduced=2.9.0,fixed=2.9.7, ECOSYSTEM:introduced=2.8.0a1,fixed=2.8.11

Identifiers

  • CVE-2020-1746
  • GHSA-j2h6-73x8-22c4
  • PYSEC-2020-13

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.