Categories
CVE-2024-21626 high CVSS 8.6

Vulnerability in github.com/opencontainers/runc (CVE-2024-21626)

Summary

Vulnerability in github.com/opencontainers/runc (CVE-2024-21626). Successful exploitation can lead to full system takeover. Exploitable via process.cwd. Mitigation: upgrade to 1.1.12 or later.

Original description

The description as published by the source.

runc is a CLI tool for spawning and running containers on Linux according to the OCI specification. In runc 1.1.11 and earlier, due to an internal file descriptor leak, an attacker could cause a newly-spawned container process (from runc exec) to have a working directory in the host filesystem namespace, allowing for a container escape by giving access to the host filesystem ("attack 2"). The same attack could be used by a malicious image to allow a container process to gain access to the host filesystem through runc run ("attack 1"). Variants of attacks 1 and 2 could be also be used to overwrite semi-arbitrary host binaries, allowing for complete container escapes ("attack 3a" and "attack 3b"). runc 1.1.12 includes patches for this issue.

Source: NIST National Vulnerability Database NVD GitHub Advisory

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-21626 has been found in github.com/opencontainers/runc.
Attackers can target a specific entry point like process.cwd over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 8.6/10.
What to do: upgrade github.com/opencontainers/runc to 1.1.12 or later.
If unsure, ask your IT team or search "github.com/opencontainers/runc CVE-2024-21626" on the vendor's site.

CVE-2024-21626 (github.com/opencontainers/runc) — CWE-403 / CVSS v3 8.6
Attack vector: local / unauthenticated
Attack surface: process.cwd / runc / ONBUILD / PR_SET_DUMPABLE
Patched: 1.1.12 — 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-403) exists in github.com/opencontainers/runc. Attackers reach the vulnerable code path via process.cwd without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of github.com/opencontainers/runc. Attack surface: process.cwd / runc / ONBUILD / PR_SET_DUMPABLE.

🔥 Severity

Severity: High (CVSS 8.6/10). Successful exploitation can lead to full system takeover.

🔧 How to fix

Update to 1.1.12.

🛡️ 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 'github.com/opencontainers/runc' . 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 'github.com/opencontainers/runc' . | grep -v node_modules

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

  2. 2
    Apply patch patch
    Upgrade github.com/opencontainers/runc to 1.1.12

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

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

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

Affected packages

go github.com/opencontainers/runc
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.1.12"}]}]

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