Ansible vulnerable to Insertion of Sensitive Information into Log File
A flaw was found in Ansible, where sensitive information stored in Ansible Vault files can be exposed in plaintext during the execution of a playbook. This occurs when using tasks such as include_vars to load vaulted variables without setting the no_log: true parameter, resulting in sensitive data being printed in the playbook output or logs. This can lead to the unintentional disclosure of secrets like passwords or API keys, compromising security and potentially allowing unauthorized access or actions.
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2024-8775US | — | — | ||
A flaw was found in Ansible, where sensitive information stored in Ansible Vault files can be exposed in plaintext during the execution of a playbook. This occurs when using tasks… | ||||
references
External citations — patches, advisories, analysis.
- https://access.redhat.com/errata/RHSA-2024:10762WEB
- https://access.redhat.com/errata/RHSA-2024:8969WEB
- https://access.redhat.com/errata/RHSA-2024:9894WEB
- https://access.redhat.com/errata/RHSA-2025:1249WEB
- https://access.redhat.com/security/cve/CVE-2024-8775WEB
- https://bugzilla.redhat.com/show_bug.cgi?id=2312119WEB
- https://github.com/advisories/GHSA-jpxc-vmjf-9fcjADVISORY
- https://github.com/ansible/ansiblePACKAGE
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan