rpm package
opensuse/runc&distro=openSUSE Leap Micro 5.3
pkg:rpm/opensuse/runc&distro=openSUSE%20Leap%20Micro%205.3
Vulnerabilities (5)
| CVE | Sev | CVSS | KEV | Affected versions | Fixed in | Published | Description |
|---|---|---|---|---|---|---|---|
| CVE-2024-21626 | — | < 1.1.11-150000.58.1 | 1.1.11-150000.58.1 | Jan 31, 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 h | ||
| CVE-2023-25809 | — | < 1.1.5-150000.41.1 | 1.1.5-150000.41.1 | Mar 29, 2023 | 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 n | ||
| CVE-2023-28642 | — | < 1.1.5-150000.41.1 | 1.1.5-150000.41.1 | Mar 29, 2023 | 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 prohibitin | ||
| CVE-2023-27561 | — | < 1.1.5-150000.41.1 | 1.1.5-150000.41.1 | Mar 3, 2023 | 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 is | ||
| CVE-2022-1996 | — | < 1.1.10-150000.55.1 | 1.1.10-150000.55.1 | Jun 6, 2022 | Authorization Bypass Through User-Controlled Key in GitHub repository emicklei/go-restful prior to v3.8.0. |
- CVE-2024-21626Jan 31, 2024affected < 1.1.11-150000.58.1fixed 1.1.11-150000.58.1
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 h
- CVE-2023-25809Mar 29, 2023affected < 1.1.5-150000.41.1fixed 1.1.5-150000.41.1
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 n
- CVE-2023-28642Mar 29, 2023affected < 1.1.5-150000.41.1fixed 1.1.5-150000.41.1
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 prohibitin
- CVE-2023-27561Mar 3, 2023affected < 1.1.5-150000.41.1fixed 1.1.5-150000.41.1
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 is
- CVE-2022-1996Jun 6, 2022affected < 1.1.10-150000.55.1fixed 1.1.10-150000.55.1
Authorization Bypass Through User-Controlled Key in GitHub repository emicklei/go-restful prior to v3.8.0.