Vulnerability in Containerd
CVE-2020-15257
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.
Published · last modified .
CVSS v3 metric
CVSS v3 base score 5.2 (Medium). Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N.
EPSS exploit prediction
EPSS 0.031, 88.1th percentile (scored ); unchanged over 30 days. About EPSS.
Affected products
- Containerd — versions < 1.3.9, >= 1.4.0, < 1.4.3
- Linuxfoundation Containerd
- Debian Linux — versions 10.0
- Fedoraproject Fedora — versions 33
Weakness classification (CWE)
Public exploits and proof-of-concept code
1 public repository with exploit or proof-of-concept code for this CVE:
- nccgroup/abstractshimmer (18 stars, last pushed 2021-01-12): Proof of concept for CVE-2020-15257 in containerd.
Also mentioned in 54 other repositories (43622283/awesome-cloud-native-security, 8-cm/kube-dump, adavarski/HomeLab-k8s-DevSecOps-playground, …). These reference the CVE in a list, notes or a scanner and are not exploit code for it.
References
- github.com/containerd/containerd/security/advisories/GHSA-36xw-fx78-c5r4 (Third Party Advisory, Mitigation)
- github.com/containerd/containerd/commit/4a4bb851f5da563ff6e68a83dc837c7699c469ad (Patch, Third Party Advisory)
- github.com/containerd/containerd/releases/tag/v1.4.3 (Third Party Advisory)
- FEDORA-2020-baeb8dbaea (vendor-advisory)
- DSA-4865 (vendor-advisory, Third Party Advisory)
- GLSA-202105-33 (vendor-advisory, Third Party Advisory)
This CVE has public exploit evidence. See the latest CVEs with public exploits.