← Back
CVE-2024-0690
Vulnerability in ansible-core (CVE-2024-0690)
Summary
vulnerability in ansible-core (CVE-2024-0690). Confidential information can be exposed externally. Mitigation: upgrade to `2.14.4, 2.15.9, 2.16.3` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2024-0690** has been found in ansible-core.
Confidential information can be exposed externally. CVSS score: ?/10.
What to do: upgrade ansible-core to **2.14.4, 2.15.9, 2.16.3** or later.
If unsure, ask your IT team or search "ansible-core CVE-2024-0690" on the vendor's site.
CVE-2024-0690 (ansible-core) — CWE-116 /
Attack vector: local / no user interaction
Patched: `2.14.4, 2.15.9, 2.16.3` — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
❓ What is the problem
**A vulnerability** (CWE-116) exists in ansible-core.
📍 Affected scope
ansible-core — .
🔥 Severity
Severity: ?. Confidential information can be exposed externally
🔧 How to fix
Update to **2.14.4, 2.15.9, 2.16.3**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'ansible-core' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'ansible-core' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `ansible-core` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade ansible-core to 2.14.4, 2.15.9, 2.16.3ステージング環境で 2.14.4, 2.15.9, 2.16.3 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
PyPI
ansible-core
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.14.4"},{"introduced":"2.15.0"},{"fixed":"2.15.9"},{"introduced":"2.16.0"},{"fixed":"2.16.3"}]}]
References
- advisory https://access.redhat.com/errata/RHSA-2024:0733
- advisory https://access.redhat.com/security/cve/CVE-2024-0690
- advisory https://security.netapp.com/advisory/ntap-20250117-0001/
- advisory https://nvd.nist.gov/vuln/detail/CVE-2024-0690
- advisory https://github.com/advisories/GHSA-h24r-m9qc-pvpg
- package https://github.com/ansible/ansible
- patch https://github.com/ansible/ansible/pull/82565
- report https://bugzilla.redhat.com/show_bug.cgi?id=2259013
- web https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/IZQGCRDSZL7ONCULMB6ZUHOE4L44KIBP/
- web https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/VDYSWOCPZMNRU5LWKIEBW4WGWLMTU7WQ/
- web https://access.redhat.com/errata/RHSA-2024:2246
- web https://access.redhat.com/errata/RHSA-2024:3043
- web https://github.com/ansible/ansible/commit/6935c8e303440addd3871ecf8e04bde61080b032
- web https://github.com/ansible/ansible/commit/78db3a3de6b40fb52d216685ae7cb903c609c3e1
- web https://github.com/ansible/ansible/commit/b9a03bbf5a63459468baf8895ff74a62e9be4532
- web https://github.com/ansible/ansible/commit/beb04bc2642c208447c5a936f94310528a1946b1
- web https://github.com/pypa/advisory-database/tree/main/vulns/ansible-core/PYSEC-2024-36.yaml
- web https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/IZQGCRDSZL7ONCULMB6ZUHOE4L44KIBP
- web https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/VDYSWOCPZMNRU5LWKIEBW4WGWLMTU7WQ
- web https://security.netapp.com/advisory/ntap-20250117-0001