Integer Overflow or Wraparound Affecting runc package, versions *
Threat Intelligence
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk ID SNYK-CENTOS8-RUNC-2311675
- published 7 Dec 2021
- disclosed 6 Dec 2021
Introduced: 6 Dec 2021
CVE-2021-43784 Open this link in a new tabHow to fix?
There is no fixed version for Centos:8 runc.
NVD Description
Note: Versions mentioned in the description apply only to the upstream runc package and not the runc package as distributed by Centos.
See How to fix? for Centos:8 relevant fixed versions and status.
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.
References
- https://github.com/opencontainers/runc/security/advisories/GHSA-v95c-p5hm-xq8f
- https://access.redhat.com/security/cve/CVE-2021-43784
- https://bugs.chromium.org/p/project-zero/issues/detail?id=2241
- https://github.com/opencontainers/runc/commit/9c444070ec7bb83995dbc0185da68284da71c554
- https://github.com/opencontainers/runc/commit/d72d057ba794164c3cce9451a00b72a78b25e1ae
- https://github.com/opencontainers/runc/commit/f50369af4b571e358f20b139eea52d612eb55eed
- https://lists.debian.org/debian-lts-announce/2021/12/msg00005.html
- https://lists.debian.org/debian-lts-announce/2024/02/msg00005.html