Credential disclosure via unmasked module arguments
Published May 26, 2021 · Updated Aug 3, 2024
Sensitive-data exposure in Red Hat Ansible before 2.8.19rc1, 2.9.18rc1, or 2.10.7 allows local users to read credentials from logs. Multiple module argument specifications omit no_log=True for secret-bearing fields, causing normal task-result handling to emit API keys, private keys, tokens, and shared secrets. Exploitation requires low-privileged local access to output from a playbook run that invokes an affected module, and the reported consequence is credential disclosure only.
Summary
What happened
Sensitive-data exposure in Red Hat Ansible before 2.8.19rc1, 2.9.18rc1, or 2.10.7 allows local users to read credentials from logs. Multiple module argument specifications omit no_log=True for secret-bearing fields, causing normal task-result handling to emit API keys, private keys, tokens, and shared secrets. Exploitation requires low-privileged local access to output from a playbook run that invokes an affected module, and the reported consequence is credential disclosure only.
The record
- CVE
- CVE-2021-20191
- Published
- May 26, 2021
- Updated
- Aug 3, 2024
- Vendor
- Red Hat
- Product
- Ansible
- Classifications
- CWE-532, T1552.001
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 26, 2021CVE publishedPublication date reported by the CVE source.
- Aug 3, 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.
- Affected versionversion=ansible 2.9.18
What conditions does exploitation require?
What is affected?
Published CVSS scores
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.
Weakness, pattern, technique
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