CVE-2020-1746

LDAP bind-password disclosure via params option

Published May 12, 2020 · Updated Aug 4, 2024

Information disclosure in affected Red Hat Ansible releases allows local users to obtain LDAP bind passwords from playbook output. The ldap_attr and ldap_entry modules merge the generic params dictionary outside normal secret handling, allowing bind_pw to reach stdout or log files. Exposure requires a task that supplies bind_pw inside params; affected releases include Engine 2.7.x before 2.7.17, 2.8.x before 2.8.11, and 2.9.x before 2.9.7, plus Tower through 3.4.5, 3.5.5, or 3.6.3.

CVSS severity5.0
Medium
EPSS probability0.41%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Information disclosure in affected Red Hat Ansible releases allows local users to obtain LDAP bind passwords from playbook output. The ldap_attr and ldap_entry modules merge the generic params dictionary outside normal secret handling, allowing bind_pw to reach stdout or log files. Exposure requires a task that supplies bind_pw inside params; affected releases include Engine 2.7.x before 2.7.17, 2.8.x before 2.8.11, and 2.9.x before 2.9.7, plus Tower through 3.4.5, 3.5.5, or 3.6.3.

The record

CVE
CVE-2020-1746
Published
May 12, 2020
Updated
Aug 4, 2024
Vendor
Red Hat
Product
Ansible
Classifications
CWE-200, T1552.001
Attack vector
local
Privileges
authenticated

Timeline

How it unfolded

  1. May 12, 2020CVE publishedPublication date reported by the CVE source.
  2. Aug 4, 2024Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=ansible-engine versions 2.7.x before 2.7.17
  2. Affected versionversion=ansible-engine versions 2.8.x before 2.8.11
  3. Affected versionversion=ansible-engine versions 2.9.x before 2.9.7
  4. Affected versionversion=Ansible Tower <= 3.4.5
  5. Affected versionversion=Ansible Tower <= 3.5.5
  6. Affected versionversion=Ansible Tower <= 3.6.3

What conditions does exploitation require?

Attack vectorlocal
Required privilegesauthenticated

What is affected?

Red Hat · Ansibleversion=ansible-engine versions 2.7.x before 2.7.17; version=ansible-engine versions 2.8.x before 2.8.11; version=ansible-engine versions 2.9.x before 2.9.7; version=Ansible Tower <= 3.4.5; version=Ansible Tower <= 3.5.5; version=Ansible Tower <= 3.6.3

Published CVSS scores

5.1GitHub Advisory DatabaseCVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:P/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
1.9NIST NVDAV:L/AC:M/Au:N/C:P/I:N/A:N
5.0Red Hat, Inc.CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:N/A:N

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectorlocal
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-200Exposure of Sensitive Information to an Unauthorized Actor
T1552.001Unsecured Credentials: Credentials In Files

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo