Register | Log in

runc

Open Container Project - runtime

Choose email to subscribe with

general

source: runc (main)
version: 1.1.4+ds1-1
maintainer: Debian Go Packaging Team (DMD)
uploaders: Dmitry Smirnov [DMD] – Tim Potter [DMD] – Alexandre Viau [DMD]
arch: all any
std-ver: 4.6.1
VCS: Git (Browse, QA)

versions [more versions can be listed by madison] [old versions available from snapshot.debian.org]

[pool directory]

o-o-stable: 0.1.1+dfsg1-2+deb9u1
o-o-sec: 0.1.1+dfsg1-2+deb9u3
oldstable: 1.0.0~rc6+dfsg1-3
stable: 1.0.0~rc93+ds1-5+deb11u2
testing: 1.1.4+ds1-1
unstable: 1.1.4+ds1-1

versioned links

0.1.1+dfsg1-2+deb9u1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
0.1.1+dfsg1-2+deb9u3: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
1.0.0~rc6+dfsg1-3: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
1.0.0~rc93+ds1-5+deb11u2: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
1.1.4+ds1-1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]

binaries

golang-github-opencontainers-runc-dev
runc

action needed

1 security issue in sid high

There is 1 open security issue in sid.

1 important issue:

CVE-2023-27561: 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.

Created: 2023-03-04 Last update: 2023-03-05 06:00

6 security issues in buster high

There are 6 open security issues in buster.

2 important issues:

CVE-2021-30465: runc before 1.0.0-rc95 allows a Container Filesystem Breakout via Directory Traversal. To exploit the vulnerability, an attacker must be able to create multiple containers with a fairly specific mount configuration. The problem occurs via a symlink-exchange attack that relies on a race condition.
CVE-2023-27561: 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.

3 issues postponed or untriaged:

CVE-2019-16884: (needs triaging) runc through 1.0.0-rc8, as used in Docker through 19.03.2-ce and other products, allows AppArmor restriction bypass because libcontainer/rootfs_linux.go incorrectly checks mount targets, and thus a malicious Docker image can mount over a /proc directory.
CVE-2019-19921: (needs triaging) runc through 1.0.0-rc9 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. (This vulnerability does not affect Docker due to an implementation detail that happens to block the attack.)
CVE-2022-29162: (needs triaging) runc is a CLI tool for spawning and running containers on Linux according to the OCI specification. A bug was found in runc prior to version 1.1.2 where `runc exec --cap` created processes with non-empty inheritable Linux process capabilities, creating an atypical Linux environment and enabling programs with inheritable file capabilities to elevate those capabilities to the permitted set during execve(2). This bug did not affect the container security sandbox as the inheritable set never contained more capabilities than were included in the container's bounding set. This bug has been fixed in runc 1.1.2. This fix changes `runc exec --cap` behavior such that the additional capabilities granted to the process being executed (as specified via `--cap` arguments) do not include inheritable capabilities. In addition, `runc spec` is changed to not set any inheritable capabilities in the created example OCI spec (`config.json`) file.

1 ignored issue:

CVE-2021-43784: 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.

Created: 2022-07-04 Last update: 2023-03-05 06:00

2 security issues in bullseye high

There are 2 open security issues in bullseye.

1 important issue:

CVE-2023-27561: 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.

1 ignored issue:

CVE-2021-43784: 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.

Created: 2022-07-04 Last update: 2023-03-05 06:00

1 security issue in bookworm high

There is 1 open security issue in bookworm.

1 important issue:

CVE-2023-27561: 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.

Created: 2023-03-04 Last update: 2023-03-05 06:00

lintian reports 4 warnings normal

Lintian reports 4 warnings about this package. You should make the package lintian clean getting rid of them.

Created: 2022-08-18 Last update: 2023-02-04 23:35

debian/patches: 7 patches to forward upstream low

Among the 11 debian patches available in version 1.1.4+ds1-1 of the package, we noticed the following issues:

7 patches where the metadata indicates that the patch has not yet been forwarded upstream. You should either forward the patch upstream or update the metadata to document its real status.

Created: 2023-02-26 Last update: 2023-02-27 20:59

Standards version of the package is outdated. wishlist

The package should be updated to follow the last version of Debian Policy (Standards-Version 4.6.2 instead of 4.6.1).

Created: 2022-12-17 Last update: 2022-12-17 19:17

news

[2022-09-04] runc 1.1.4+ds1-1 MIGRATED to testing (Debian testing watch)
[2022-08-27] Accepted runc 1.1.4+ds1-1 (source) into unstable (Shengjing Zhu)
[2022-08-20] runc 1.1.3+ds1-7 MIGRATED to testing (Debian testing watch)
[2022-08-17] Accepted runc 1.1.3+ds1-7 (source) into unstable (Reinhard Tartler)
[2022-08-17] Accepted runc 1.1.3+ds1-6 (source) into unstable (Reinhard Tartler)
[2022-08-17] Accepted runc 1.1.3+ds1-3 (source) into unstable (Reinhard Tartler)
[2022-07-05] Accepted runc 1.1.3+ds1-5 (source) into experimental (Shengjing Zhu)
[2022-07-04] Accepted runc 1.1.3+ds1-4 (source) into experimental (Shengjing Zhu)
[2022-06-21] runc 1.1.3+ds1-2 MIGRATED to testing (Debian testing watch)
[2022-06-20] Accepted runc 1.1.3+ds1-3 (source) into experimental (Shengjing Zhu)
[2022-06-19] Accepted runc 1.1.3+ds1-2 (source) into unstable (Shengjing Zhu)
[2022-06-19] runc 1.1.3+ds1-1 MIGRATED to testing (Debian testing watch)
[2022-06-18] Accepted runc 1.0.0~rc93+ds1-5+deb11u2 (source) into proposed-updates->stable-new, proposed-updates (Debian FTP Masters) (signed by: Reinhard Tartler)
[2022-06-18] Accepted runc 1.0.0~rc93+ds1-5+deb11u1 (source) into proposed-updates->stable-new, proposed-updates (Debian FTP Masters) (signed by: Reinhard Tartler)
[2022-06-13] Accepted runc 1.1.3+ds1-1 (source) into unstable (Shengjing Zhu)
[2022-04-02] runc 1.1.1+ds1-1 MIGRATED to testing (Debian testing watch)
[2022-03-29] Accepted runc 1.1.1+ds1-1 (source) into unstable (Shengjing Zhu)
[2022-02-09] runc 1.1.0+ds1-1 MIGRATED to testing (Debian testing watch)
[2022-02-09] runc 1.1.0+ds1-1 MIGRATED to testing (Debian testing watch)
[2022-02-06] Accepted runc 1.1.0+ds1-1 (source) into unstable (Shengjing Zhu)
[2021-12-14] Accepted runc 1.1.0~rc.1+ds1-1 (source) into experimental (Shengjing Zhu)
[2021-12-09] runc 1.0.3+ds1-1 MIGRATED to testing (Debian testing watch)
[2021-12-06] Accepted runc 0.1.1+dfsg1-2+deb9u3 (source all amd64) into oldoldstable (Chris Lamb)
[2021-12-06] Accepted runc 1.0.3+ds1-1 (source) into unstable (Shengjing Zhu)
[2021-10-15] runc 1.0.2+ds1-2 MIGRATED to testing (Debian testing watch)
[2021-10-10] Accepted runc 1.0.2+ds1-2 (source) into unstable (Shengjing Zhu)
[2021-08-26] runc 1.0.2+ds1-1 MIGRATED to testing (Debian testing watch)
[2021-08-23] Accepted runc 1.0.2+ds1-1 (source) into unstable (Shengjing Zhu)
[2021-08-23] runc 1.0.1+ds1-2 MIGRATED to testing (Debian testing watch)
[2021-08-20] Accepted runc 1.0.1+ds1-2 (source) into unstable (Shengjing Zhu)

1
2

bugs [bug history graph]

all: 0

links

homepage
lintian (0, 4)
buildd: logs, checks, reproducibility, cross
popcon
browse source code
edit tags
other distros
security tracker
screenshots
debian patches
debci

ubuntu

[Information about Ubuntu for Debian Developers]

version: 1.1.4-0ubuntu1
2 bugs
patches for 1.1.4-0ubuntu1

Debian Package Tracker — Copyright 2013-2018 The Distro Tracker Developers

Report problems to the tracker.debian.org pseudo-package in the Debian BTS.

Documentation — Bugs — Git Repository — Contributing