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.
CVE-2024-21626 - High Severity Vulnerability
github.com/opencontainers/runc/libcontainer/utils-v1.0.0-rc9
CLI tool for spawning and running containers according to the OCI specification
Dependency Hierarchy: - :x: **github.com/opencontainers/runc/libcontainer/utils-v1.0.0-rc9** (Vulnerable Library)
github.com/opencontainers/runc-v1.0.0-rc9
CLI tool for spawning and running containers according to the OCI specification
Library home page: https://proxy.golang.org/github.com/opencontainers/runc/@v/v1.0.0-rc9.zip
Dependency Hierarchy: - github.com/google/cadvisor/container/common-v0.35.0 (Root Library) - github.com/google/cadvisor/container-v0.35.0 - github.com/google/cadvisor/container/docker-v0.35.0 - github.com/google/cadvisor/container/libcontainer-v0.35.0 - :x: **github.com/opencontainers/runc-v1.0.0-rc9** (Vulnerable Library)
Found in HEAD commit: 6e30df8c07a51f900077867824d3807dffb18045
Found in base branch: master
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.
Publish Date: 2024-01-31
URL: CVE-2024-21626
Base Score Metrics: - Exploitability Metrics: - Attack Vector: Local - Attack Complexity: Low - Privileges Required: None - User Interaction: Required - Scope: Changed - Impact Metrics: - Confidentiality Impact: High - Integrity Impact: High - Availability Impact: High
For more information on CVSS3 Scores, click here.Type: Upgrade version
Origin: https://github.com/opencontainers/runc/security/advisories/GHSA-xr7r-f8xq-vfvv
Release Date: 2024-01-31
Fix Resolution: v1.1.12
Step up your Open Source Security Game with Mend here