Search for packages
| purl | pkg:deb/debian/runc@1.0.3%2Bds1-1 |
| Vulnerability | Summary | Fixed by |
|---|---|---|
| This package is not known to be affected by vulnerabilities. | ||
| Vulnerability | Summary | Aliases |
|---|---|---|
| VCID-6j4q-p114-aaae | runc is a CLI tool for spawning and running containers according to the OCI specification. It was found that AppArmor can be bypassed when `/proc` inside the container is symlinked with a specific mount configuration. This issue has been fixed in runc version 1.1.5, by prohibiting symlinked `/proc`. See PR #3785 for details. users are advised to upgrade. Users unable to upgrade should avoid using an untrusted container image. |
CVE-2023-28642
GHSA-g2j6-57v7-gm8c |
| VCID-78xd-zy32-aaas | runc is a CLI tool for spawning and running containers according to the OCI specification. In affected versions it was found that rootless runc makes `/sys/fs/cgroup` writable in following conditons: 1. when runc is executed inside the user namespace, and the `config.json` does not specify the cgroup namespace to be unshared (e.g.., `(docker|podman|nerdctl) run --cgroupns=host`, with Rootless Docker/Podman/nerdctl) or 2. when runc is executed outside the user namespace, and `/sys` is mounted with `rbind, ro` (e.g., `runc spec --rootless`; this condition is very rare). A container may gain the write access to user-owned cgroup hierarchy `/sys/fs/cgroup/user.slice/...` on the host . Other users's cgroup hierarchies are not affected. Users are advised to upgrade to version 1.1.5. Users unable to upgrade may unshare the cgroup namespace (`(docker|podman|nerdctl) run --cgroupns=private)`. This is the default behavior of Docker/Podman/nerdctl on cgroup v2 hosts. or add `/sys/fs/cgroup` to `maskedPaths`. |
CVE-2023-25809
GHSA-m8cg-xc2p-r3fc |
| VCID-8few-q1n1-s7gr | 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. |
CVE-2024-45310
GHSA-jfvp-7x6p-h2pv |
| VCID-sxre-t5g1-aaaj | runc through 1.1.4 has Incorrect Access Control leading to Escalation of Privileges, related to libcontainer/rootfs_linux.go. To exploit this, an attacker must be able to spawn two containers with custom volume-mount configurations, and be able to run custom images. NOTE: this issue exists because of a CVE-2019-19921 regression. |
CVE-2023-27561
GHSA-vpvm-3wq2-2wvm |
| VCID-us2v-fh9z-aaaa | runc is a CLI tool for spawning and running containers on Linux according to the OCI specification. In runc, netlink is used internally as a serialization system for specifying the relevant container configuration to the `C` portion of the code (responsible for the based namespace setup of containers). In all versions of runc prior to 1.0.3, the encoder did not handle the possibility of an integer overflow in the 16-bit length field for the byte array attribute type, meaning that a large enough malicious byte array attribute could result in the length overflowing and the attribute contents being parsed as netlink messages for container configuration. This vulnerability requires the attacker to have some control over the configuration of the container and would allow the attacker to bypass the namespace restrictions of the container by simply adding their own netlink payload which disables all namespaces. The main users impacted are those who allow untrusted images with untrusted configurations to run on their machines (such as with shared cloud infrastructure). runc version 1.0.3 contains a fix for this bug. As a workaround, one may try disallowing untrusted namespace paths from your container. It should be noted that untrusted namespace paths would allow the attacker to disable namespace protections entirely even in the absence of this bug. |
CVE-2021-43784
GHSA-v95c-p5hm-xq8f |
| Date | Actor | Action | Vulnerability | Source | VulnerableCode Version |
|---|---|---|---|---|---|
| 2025-06-22T03:00:09.829514+00:00 | Debian Importer | Fixing | VCID-8few-q1n1-s7gr | https://security-tracker.debian.org/tracker/data/json | 36.1.3 |
| 2025-04-05T21:22:08.333461+00:00 | Debian Importer | Fixing | VCID-8few-q1n1-s7gr | https://security-tracker.debian.org/tracker/data/json | 36.0.0 |
| 2025-02-22T03:29:27.633456+00:00 | Debian Importer | Fixing | VCID-8few-q1n1-s7gr | https://security-tracker.debian.org/tracker/data/json | 35.1.0 |
| 2024-11-24T13:24:01.218191+00:00 | Debian Importer | Fixing | VCID-8few-q1n1-s7gr | https://security-tracker.debian.org/tracker/data/json | 35.0.0 |
| 2024-04-26T02:41:26.123879+00:00 | Debian Importer | Fixing | VCID-6j4q-p114-aaae | https://security-tracker.debian.org/tracker/data/json | 34.0.0rc4 |
| 2024-04-26T02:30:30.170210+00:00 | Debian Importer | Fixing | VCID-sxre-t5g1-aaaj | https://security-tracker.debian.org/tracker/data/json | 34.0.0rc4 |
| 2024-04-26T02:13:54.605593+00:00 | Debian Importer | Fixing | VCID-78xd-zy32-aaas | https://security-tracker.debian.org/tracker/data/json | 34.0.0rc4 |
| 2024-04-25T05:42:31.961037+00:00 | Debian Importer | Fixing | VCID-us2v-fh9z-aaaa | https://security-tracker.debian.org/tracker/data/json | 34.0.0rc4 |
| 2024-01-12T12:44:14.560393+00:00 | Debian Importer | Fixing | VCID-6j4q-p114-aaae | https://security-tracker.debian.org/tracker/data/json | 34.0.0rc2 |
| 2024-01-12T12:44:09.062247+00:00 | Debian Importer | Fixing | VCID-6j4q-p114-aaae | None | 34.0.0rc2 |
| 2024-01-12T12:32:32.436071+00:00 | Debian Importer | Fixing | VCID-sxre-t5g1-aaaj | https://security-tracker.debian.org/tracker/data/json | 34.0.0rc2 |
| 2024-01-12T12:32:14.591932+00:00 | Debian Importer | Fixing | VCID-sxre-t5g1-aaaj | None | 34.0.0rc2 |
| 2024-01-12T12:11:50.792214+00:00 | Debian Importer | Fixing | VCID-78xd-zy32-aaas | https://security-tracker.debian.org/tracker/data/json | 34.0.0rc2 |
| 2024-01-12T12:11:45.482479+00:00 | Debian Importer | Fixing | VCID-78xd-zy32-aaas | None | 34.0.0rc2 |
| 2024-01-11T07:25:04.196557+00:00 | Debian Importer | Fixing | VCID-us2v-fh9z-aaaa | https://security-tracker.debian.org/tracker/data/json | 34.0.0rc2 |
| 2024-01-11T07:24:51.700555+00:00 | Debian Importer | Fixing | VCID-us2v-fh9z-aaaa | None | 34.0.0rc2 |
| 2024-01-05T08:27:49.247745+00:00 | Debian Importer | Fixing | VCID-6j4q-p114-aaae | https://security-tracker.debian.org/tracker/data/json | 34.0.0rc1 |
| 2024-01-05T08:27:44.529601+00:00 | Debian Importer | Fixing | VCID-6j4q-p114-aaae | None | 34.0.0rc1 |
| 2024-01-05T08:21:16.775520+00:00 | Debian Importer | Fixing | VCID-sxre-t5g1-aaaj | https://security-tracker.debian.org/tracker/data/json | 34.0.0rc1 |
| 2024-01-05T08:21:11.751609+00:00 | Debian Importer | Fixing | VCID-sxre-t5g1-aaaj | None | 34.0.0rc1 |
| 2024-01-05T08:12:03.344918+00:00 | Debian Importer | Fixing | VCID-78xd-zy32-aaas | https://security-tracker.debian.org/tracker/data/json | 34.0.0rc1 |
| 2024-01-05T08:11:59.269021+00:00 | Debian Importer | Fixing | VCID-78xd-zy32-aaas | None | 34.0.0rc1 |
| 2024-01-04T18:12:08.991813+00:00 | Debian Importer | Fixing | VCID-us2v-fh9z-aaaa | https://security-tracker.debian.org/tracker/data/json | 34.0.0rc1 |
| 2024-01-04T18:11:59.824026+00:00 | Debian Importer | Fixing | VCID-us2v-fh9z-aaaa | None | 34.0.0rc1 |