← Back
CVE-2024-11079
medium
CVSS 5.5
Vulnerability in ansible-core (CVE-2024-11079)
Summary
vulnerability in ansible-core (CVE-2024-11079). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to `2.16.14rc1` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2024-11079** has been found in ansible-core.
Risk of unauthorized operations or information disclosure. CVSS score: 5.5/10.
What to do: upgrade ansible-core to **2.16.14rc1** or later.
If unsure, ask your IT team or search "ansible-core CVE-2024-11079" on the vendor's site.
CVE-2024-11079 (ansible-core) — CWE-20 / CVSS v3 5.5
Attack vector: remote (network-reachable)
Patched: `2.16.14rc1` — 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-20) exists in ansible-core.
📍 Affected scope
ansible-core — .
🔥 Severity
Severity: Medium (CVSS 5.5/10). Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **2.16.14rc1**.
🛡️ 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.16.14rc1ステージング環境で 2.16.14rc1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、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.16.14rc1"}]}]
References
- advisory https://nvd.nist.gov/vuln/detail/CVE-2024-11079
- advisory https://github.com/advisories/GHSA-99w6-3xph-cx78
- package https://github.com/ansible/ansible
- package https://pypi.org/project/ansible-core
- web https://access.redhat.com/errata/RHSA-2024:10770
- web https://access.redhat.com/errata/RHSA-2024:11145
- web https://bugzilla.redhat.com/show_bug.cgi?id=2325171
- web https://access.redhat.com/security/cve/CVE-2024-11079
- web https://lists.debian.org/debian-lts-announce/2026/03/msg00006.html
- web https://github.com/ansible/ansible/pull/84299
- web https://github.com/ansible/ansible/pull/84339
- web https://github.com/ansible/ansible/commit/2936b80dbbc7efb889934aeec80f6142c10266ce
- web https://github.com/ansible/ansible/commit/70e83e72b43e05e57eb42a6d52d01a4d9768f510
- web https://github.com/ansible/ansible/commit/98774d15d7748ebaaaf2e83942cc7e8d39f7280e
- web https://github.com/ansible/ansible/blob/v2.18.1/changelogs/CHANGELOG-v2.18.rst#security-fixes