{"id":"EUVD-2024-2819","revision":"34233502bbe04a8bb007d3be670bbd82","records":[{"revision":"34233502bbe04a8bb007d3be670bbd82","observedAt":"2026-10-31T22:07:10.808+00:00","statement":{"source":"euvd","id":"EUVD-2024-2819","aliases":["CVE-2024-45310","GHSA-jfvp-7x6p-h2pv"],"title":"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…","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.\n\nSome 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\nuser 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.","state":0,"publishedAt":null,"modifiedAt":null,"affected":[],"metrics":[{"system":"EUVD CVSS 3.1","vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:N/I:L/A:N","score":3.6,"severity":null}],"references":["https://github.com/opencontainers/runc/security/advisories/GHSA-jfvp-7x6p-h2pv","https://github.com/opencontainers/runc/pull/4359","https://github.com/opencontainers/runc/commit/63c2908164f3a1daea455bf5bcd8d363d70328c7","https://github.com/opencontainers/runc/commit/8781993968fd964ac723ff5f360b6f259e809a3e","https://github.com/opencontainers/runc/commit/f0b652ea61ff6750a8fcc69865d45a7abf37accf"],"sourceUrl":"https://euvd.enisa.europa.eu/vulnerability/EUVD-2024-2819","license":"ENISA EUVD · source terms and attribution apply","enrichment":{"sourceStatus":null,"weaknesses":[],"productCriteria":[],"sourceDates":{"datePublished":"Sep 3, 2024, 7:07:34 PM","dateUpdated":"Feb 21, 2025, 6:03:30 PM"},"relatedAdvisories":[{"id":"SUSE-SU-2024:3222-1","title":"Security update for runc","vulnerabilityIds":["CVE-2024-45310"]},{"id":"openSUSE-SU-2026:21379-1","title":"Security update for ctop","vulnerabilityIds":["CVE-2022-21698","CVE-2024-45310","CVE-2026-10722","CVE-2026-33814","CVE-2026-39821"]},{"id":"SUSE-SU-2025:02198-1","title":"Security update for runc","vulnerabilityIds":["CVE-2024-45310"]},{"id":"openSUSE-SU-2026:10842-1","title":"apptainer-1.4.5-5.1 on GA media","vulnerabilityIds":["CVE-2024-45310","CVE-2026-33814","CVE-2026-39827","CVE-2026-39831","CVE-2026-39832","CVE-2026-39835"]},{"id":"SUSE-SU-2025:20046-1","title":"Security update for runc","vulnerabilityIds":["CVE-2024-45310"]},{"id":"openSUSE-SU-2026:11153-1","title":"cadvisor-0.60.3-1.1 on GA media","vulnerabilityIds":["CVE-2024-45310","CVE-2026-10722","CVE-2026-33186","CVE-2026-39821"]},{"id":"RHSA-2026:3406","title":"Red Hat Security Advisory: New container image: rhceph-9.0","vulnerabilityIds":["CVE-2021-23358","CVE-2024-45310","CVE-2024-51744","CVE-2024-55565","CVE-2025-6176","CVE-2025-7783","CVE-2025-14104","CVE-2025-22868","CVE-2025-26791","CVE-2025-50181","CVE-2025-50182","CVE-2025-66418","CVE-2025-66471","CVE-2026-21441"]},{"id":"SUSE-SU-2025:02198-2","title":"Security update for runc","vulnerabilityIds":["CVE-2024-45310"]},{"id":"SUSE-SU-2026:20571-1","title":"Security update for kubevirt","vulnerabilityIds":["CVE-2024-45310","CVE-2025-22872","CVE-2025-64324","CVE-2025-64432","CVE-2025-64433","CVE-2025-64434","CVE-2025-64435","CVE-2025-64437"]},{"id":"SUSE-SU-2025:20353-1","title":"Security update for runc","vulnerabilityIds":["CVE-2024-45310"]},{"id":"msrc_CVE-2024-45310","title":"runc can be confused to create empty files/directories on the host","vulnerabilityIds":["CVE-2024-45310"]},{"id":"SUSE-SU-2026:20610-1","title":"Security update for kubevirt","vulnerabilityIds":["CVE-2024-45310","CVE-2025-22872","CVE-2025-64324","CVE-2025-64432","CVE-2025-64433","CVE-2025-64434","CVE-2025-64435","CVE-2025-64437"]},{"id":"openSUSE-SU-2024:14312-1","title":"runc-1.2.0~rc3-1.1 on GA media","vulnerabilityIds":["CVE-2024-45310"]},{"id":"openSUSE-SU-2026:20281-1","title":"Security update for kubevirt","vulnerabilityIds":["CVE-2024-45310","CVE-2025-22872","CVE-2025-64324","CVE-2025-64432","CVE-2025-64433","CVE-2025-64434","CVE-2025-64435","CVE-2025-64437"]},{"id":"openSUSE-SU-2026:20834-1","title":"Security update for apptainer","vulnerabilityIds":["CVE-2024-45310","CVE-2026-33814","CVE-2026-39827","CVE-2026-39828","CVE-2026-39829","CVE-2026-39830","CVE-2026-39831","CVE-2026-39832","CVE-2026-39833","CVE-2026-39834","CVE-2026-39835","CVE-2026-42508","CVE-2026-46595","CVE-2026-46597","CVE-2026-46598"]},{"id":"openSUSE-SU-2025:15424-1","title":"govulncheck-vulndb-0.0.20250807T150727-1.1 on GA media","vulnerabilityIds":["CVE-2015-7561","CVE-2016-9962","CVE-2017-1000056","CVE-2017-1002102","CVE-2018-1002100","CVE-2018-1002101","CVE-2018-16733","CVE-2018-19184","CVE-2019-1002100","CVE-2019-1002101","CVE-2019-11245","CVE-2019-11251","CVE-2019-11253","CVE-2020-26240","CVE-2020-26241","CVE-2020-8551","CVE-2020-8555","CVE-2020-8557","CVE-2020-8558","CVE-2020-8562","CVE-2020-8563","CVE-2020-8566","CVE-2021-25735","CVE-2021-25736","CVE-2021-25737","CVE-2021-25741","CVE-2021-25743","CVE-2021-30465","CVE-2022-29162","CVE-2022-29177","CVE-2022-3162","CVE-2022-3294","CVE-2023-2431","CVE-2023-25809","CVE-2023-2727","CVE-2023-2728","CVE-2023-27561","CVE-2023-28642","CVE-2023-5528","CVE-2024-45310","CVE-2024-5321","CVE-2025-3445","CVE-2025-47907","CVE-2025-47908"]},{"id":"WID-SEC-W-2025-0632","title":"IBM MQ: Mehrere Schwachstellen","vulnerabilityIds":["CVE-2024-45310","CVE-2024-9341"]},{"id":"SUSE-SU-2025:1374-1","title":"Security update for runc","vulnerabilityIds":["CVE-2024-45310"]},{"id":"SUSE-SU-2026:0439-1","title":"Security update for apptainer","vulnerabilityIds":["CVE-2024-45310","CVE-2025-22869","CVE-2025-22870","CVE-2025-22872","CVE-2025-27144","CVE-2025-47913","CVE-2025-47914","CVE-2025-58181","CVE-2025-65105","CVE-2025-8556"]},{"id":"SUSE-SU-2026:20551-1","title":"Security update for kubevirt","vulnerabilityIds":["CVE-2024-45310","CVE-2025-22872","CVE-2025-64324","CVE-2025-64432","CVE-2025-64433","CVE-2025-64434","CVE-2025-64435","CVE-2025-64437"]},{"id":"openSUSE-SU-2026:21265-1","title":"Security update for cadvisor","vulnerabilityIds":["CVE-2024-45310","CVE-2025-22868","CVE-2026-10722","CVE-2026-33186","CVE-2026-39821"]},{"id":"SUSE-SU-2024:3324-1","title":"Security update for runc","vulnerabilityIds":["CVE-2024-45310"]},{"id":"RHSA-2026:37387","title":"Red Hat Security Advisory: Red Hat OpenShift Data Foundation 4.22.0 security, enhancement & bug fix update","vulnerabilityIds":["CVE-2024-25621","CVE-2024-40635","CVE-2024-45310","CVE-2025-8766","CVE-2025-21613","CVE-2025-21614","CVE-2025-22870","CVE-2025-47911","CVE-2025-52881","CVE-2025-54410","CVE-2025-58058","CVE-2025-64329","CVE-2025-66506","CVE-2026-22772","CVE-2026-23831","CVE-2026-24117","CVE-2026-25680","CVE-2026-25681","CVE-2026-25934","CVE-2026-27136","CVE-2026-27141","CVE-2026-27903","CVE-2026-33540","CVE-2026-33747","CVE-2026-33748","CVE-2026-33814","CVE-2026-34986","CVE-2026-35172","CVE-2026-35469","CVE-2026-39821","CVE-2026-39827","CVE-2026-39828","CVE-2026-39829","CVE-2026-39830","CVE-2026-39831","CVE-2026-39832","CVE-2026-39833","CVE-2026-39834","CVE-2026-39835","CVE-2026-39883","CVE-2026-41506","CVE-2026-41567","CVE-2026-41568","CVE-2026-42502","CVE-2026-42506","CVE-2026-42508","CVE-2026-44740","CVE-2026-45571","CVE-2026-46595","CVE-2026-46597","CVE-2026-46598"]},{"id":"SUSE-SU-2025:20335-1","title":"Security update for runc","vulnerabilityIds":["CVE-2024-45310"]},{"id":"SUSE-SU-2026:0479-1","title":"Security update for kubevirt, virt-api-container, virt-controller-container, virt-exportproxy-container, virt-exportserver-container, virt-handler-container, virt-launcher-container, virt-libguestfs-tools-container, virt-operator-container, virt-pr-helper-container, virt-synchronization-controller-container","vulnerabilityIds":["CVE-2024-45310","CVE-2025-64435"]}],"note":"EUVD source date text has no stated timezone and is retained without inventing a UTC instant. Related bulletin membership is not an alias, common cause or applicability claim. A missing vector with a zero score is treated as unrated. Complete vendor/product and underlying source evidence remains in the original JSON."},"key":"euvd:EUVD-2024-2819","identifiers":["EUVD-2024-2819","CVE-2024-45310","GHSA-jfvp-7x6p-h2pv"]},"retained":false,"historicalAffected":[]}],"coverage":[]}