Microsoft security update for CVE-2024-8775
🔗 CVE IDs covered (1)
📋 Microsoft's advisory
EchelonGraph does not copy Microsoft's advisory page: its FAQ and remediation text are not shown here. Read the advisory on https://msrc.microsoft.com/update-guide/vulnerability/CVE-2024-8775. This page also shows what EchelonGraph holds for CVE-2024-8775, with the description from its CVE record, which the CVE Numbering Authority that assigned the CVE wrote: for a CVE Microsoft assigned, often in the words of Microsoft's own advisory.
🎯 Affected products4
- azl3 ansible 2.17.0-1 on Azure Linux 3.0
- azl3 ansible 2.17.11-1 on Azure Linux 3.0
- cbl2 ansible 2.14.18-1 on CBL Mariner 2.0
- cbl2 ansible 2.14.18-1 on CBL-Mariner 2.0
✅ Updates Microsoft lists: 2 updates
2 rows: one per KB article or update, update type and fixed build. Their details are on Microsoft's advisory.
| KB article | Update | Fixed build |
|---|---|---|
| — | Security Update | 2.17.11-1 |
| — | Security Update | 2.14.18-1 |
🧭 EchelonGraph on CVE-2024-8775
- EchelonGraph score
- 5.5 MEDIUM
- CISA KEV
- Not listed
- Fix status
- A fix is available — apply it.
Description from the CVE record (CVE.org), as published by its numbering authority
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.
Published by Red Hat, Inc., the CVE Numbering Authority that assigned CVE-2024-8775, in its CVE record at CVE.org; reused under the CVE Program's Terms of Use (its licence and MITRE's copyright notice are in our Terms of Service).