Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2019-19921

Vulnerability in github.com/opencontainers/runc (CVE-2019-19921)

Summary

Vulnerability in github.com/opencontainers/runc (CVE-2019-19921). Successful exploitation can lead to full system takeover. Exploitable via runc. Mitigation: upgrade to 1.0.0-rc10 or later.

Original description

The description as published by the source.

Impact

By crafting a malicious root filesystem (with /proc being a symlink to a directory which was inside a volume shared with another running container), an attacker in control of both containers can trick runc into not correctly configuring the container's security labels and not correctly masking paths inside /proc which contain potentially-sensitive information about the host (or even allow for direct attacks against the host).

In order to exploit this bug, an untrusted user must be able to spawn custom containers with custom mount configurations (such that a volume is shared between two containers). It should be noted that we consider this to be a fairly high level of access for an untrusted user -- and we do not recommend allowing completely untrusted users to have such degrees of access without further restrictions.

Specific Go Package Affected

github.com/opencontainers/runc/libcontainer

Patches

This vulnerability has been fixed in 1.0.0-rc10. It should be noted that the current fix is effectively a hot-fix, and there are known ways for it to be worked around (such as making the entire root filesystem a shared volume controlled by another container). We recommend that users review their access policies to ensure that untrusted users do not have such high levels of controls over container mount configuration.

Workarounds

If you are not providing the ability for untrusted users to configure mountpoints for runc (or through a higher-level to…

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

CVE-2019-19921 (github.com/opencontainers/runc) — CWE-362
Attack vector: local / no user interaction
Attack surface: runc
Patched: 1.0.0-rc10 — 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-362) exists in github.com/opencontainers/runc. Attackers reach the vulnerable code path via runc.

📍 Affected scope

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

🔥 Severity

Severity: ?. Successful exploitation can lead to full system takeover.

🔧 How to fix

Update to 1.0.0-rc10.

🛡️ 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.0.0-rc10

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

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

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

Affected packages

go github.com/opencontainers/runc
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"1.0.0-rc9.0.20200122160610-2fc03cc11c77"}]}]

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