Credential disclosure via unmasked secured module values
Published Mar 16, 2022 · Updated Aug 3, 2024
Information disclosure in Red Hat Ansible before 2.9.18 allows local users to read Bitbucket pipeline credentials from console logs. When secured is true, bitbucket_pipeline_variable leaves its value argument without no_log protection, causing task output to print the secret. Exposure requires execution of that module with a secured variable and access to its console output; the documented consequence is credential disclosure.
Summary
What happened
Information disclosure in Red Hat Ansible before 2.9.18 allows local users to read Bitbucket pipeline credentials from console logs. When secured is true, bitbucket_pipeline_variable leaves its value argument without no_log protection, causing task output to print the secret. Exposure requires execution of that module with a secured variable and access to its console output; the documented consequence is credential disclosure.
The record
- CVE
- CVE-2021-20180
- Published
- Mar 16, 2022
- Updated
- Aug 3, 2024
- Vendor
- Red Hat
- Product
- Ansible
- Classifications
- CWE-532, T1552.001
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 16, 2022CVE 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=Fixed in ansible 2.9.18
What conditions does exploitation require?
What is affected?
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