CVE-2024-21626
Published: 31 January 2024
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.
Notes
| Author | Note |
|---|---|
Priority reason: Allows an attacker to escape containers |
|
| 0xnishit | affected versions >=v1.0.0-rc93,<=1.1.11 |
Priority
Status
| Package | Release | Status |
|---|---|---|
|
runc Launchpad, Ubuntu, Debian |
bionic |
Released
(1.1.4-0ubuntu1~18.04.2+esm1)
Available with Ubuntu Pro |
| focal |
Released
(1.1.7-0ubuntu1~20.04.2)
|
|
| jammy |
Released
(1.1.7-0ubuntu1~22.04.2)
|
|
| lunar |
Ignored
(end of life, was needs-triage)
|
|
| mantic |
Released
(1.1.7-0ubuntu2.2)
|
|
| noble |
Needed
|
|
| trusty |
Ignored
(end of standard support)
|
|
| upstream |
Released
(1.1.12)
|
|
| xenial |
Not vulnerable
(version not affected)
|
Severity score breakdown
| Parameter | Value |
|---|---|
| Base score | 8.6 |
| Attack vector | Local |
| Attack complexity | Low |
| Privileges required | None |
| User interaction | Required |
| Scope | Changed |
| Confidentiality | High |
| Integrity impact | High |
| Availability impact | High |
| Vector | CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H |