← Back
CVE-2024-9902
Authorization Flaw in ansible-core (CVE-2024-9902)
Summary
vulnerability in ansible-core (CVE-2024-9902). Confidential information can be exposed externally. Exploitable via ``user``. Mitigation: upgrade to `2.18.0rc2` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2024-9902** has been found in ansible-core.
Attackers can target a specific entry point like ``user`` over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: ?/10.
What to do: upgrade ansible-core to **2.18.0rc2** or later.
If unsure, ask your IT team or search "ansible-core CVE-2024-9902" on the vendor's site.
CVE-2024-9902 (ansible-core) — CWE-863 /
Attack vector: local
Attack surface: `user`
Patched: `2.18.0rc2` — 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
**incorrect authorization** (CWE-863) exists in ansible-core. Attackers reach the vulnerable code path via ``user`` without authentication.
📍 Affected scope
ansible-core — . Attack surface: `user`.
🔥 Severity
Severity: ?. Confidential information can be exposed externally
🔧 How to fix
Update to **2.18.0rc2**.
🛡️ 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.18.0rc2ステージング環境で 2.18.0rc2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、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":"2.18.0b1"},{"fixed":"2.18.0rc2"}]}]
References
- advisory https://nvd.nist.gov/vuln/detail/CVE-2024-9902
- advisory https://github.com/advisories/GHSA-32p4-gm2c-wmch
- package https://github.com/ansible/ansible
- package https://pypi.org/project/ansible-core
- web https://access.redhat.com/errata/RHSA-2024:10762
- web https://access.redhat.com/errata/RHSA-2024:8969
- web https://access.redhat.com/errata/RHSA-2024:9894
- web https://access.redhat.com/errata/RHSA-2025:1861
- web https://bugzilla.redhat.com/show_bug.cgi?id=2318271
- web https://access.redhat.com/security/cve/CVE-2024-9902
- web https://github.com/ansible/ansible/commit/03794735d370db98a5ec2ad514fab2b0dd22d6be
- web https://github.com/ansible/ansible/commit/03daf774d0d80fb7235910ed1c2b4fbcaebdfe65
- web https://github.com/ansible/ansible/commit/3b6de811abea0a811e03e3029222a7e459922892
- web https://github.com/ansible/ansible/commit/9d7312f695639e804d2caeb1d0f51c716a9ac7dd
- web https://github.com/ansible/ansible/commit/f7be90626da3035c697623dcf9c90b7a0bc91c92
- web https://lists.debian.org/debian-lts-announce/2024/11/msg00021.html