Security readout for executives and security teams
Plain-English summary
Containerd could mishandle extraction of a malicious container image, changing Unix permissions on host files outside the intended unpack directory. That could disrupt access, weaken protections, or set special permission bits. The advisory says it does not directly let an attacker read, modify, or execute files without another cooperating process.
Executive priority
Treat as a moderate infrastructure hygiene issue. Prioritize systems that pull third-party images or support multi-team image publishing, because permission changes on host files can create operational disruption or weaken security boundaries.
Technical view
In containerd before 1.4.8 and 1.5.4, archive unpack handling could apply chmod operations outside the target directory when pulling or extracting specially crafted images. Impact is limited confidentiality, integrity, and availability loss; CVSS is 5.0 with high complexity and user interaction required.
Likely exposure
Exposure is most likely on Linux hosts or clusters running containerd 1.4.7 or earlier, or 1.5.0 through 1.5.3, that pull images from untrusted or weakly controlled registries.
Exploitation context
Sources describe a specially crafted image trigger during pull and extraction. The bundle does not cite public exploitation, and KEV is false. Exploitation appears constrained because the bug changes permissions rather than directly reading, writing, or executing files.
Researcher notes
The key boundary issue is chmod application outside the intended unpack target. The advisory explicitly limits direct impact: no standalone file read, modification, or execution without another cooperating process. Evidence is sufficient for affected versions and fixed releases, but incomplete for real-world exploitation.
Mitigation direction
- Upgrade containerd to 1.4.8, 1.5.4, or a later vendor-supported release.
- Restrict image pulls to trusted registries and approved image sources.
- Use SELinux, AppArmor, or equivalent LSM profiles to limit containerd file interactions.
- Review Fedora, Gentoo, or platform vendor advisories for packaged fixes.
Validation and detection
- Inventory containerd versions across hosts, nodes, and container platforms.
- Identify environments pulling images from external, public, or user-controlled registries.
- Confirm upgrade status against containerd 1.4.8 or 1.5.4 fixed releases.
- Check whether SELinux or AppArmor policies constrain containerd host file access.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-668: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupContainer behavior lookup
The affected technology mentions containers, so container-specific ATT&CK technique review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2021-32760 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 5 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:L
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:L1.63.4Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
5MediumVector: CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:L
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/containerd/containerd/security/advisories/GHSA-c72p-9xmj-rx3wCVE reference
- https://github.com/containerd/containerd/releases/tag/v1.4.8CVE reference
- https://github.com/containerd/containerd/releases/tag/v1.5.4CVE reference
- FEDORA-2021-53ce601cb0CVE reference · vendor-advisory
- GLSA-202401-31CVE reference · vendor-advisory
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Exposure of Resource to Wrong Sphere
Exposure of Resource to Wrong Sphere represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.