Skip to content

CVE-2024-21626

Linuxfoundation Runc information disclosure

8.6 HIGHPublic exploitEPSS 18.9%
  1. Published31 Jan 2024

Description

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.

CVSS 3.1 breakdown

Attack vectorLocal
Attack complexityLow
Privileges requiredNone
User interactionRequired
ScopeChanged
ConfidentialityHigh
IntegrityHigh
AvailabilityHigh
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H

Affected products

Linuxfoundation Runc< 1.1.12
Fedoraproject Fedora39

Frequently asked

Is CVE-2024-21626 being actively exploited?

CVE-2024-21626 is not in the CISA KEV catalog. A public exploit reference exists, so treat it as exploitable. Its EPSS exploit probability is 18.9%.

How severe is CVE-2024-21626?

CVE-2024-21626 has a CVSS 3.1 base score of 8.6, rated high. EPSS estimates a 18.9% probability of exploitation.

Which products are affected by CVE-2024-21626?

Affected products include Linuxfoundation Runc, Fedoraproject Fedora.

How do I fix CVE-2024-21626?

Upgrade affected software to a fixed version, for example Linuxfoundation Runc 1.1.12 or later, then confirm no affected versions remain in your inventory.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2024-21626 against the real software inventory on every managed device, as each hourly inventory arrives. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.

Get Patch this first every Monday

Five vulnerabilities that matter this week, ranked on real exploitation. Plain language, one email, no spam.

You can unsubscribe with one click from every issue. We handle your details as described in our privacy policy.

Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.