# CVE-2024-0690: Ansible-core: possible information leak in tasks that ignore ansible_no_log configuration > Attackers can view sensitive decrypted secrets in Ansible task output because the no-log configuration is ignored in certain scenarios. - **Severity:** Medium 5.0 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:N/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Local or same network only - **Victim action needed:** A user has to click or open something - **Fix available:** Yes - **Published:** 6 Feb 2024 - **Updated:** 6 Nov 2025 - **Also known as:** ALSA-2024:2246, ALSA-2024:3043, AZL-34190, AZL-34539, CLSA-2026-1779801095, DEBIAN-CVE-2024-0690, GHSA-h24r-m9qc-pvpg, MGASA-2024-0239, OESA-2024-1190, PYSEC-2024-36, RHSA-2024:2246, RHSA-2024:3043, RLSA-2024:3043, UBUNTU-CVE-2024-0690, openSUSE-SU-2024:13636-1 ## What is CVE-2024-0690? CVE-2024-0690 is a medium-severity vulnerability in Fedoraproject Fedora, published on 6 Feb 2024. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link. ### Official description 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. Weakness: CWE-116 (Improper Encoding or Escaping of Output), CWE-117 (Improper Output Neutralization for Logs) ## Which versions are affected by CVE-2024-0690? 7 open source packages ship an affected version, including ansible-core. It affects 6 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `ansible-core` | PyPI | All versions | 2.14.4, 2.15.9, 2.16.3 | | `ansible-core` | PyPI | All versions | 2.14.14 | | `ansible-core` | PyPI | All versions | 2.14.14 | | `ansible-core` | PyPI | From 2.15.0 | 2.15.9 | | `ansible-core` | PyPI | From 2.15.0 | 2.15.9 | | `ansible-core` | PyPI | From 2.16.0 | 2.16.3 | | `ansible-core` | PyPI | From 2.16.0 | 2.16.3 | | `ansible-core` | AlmaLinux:8 | All versions | 2.16.3-2.el8 | | `ansible-test` | AlmaLinux:8 | All versions | 2.16.3-2.el8 | | `ansible-core` | AlmaLinux:9 | All versions | 1:2.14.14-1.el9 | | `ansible-test` | AlmaLinux:9 | All versions | 1:2.14.14-1.el9 | | `ansible-core` | Red Hat:enterprise_linux:8::appstream | All versions | 0:2.16.3-2.el8 | | `ansible-test` | Red Hat:enterprise_linux:8::appstream | All versions | 0:2.16.3-2.el8 | | `ansible-core` | Red Hat:enterprise_linux:9::appstream | All versions | 1:2.14.14-1.el9 | | `ansible-test` | Red Hat:enterprise_linux:9::appstream | All versions | 1:2.14.14-1.el9 | | `ansible-core` | Rocky Linux:8 | All versions | 0:2.16.3-2.el8 | Products: Fedoraproject Fedora, Redhat Ansible, Redhat Ansible Automation Platform, Redhat Ansible Developer, Redhat Ansible Inside, Redhat Enterprise Linux. ## How do I fix CVE-2024-0690? Upgrade ansible-core to a fixed version for your release line: 2.14.4, 2.15.9, 2.16.3 or 2.14.14. ## Is CVE-2024-0690 being exploited? There is no known exploitation of CVE-2024-0690 in the wild and no public exploit code. ## Other vulnerabilities in Fedoraproject Fedora - [CVE-2024-4577](https://insights.sbomify.com/CVE-2024-4577/): PHP-CGI OS Command Injection (critical 9.8, exploited in the wild) - [CVE-2021-39226](https://insights.sbomify.com/CVE-2021-39226/): Grafana Authentication Bypass (critical 9.8, exploited in the wild) - [CVE-2019-5544](https://insights.sbomify.com/CVE-2019-5544/): VMware ESXi and Horizon DaaS OpenSLP Heap-Based Buffer Overflow (critical 9.8, exploited in the wild) - [CVE-2024-4947](https://insights.sbomify.com/CVE-2024-4947/): Google Chromium V8 Type Confusion (critical 9.6, exploited in the wild) - [CVE-2024-4671](https://insights.sbomify.com/CVE-2024-4671/): Google Chromium Visuals Use-After-Free (critical 9.6, exploited in the wild) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2024-0690 and fix it if it is affected. What it is: CVE-2024-0690 is a medium-severity vulnerability in Fedoraproject Fedora, published on 6 Feb 2024. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link. Exploitation: There is no known exploitation of CVE-2024-0690 in the wild and no public exploit code. Affected packages and fixed versions: - ansible-core (PyPI): affected all versions; fixed in 2.14.4, 2.15.9, 2.16.3 - ansible-core (PyPI): affected all versions; fixed in 2.14.14 - ansible-core (PyPI): affected all versions; fixed in 2.14.14 - ansible-core (PyPI): affected from 2.15.0; fixed in 2.15.9 - ansible-core (PyPI): affected from 2.15.0; fixed in 2.15.9 - ansible-core (PyPI): affected from 2.16.0; fixed in 2.16.3 - ansible-core (PyPI): affected from 2.16.0; fixed in 2.16.3 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2024-0690/ (Markdown: https://insights.sbomify.com/CVE-2024-0690/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2024-0690 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-0690 - OSV: https://osv.dev/vulnerability/CVE-2024-0690 --- From sbomify Insights: https://insights.sbomify.com/CVE-2024-0690/ Summaries are generated and may contain mistakes; the official description above is the record.