CVE-2020-15257: containerd-shim API Exposed to Host Network Containers
Noroxi assessment
Priority: Monitor (action score 21/100)
- Public proof-of-concept code exists (GitHub); there is no record of exploitation in the wild.
- Probability of exploitation in the next 30 days: 3.1% (FIRST EPSS); higher than 88% of all records.
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: containerd (Alpine:v3.11) 1.3.9-r0; containerd (Alpine:v3.12) 1.4.3-r0; docker (Alpine:v3.12) 19.03.14-r0.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to containerd (Alpine:v3.11) 1.3.9-r0; containerd (Alpine:v3.12) 1.4.3-r0; docker (Alpine:v3.12) 19.03.14-r0 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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
- Nov 30, 2020
- Updated
- Jun 16, 2026
- EPSS
- 3.1% · 88th percentile
- CWE
- CWE-669
Report tools
Action score
21
Low priority for now.
- CVSS
- 20 / 40 · 5.2 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 3.1%
CNA vs NVD score
- NVD
- 5.2
- CNA · GitHub_M
- 5.2
- agree
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- Proof of concept exists, no weaponized module
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linuxfoundation | containerd | cpe:2.3:a:linuxfoundation:containerd |
| fedoraproject | fedora | cpe:2.3:o:fedoraproject:fedora |
| debian | debian linux | cpe:2.3:o:debian:debian_linux |
Using containerd? Add it to your stack and be the first to know about CVEs like this one. (Docker)
Versions reported by the vendor
Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.
containerd containerd
- < 1.3.9, >= 1.4.0, < 1.4.3affected
Affected versions · NVD (4)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- debian debian linux10.0
- fedoraproject fedora33
- linuxfoundation containerdbefore 1.3.9
- linuxfoundation containerd1.4.0 and later · before 1.4.3
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Alpine:v3.11 | containerd | from 1.4.0 · before 1.3.9-r0 | 1.3.9-r0 |
| Alpine:v3.12 | containerd | from 1.4.0 · before 1.4.3-r0 | 1.4.3-r0 |
| Alpine:v3.12 | docker | before 19.03.14-r0 | 19.03.14-r0 |
| Alpine:v3.13 | k3s | before 1.19.4.2-r0 | 1.19.4.2-r0 |
| Debian:10 | docker.io | before 18.09.1+dfsg1-7.1+deb10u3 | 18.09.1+dfsg1-7.1+deb10u3 |
| Debian:12 | containerd | before 1.4.3~ds1-1 | 1.4.3~ds1-1 |
| Debian:12 | docker.io | before 20.10.0~rc1+dfsg2-1 | 20.10.0~rc1+dfsg2-1 |
| Go | github.com/containerd/containerd | from 1.4.0 · before 1.4.3 | 1.4.3 |
| Go | github.com/containerd/containerd | before 1.3.9 | 1.3.9 |
| openSUSE:Leap 15.2 | containerd | before 1.3.9-lp152.2.3.1 | 1.3.9-lp152.2.3.1 |
| openSUSE:Leap 15.2 | docker | before 19.03.15_ce-lp152.2.3.1 | 19.03.15_ce-lp152.2.3.1 |
| openSUSE:Leap 15.2 | docker-runc | before 1.0.0rc10+gitr3981_dc9208a3303f-lp152.2.3.1 | 1.0.0rc10+gitr3981_dc9208a3303f-lp152.2.3.1 |
| openSUSE:Leap 15.2 | fish | before 2.7.1-lp152.5.3.1 | 2.7.1-lp152.5.3.1 |
| openSUSE:Leap 15.2 | golang-github-docker-libnetwork | before 0.7.0.1+gitr2908_55e924b8a842-lp152.2.3.1 | 0.7.0.1+gitr2908_55e924b8a842-lp152.2.3.1 |
| openSUSE:Tumbleweed | containerd | before 1.4.8-2.2 | 1.4.8-2.2 |
| openSUSE:Tumbleweed | docker | before 20.10.6_ce-2.1 | 20.10.6_ce-2.1 |
| SUSE:Linux Enterprise Module for Containers 12 | containerd | before 1.3.9-16.32.1 | 1.3.9-16.32.1 |
| SUSE:Linux Enterprise Module for Containers 12 | docker | before 19.03.14_ce-98.57.1 | 19.03.14_ce-98.57.1 |
| SUSE:Linux Enterprise Module for Containers 12 | docker-runc | before 1.0.0rc10+gitr3981_dc9208a3303f-1.49.1 | 1.0.0rc10+gitr3981_dc9208a3303f-1.49.1 |
| SUSE:Linux Enterprise Module for Containers 12 | golang-github-docker-libnetwork | before 0.7.0.1+gitr2908_55e924b8a842-34.1 | 0.7.0.1+gitr2908_55e924b8a842-34.1 |
| SUSE:Linux Enterprise Module for Containers 15 SP2 | containerd | before 1.3.9-5.29.3 | 1.3.9-5.29.3 |
| SUSE:Linux Enterprise Module for Containers 15 SP2 | docker | before 19.03.15_ce-6.43.3 | 19.03.15_ce-6.43.3 |
| SUSE:Linux Enterprise Module for Containers 15 SP2 | docker-runc | before 1.0.0rc10+gitr3981_dc9208a3303f-6.45.3 | 1.0.0rc10+gitr3981_dc9208a3303f-6.45.3 |
| SUSE:Linux Enterprise Module for Containers 15 SP2 | golang-github-docker-libnetwork | before 0.7.0.1+gitr2908_55e924b8a842-4.28.3 | 0.7.0.1+gitr2908_55e924b8a842-4.28.3 |
Same product
linuxfoundation: all recordsOther highest-scoring records for the same primary product.
- CVE-2022-23648Insecure handling of image volumes in containerd CRI plugin38Monitor
- CVE-2026-53488containerd CRI plugin: — image-config `LABEL` flows to restart-monitor `binary://` logger: host-root command execution from an image pull37Monitor
- CVE-2021-43816Improper Preservation of Permissions in containerd37Monitor
Published before and after this one in the same product
- ← EarlierCVE-2020-15157Oct 16, 2020 · containerd can be coerced into leaking credentials during image pull25Monitor
- Later →CVE-2021-21334Mar 10, 2021 · environment variable leak26Monitor
- Later →CVE-2021-32760Jul 19, 2021 · Archive package allows chmod of file outside of unpack target directory25Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| alpine:containerd | 1.3.9-r0 · Alpine:v3.11 | Package registry (OSV) |
| alpine:docker | 19.03.14-r0 · Alpine:v3.12 | Package registry (OSV) |
| alpine:k3s | 1.19.4.2-r0 · Alpine:v3.13 | Package registry (OSV) |
| debian:containerd | 1.4.3~ds1-1 · Debian:12 | Package registry (OSV) |
| debian:docker.io | 20.10.0~rc1+dfsg2-1 · Debian:12 | Package registry (OSV) |
| Go:github.com/containerd/containerd | 1.3.9 | Package registry (OSV) |
| Go:github.com/containerd/containerd | 1.4.3 | Package registry (OSV) |
| opensuse:containerd | 1.3.9-lp152.2.3.1 · openSUSE:Leap 15.2 | Package registry (OSV) |
| opensuse:docker | 19.03.15_ce-lp152.2.3.1 · openSUSE:Leap 15.2 | Package registry (OSV) |
| opensuse:docker-runc | 1.0.0rc10+gitr3981_dc9208a3303f-lp152.2.3.1 · openSUSE:Leap 15.2 | Package registry (OSV) |
| opensuse:fish | 2.7.1-lp152.5.3.1 · openSUSE:Leap 15.2 | Package registry (OSV) |
| opensuse:golang-github-docker-libnetwork | 0.7.0.1+gitr2908_55e924b8a842-lp152.2.3.1 · openSUSE:Leap 15.2 | Package registry (OSV) |
| suse:containerd | 1.3.9-16.32.1 · SUSE:Linux Enterprise Module for Containers 12 | Package registry (OSV) |
| suse:docker | 19.03.14_ce-98.57.1 · SUSE:Linux Enterprise Module for Containers 12 | Package registry (OSV) |
| suse:docker-runc | 1.0.0rc10+gitr3981_dc9208a3303f-1.49.1 · SUSE:Linux Enterprise Module for Containers 12 | Package registry (OSV) |
| suse:golang-github-docker-libnetwork | 0.7.0.1+gitr2908_55e924b8a842-34.1 · SUSE:Linux Enterprise Module for Containers 12 | Package registry (OSV) |
Exploit status
Proof of concept available
A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.
Evidence
- Proof-of-concept repository on GitHub ×1
Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.
| Source | Kind | Date |
|---|---|---|
| Proof-of-concept repository on GitHub | stars:18 | 2020-12-07 |
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
- Published
- First PoC+6 d
- TodayNov 16, 2026+2176 d
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-20-1035 · Dec 11, 2020(containerd Güvenlik Güncellemesi)
Not on record for this CVE: EPSS history · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- low · data can be read
- Integrity
- low · data or configuration can be modified
- Availability
- none
Impact can extend beyond the vulnerable component (scope changes).
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality impact
- Low
- Integrity impact
- Low
- Availability impact
- None
Weakness class (CWE)
CWE-669 · Incorrect Resource Transfer Between SpheresCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (5 more)Show less
- github.com/containerd/containerd/releases/tag/v1.4.3
- github.com/containerd/containerd/security/advisories/GHSA-36xw-fx78-c5r4
- lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/LNKXLOLZWO5FMAPX63ZL7JNKTNNT5NQD/
- security.gentoo.org/glsa/202105-33
- www.debian.org/security/2021/dsa-4865
Vendor advisories and official records. Exploit/PoC links are deliberately left out.