CVE-2020-1746 json
Exposure of Sensitive Information to an Unauthorized Actor in ansible
published 6y ago modified 4mo ago also GHSA-j2h6-73x8-22c4 , PYSEC-2020-13 , EUVD-2020-0006
- cvss
- 5.0
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 33%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- pypi ansible 2.7.17, 2.8.11, 2.9.7
- redhat ansible_engine 2.7.17, 2.8.11, 2.9.7
- ansible Debian 14, Debian 13, Debian 12 2.9.7+dfsg-1
debian advisories DEBIAN-CVE-2020-1746
- ansible ansible engine 2.9, ansible engine 2 2.9.7-1.el7ae
- ansible ansible engine 2.9, ansible engine 2 2.9.7-1.el8ae
- ansible-test ansible engine 2.9, ansible engine 2 2.9.7-1.el7ae
- ansible-test ansible engine 2.9, ansible engine 2 2.9.7-1.el8ae
- ansible ansible engine 2.7 2.7.17-1.el7ae
- ansible ansible engine 2.8 2.8.11-1.el7ae
- ansible ansible engine 2.8 2.8.11-1.el8ae
red hat advisories RHSA-2020:1542RHSA-2020:1541RHSA-2020:1544RHSA-2020:1543
- storm OpenStack Cloud Crowbar 8, OpenStack Cloud 8, HPE Helion OpenStack 8 1.2.3-3.6.1
- ansible OpenStack Cloud Crowbar 8, OpenStack Cloud 8, HPE Helion OpenStack 8 2.9.14-3.15.1
- grafana OpenStack Cloud Crowbar 8, OpenStack Cloud 8, HPE Helion OpenStack 8 6.7.4-4.12.1
- ardana-mq OpenStack Cloud 8, HPE Helion OpenStack 8 8.0+git.1593618123.678c32b-3.26.1
- ardana-nova OpenStack Cloud 8, HPE Helion OpenStack 8 8.0+git.1601298847.dd01585-3.42.1
- crowbar-core OpenStack Cloud Crowbar 8 5.0+git.1600432272.b3ad722f0-3.44.1
- python-kombu OpenStack Cloud Crowbar 8, OpenStack Cloud 8, HPE Helion OpenStack 8 4.1.0-3.7.1
- ardana-cinder OpenStack Cloud 8, HPE Helion OpenStack 8 8.0+git.1596129856.263f430-3.43.1
suse advisories SUSE-SU-2020:3309-1
- ansible-14 openSUSE Tumbleweed 14.6.0-1.1
- ansible-13 openSUSE Tumbleweed 13.7.0-1.1
- ansible-12 openSUSE Tumbleweed 12.2.0-1.1
- ansible-11 openSUSE Tumbleweed 11.11.0-1.1
- ansible-10 openSUSE Tumbleweed 10.6.0-1.1
- ansible-9 openSUSE Tumbleweed 9.8.0-1.1
- ansible Package Hub 15 SP3, openSUSE Leap 15.3 2.9.21-bp153.2.3.1
opensuse advisories openSUSE-SU-2026:12447-1openSUSE-SU-2026:10944-1openSUSE-SU-2025:15753-1openSUSE-SU-2025:15605-1openSUSE-SU-2024:14536-1openSUSE-SU-2024:14244-1
- ansible Alpine 3.12, Alpine 3.11 2.9.7-r0
- ansible Alpine 3.9 2.7.17-r0
- ansible-base Alpine 3.15, Alpine 3.14, Alpine 3.13 2.9.7-r0
alpine advisories ALPINE-CVE-2020-1746
Alpine secdb © Alpine Linux, from https://secdb.alpinelinux.org via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- github.com/ansible/ansible@d41e384 commit
- github.com/ansible/ansible@e6199d7 commit
- github.com/ansible/ansible@edd1e17 commit
- github.com/ansible/ansible#67866 pull request
Is CVE-2020-1746 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2020-1746 updated cvss 5.0
ansible: Information disclosure issue in ldap_attr and ldap_entry modules
-
Red Hat Ceph Storage 2 ansibleaffected: workaround, no fix planned “Using args keyword and embedding the ldap_auth variable instead of using bind_pw parameter would mitigate this issue.”
-
Red Hat Ceph Storage 3 ansibleaffected: workaround, no fix available “Using args keyword and embedding the ldap_auth variable instead of using bind_pw parameter would mitigate this issue.”
-
Red Hat OpenStack Platform 10 (Newton) ansible Red Hat OpenStack Platform 13 (Queens) ansible Red Hat Storage 3 ansibleaffected: workaround, no fix planned “Using args keyword and embedding the ldap_auth variable instead of using bind_pw parameter would mitigate this issue.”
-
Red Hat Ansible Engine 2 for RHEL 7 ansible 2.9.7-1.el7ae, ansible-test 2.9.7-1.el7ae Red Hat Ansible Engine 2 for RHEL 8 ansible 2.9.7-1.el8ae, ansible-test 2.9.7-1.el8aefixed: vendor fix “Using args keyword and embedding the ldap_auth variable instead of using bind_pw parameter would mitigate this issue.” RHSA-2020:1542
-
Red Hat Ansible Engine 2.7 for RHEL 7 Server ansible 2.7.17-1.el7aefixed: vendor fix “Using args keyword and embedding the ldap_auth variable instead of using bind_pw parameter would mitigate this issue.” RHSA-2020:1544
-
Red Hat Ansible Engine 2.8 for RHEL 7 Server ansible 2.8.11-1.el7ae Red Hat Ansible Engine 2.8 for RHEL 8 ansible 2.8.11-1.el8aefixed: vendor fix “Using args keyword and embedding the ldap_auth variable instead of using bind_pw parameter would mitigate this issue.” RHSA-2020:1543
-
Red Hat Ansible Engine 2.9 for RHEL 7 Server ansible 2.9.7-1.el7ae, ansible-test 2.9.7-1.el7ae Red Hat Ansible Engine 2.9 for RHEL 8 ansible 2.9.7-1.el8ae, ansible-test 2.9.7-1.el8aefixed: vendor fix “Using args keyword and embedding the ldap_auth variable instead of using bind_pw parameter would mitigate this issue.” RHSA-2020:1541
-
Red Hat Ansible Tower 3.4 for RHEL 7 Server ansible-tower-34/ansible-tower-memcached 1.4.15-28, ansible-tower-35/ansible-tower-memcached 1.4.15-28, ansible-tower-37/ansible-tower-memcached-rhel7 1.4.15-28fixed: vendor fix “Using args keyword and embedding the ldap_auth variable instead of using bind_pw parameter would mitigate this issue.” RHBA-2020:0547
show 2 moreshow fewer
-
Red Hat Ansible Tower 3.5 for RHEL 7 Server ansible-tower-35/ansible-tower 3.5.6-1fixed: vendor fix “Using args keyword and embedding the ldap_auth variable instead of using bind_pw parameter would mitigate this issue.” RHBA-2020:1539
-
Red Hat CloudForms Management Engine 5 ansiblenot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
0.39% chance of exploitation in the next 30 days, higher than 33% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 5.0 | CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:N/A:N |
| NVD | 3.1 | 5.0 | CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:N/A:N |
| NVD | 2.0 | 1.9 | AV:L/AC:M/Au:N/C:P/I:N/A:N |
| GitHub | 3.1 | 5.0 | CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:N/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| pypi | ansible | >=2.8.0a1, <2.8.11 >=2.9.0a1, <2.9.7 >=2.7.0a1, <2.7.17 >=2.7.0, <2.7.17 >=2.8.0, <2.8.11 >=2.9.0, <2.9.7 |
2.8.11 2.9.7 2.7.17 |
Affected products
- Red Hat ansible
Classification
- Weakness
-
- CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
References
-
github.com
/ansible/ansible/pull/67866
web, patch, third-party-advisory
-
github.com
/ansible/ansible/commit/d41e38435b1a9e300d8011ac28f16a5add2db119
web
-
github.com
/ansible/ansible/commit/e6199d768c1c18a4e750ec78d4ded088629baa3f
web
-
github.com
/ansible/ansible/commit/edd1e1723cc937ec9251adf38c1199a00b0bf6d4
web
-
debian.org
/security/2021/dsa-4950
vendor-advisory, web, third-party-advisory
-
bugzilla.redhat.com
/show_bug.cgi?id=CVE-2020-1746
web, issue-tracking, vendor-advisory, report
-
nvd.nist.gov
/vuln/detail/CVE-2020-1746
advisory
-
github.com
/advisories/GHSA-j2h6-73x8-22c4
advisory
-
github.com
/ansible/ansible
package
-
github.com
/pypa/advisory-database/tree/main/vulns/ansible/PYSEC-2020-13.yaml
web
Sources
- CVE List CVE-2020-1746
- GitHub Advisory GHSA-j2h6-73x8-22c4
- NVD CVE-2020-1746
- OSV PYSEC-2020-13
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.