Insertion of Sensitive Information into Log File
CVE-2024-8775
Summary
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. This vulnerability affects versions prior to 2.14.18, 2.15.0 prior to 2.15.13, 2.16.0 prior to 2.16.13, 2.17.0 prior to 2.17.6, 2.18.0b1 and 2.18.0rc1.
- LOW
- LOCAL
- NONE
- UNCHANGED
- NONE
- LOW
- HIGH
- NONE
CWE-532 - Insertion of Sensitive Information into Log File
It's quite common for applications to save logs. For example, whenever a user requests a resource from a particular website, the web server writes information about the request to a log file. These files are helpful for identifying abnormal system activity, bugs, and evaluating the security controls of the application. Security of log files is critical for the overall security of the application and its confidential resources. An application that lacks appropriate logging levels can expose sensitive user data and system information stored on the log files to malicious users. This info can be exploited to compromise your system.
References
Advisory Timeline
- Published