CVE-2020-15257

Aliases:GHSA-36xw-fx78-c5r4GO-2022-0784
Advisory lineage Upstream: 0 Downstream: 13
Modified
Published: 01 Dec 2020, 02:30
Last modified:04 Aug 2024, 13:15

Vulnerability Summary

Overall Risk (default)
low
23/100
CVSS Score
5.2 MEDIUM
v3.1 (cve.org)
EPSS Score
13.3% MEDIUM
13% probability +2.16%
KEV
Not listed
Ransomware
No reports
Public exploits
None found
Dark Web
Not detected

Timeline

01 Dec 2020, 02:30
Published
Vulnerability first disclosed
04 Aug 2024, 13:15
Last Modified
Vulnerability information updated

Description

containerd is an industry-standard container runtime and is available as a daemon for Linux and Windows. In containerd before versions 1.3.9 and 1.4.3, the containerd-shim API is improperly exposed to host network containers. Access controls for the shim’s API socket verified that the connecting process had an effective UID of 0, but did not otherwise restrict access to the abstract Unix domain socket. This would allow malicious containers running in the same network namespace as the shim, with an effective UID of 0 but otherwise reduced privileges, to cause new processes to be run with elevated privileges. This vulnerability has been fixed in containerd 1.3.9 and 1.4.3. Users should update to these versions as soon as they are released. It should be noted that containers started with an old version of containerd-shim should be stopped and restarted, as running containers will continue to be vulnerable even after an upgrade. If you are not providing the ability for untrusted users to start containers in the same network namespace as the shim (typically the "host" network namespace, for example with docker run --net=host or hostNetwork: true in a Kubernetes pod) and run with an effective UID of 0, you are not vulnerable to this issue. If you are running containers with a vulnerable configuration, you can deny access to all abstract sockets with AppArmor by adding a line similar to deny unix addr=@**, to your policy. It is best practice to run containers with a reduced set of privileges, with a non-zero UID, and with isolated namespaces. The containerd maintainers strongly advise against sharing namespaces with the host. Reducing the set of isolation mechanisms used for a container necessarily increases that container's privilege, regardless of what container runtime is used for running that container.

CVSS Metrics

  • v3.1•MEDIUM•Score: 5.2CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N
  • v2.0•LOW•Score: 3.6AV:L/AC:L/Au:N/C:P/I:P/A:N

EPSS Trends

Current EPSS score: 13.30%• Percentile: 94%

Techniques & Countermeasures

  • CWE-669•Incorrect Resource Transfer Between Spheres

    The product does not properly transfer a resource/behavior to another sphere, or improperly imports a resource/behavior from another sphere, in a manner that provides unintended control over that resource.

Affected Systems

  • containerd•containerd

    < 1.3.9 | ≥ 1.4.0, < 1.4.3

  • debian•debian_linux

    10.0

  • fedoraproject•fedora

    33

  • github.com/containerd•containerd

    < 1.3.9 | ≥ 1.4.0, < 1.4.3

  • linuxfoundation•containerd

    < 1.3.9 | ≥ 1.4.0, < 1.4.3

References (9)