Sign in Sign up
JA · EN · FR
SecPulse
Categories
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.

Original description

The description as published by the source.

A flaw was found in Ansible-Core. This vulnerability allows attackers to bypass unsafe content protections using the hostvars object to reference and execute templated content. This issue can lead to arbitrary code execution if remote data or module outputs are improperly templated within playbooks.

Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

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

Check the vendor advisory for the affected versions of 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

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r 'ansible-core' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で ansible-core を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch 
    Upgrade ansible-core to 2.16.14rc1

    ステージング環境で 2.16.14rc1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

PyPI ansible-core
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.16.14rc1"}]}]

Fix status by distribution

Fixed packages published by each distribution for this CVE

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details