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.
Published 2024-01-31 22:15:54
Updated 2024-02-19 03:15:08
Source GitHub, Inc.
View at NVD,   CVE.org

Products affected by CVE-2024-21626

Exploit prediction scoring system (EPSS) score for CVE-2024-21626

4.31%
Probability of exploitation activity in the next 30 days EPSS Score History
~ 88 %
Percentile, the proportion of vulnerabilities that are scored at or less

Metasploit modules for CVE-2024-21626

  • runc (docker) File Descriptor Leak Privilege Escalation
    Disclosure Date: 2024-01-31
    First seen: 2024-02-09
    exploit/linux/local/runc_cwd_priv_esc
    All versions of runc <=1.1.11, as used by containerization technologies such as Docker engine, and Kubernetes are vulnerable to an arbitrary file write. Due to a file descriptor leak it is possible to mount the host file system with the permissions of runc (t

CVSS scores for CVE-2024-21626

Base Score Base Severity CVSS Vector Exploitability Score Impact Score Score Source First Seen
8.6
HIGH CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H
1.8
6.0
NIST 2024-02-09
8.6
HIGH CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H
1.8
6.0
GitHub, Inc. 2024-01-31

CWE ids for CVE-2024-21626

References for CVE-2024-21626

Jump to
This web site uses cookies for managing your session, storing preferences, website analytics and additional purposes described in our privacy policy.
By using this web site you are agreeing to CVEdetails.com terms of use!