runc can be confused to create empty files/directories on the host

Description

runc is a CLI tool for spawning and running containers according to the OCI specification. runc 1.1.13 and earlier, as well as 1.2.0-rc2 and earlier, can be tricked into creating empty files or directories in arbitrary locations in the host filesystem by sharing a volume between two containers and exploiting a race with `os.MkdirAll`. While this could be used to create empty files, existing files would not be truncated. An attacker must have the ability to start containers using some kind of custom volume configuration. Containers using user namespaces are still affected, but the scope of places an attacker can create inodes can be significantly reduced. Sufficiently strict LSM policies (SELinux/Apparmor) can also in principle block this attack -- we suspect the industry standard SELinux policy may restrict this attack's scope but the exact scope of protection hasn't been analysed. This is exploitable using runc directly as well as through Docker and Kubernetes. The issue is fixed in runc v1.1.14 and v1.2.0-rc3. Some workarounds are available. Using user namespaces restricts this attack fairly significantly such that the attacker can only create inodes in directories that the remapped root user/group has write access to. Unless the root user is remapped to an actual user on the host (such as with rootless containers that don't use `/etc/sub[ug]id`), this in practice means that an attacker would only be able to create inodes in world-writable directories. A strict enough SELinux or AppArmor policy could in principle also restrict the scope if a specific label is applied to the runc runtime, though neither the extent to which the standard existing policies block this attack nor what exact policies are needed to sufficiently restrict this attack have been thoroughly tested.

Timeline

Scores

EPSS (exploitation in 30 days)

0.32% · top 75% of all CVEs (7 Nov 2026)

CISA SSVC

Exploitation: none · Automatable: no · Technical impact: partial

The list uses the assigner's score when there is one, then CISA's, then NVD's: Low 3.6.

Weakness

• CWE-363: Race Condition Enabling Link Following (opens in a new tab)All about CWE-363 and its CVEs
• CWE-61: UNIX Symbolic Link (Symlink) Following (opens in a new tab)All about CWE-61 and its CVEs

Affected products

• opencontainers · runc

  • affected < 1.1.14
  • affected >= 1.2.0-rc-1, < 1.2.0-rc.3

Affected packages

From reviewed advisories of the GitHub Advisory Database.

• Gogithub.com/opencontainers/runcGHSA-jfvp-7x6p-h2pv (opens in a new tab)

References (7)

• https://github.com/opencontainers/runc/security/advisories/GHSA-jfvp-7x6p-h2pv (opens in a new tab)x_refsource_CONFIRM
• https://github.com/opencontainers/runc/pull/4359 (opens in a new tab)x_refsource_MISC
• https://github.com/opencontainers/runc/commit/63c2908164f3a1daea455bf5bcd8d363d70328c7 (opens in a new tab)x_refsource_MISC
• https://github.com/opencontainers/runc/commit/8781993968fd964ac723ff5f360b6f259e809a3e (opens in a new tab)x_refsource_MISC
• https://github.com/opencontainers/runc/commit/f0b652ea61ff6750a8fcc69865d45a7abf37accf (opens in a new tab)x_refsource_MISC
• http://www.openwall.com/lists/oss-security/2024/09/03/1 (opens in a new tab)
• https://security.netapp.com/advisory/ntap-20250221-0008/ (opens in a new tab)

Sources

The same CVE in the primary databases and aggregators, to check against.

• CVE.org record (opens in a new tab)
• CVE List JSON (GitHub) (opens in a new tab)
• NVD (opens in a new tab)
• FIRST EPSS (opens in a new tab)
• OSV.dev (opens in a new tab)
• GitHub Advisory GHSA-jfvp-7x6p-h2pv (opens in a new tab)
• CIRCL Vulnerability-Lookup (opens in a new tab)

Badge for a README or a ticket

[![CVE-2024-45310](https://trackcve.app/badge/CVE-2024-45310.svg)](https://trackcve.app/cve/CVE-2024-45310)

Record last updated 21 Feb 2025, 18:03 UTC.