CVE-2024-0690GHSA-H24R-M9QC-PVPGPYSEC-2024-36
Ansible-core: possible information leak in tasks that ignore ansible_no_log configuration
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 2.14.4, 2.15.9, 2.16.3, 2.14.14
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
CISA's decision points: whether it is exploited, whether attacks can be automated, and how much control an attacker gets. Assessed (SSVC 2.0.3).What do these mean? →
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
An information disclosure flaw was found in ansible-core due to a failure to respect the ANSIBLE_NO_LOG configuration in some scenarios. Information is still included in the output in certain tasks, such as loop items. Depending on the task, this issue may include sensitive information, such as decrypted secret values.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- ansible
From 2.14.0 · fixed in 2.14.4; From 2.15.0 · fixed in 2.15.9; From 2.16.0 · fixed in 2.16.3
- ansible-core
Version range not reported
- ansible-core
Version range not reported
- ansible-core
Version range not reported
- ansible-core
Version range not reported
- ansible-corePyPI
fixed in 2.14.14
- ansible-corePyPI
From 2.16.0 · fixed in 2.16.3
- ansible-corePyPI
From 2.15.0 · fixed in 2.15.9
- ansible-corePyPI
fixed in 2.14.4; From 2.15.0 · fixed in 2.15.9; From 2.16.0 · fixed in 2.16.3