BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2021
CVE-2021-32760High confidence

Archive package allows chmod of file outside of unpack target directory

containerd · containerd

Official source article: GitHub GHSA-C72P-9XMJ-RX3W ↗. Check the applicable product and release in the original source.

5.0MediumCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. Verified remediation exists for at least one product or source, but 2 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityMediumOperational priority:Medium, unchanged from published severity.unchanged

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • EPSS is 1.59% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict the affected network interface to trusted sources where business-safe.
  • Monitor vendor guidance and exploitation sources for a material change.

Verification

  1. Confirm that the asset runs containerd containerd and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: As exposure requiresRemediation target: Within 365 days

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Cross-source reconciliation

Remediation availability differs by product scope

Verified remediation exists for at least one product or source, but 2 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Distribution package intelligence

Release-specific package status

Alpine, Debian findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.

7 package states
Repository candidate not checked

A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.

Distribution releaseSource packageVendor stateFixed versionEvidence
Alpine v3.23v3.23 · communitycontainerdVendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.1.5.4-r0Alpine Security Database ↗Source updated 11 Sep 2026
Alpine v3.22v3.22 · communitycontainerdVendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.1.5.4-r0Alpine Security Database ↗Source updated 11 Sep 2026
Alpine v3.21v3.21 · communitycontainerdVendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.1.5.4-r0Alpine Security Database ↗Source updated 19 Aug 2026
Debian trixietrixie · sourcecontainerdVendor fix publishedDebian records a fixed source-package version for this release.1.4.5~ds1-2Debian Security Tracker ↗Source updated 6 Oct 2026
Debian bookwormbookworm · sourcecontainerdVendor fix publishedDebian records a fixed source-package version for this release.1.4.5~ds1-2Debian Security Tracker ↗Source updated 6 Oct 2026
Debian forkyforky · sourcecontainerdVendor fix publishedDebian records a fixed source-package version for this release.1.4.5~ds1-2Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · sourcecontainerdVendor fix publishedDebian records a fixed source-package version for this release.1.4.5~ds1-2Debian Security Tracker ↗Source updated 6 Oct 2026
Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.

1 current
CVE-2021-32760 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitycontainerd: pulling and extracting crafted container image may result in Unix file permission changes
4 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • 3scale-operator-container as a component of Red Hat 3scale API Management Platform 2
  • rhods/odh-operator-base-rhel8 as a component of Red Hat OpenShift Data Science (RHODS)
  • osp-director-provisioner-container as a component of Red Hat OpenStack Platform 16.2
  • rhosp-rhel8/osp-director-downloader as a component of Red Hat OpenStack Platform 16.2
Summary
A flaw was found in containerd where pulling and extracting a specially-crafted container image can result in Unix file permission changes for existing files in the host’s filesystem. Changes to file permissions can deny access to the expected owner of the file, widen access to others, or set extended bits like setuid, setgid, and sticky. This bug does not directly allow files to be read, modified, or executed without an additional cooperating process.
Remediation
OSP 16.2 Release - OSP Director Operator Containers tech preview
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2021-1457

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
Not supplied in the stored EUVD record
Advisory evidence
No linked advisory details stored yet
Recommended actionPatch only the product branches with a verified fix

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. Verified remediation exists for at least one product or source, but 2 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
01

What, why and how

containerd is a container runtime. A bug was found in containerd versions prior to 1.4.8 and 1.5.4 where pulling and extracting a specially-crafted container image can result in Unix file permission changes for existing files in the host’s filesystem. Changes to file permissions can deny access to the expected owner of the file, widen access to others, or set extended bits like setuid, setgid, and sticky. This bug does not directly allow files to be read, modified, or executed without an additional cooperating process. This bug has been fixed in containerd 1.5.4 and 1.4.8. As a workaround, ensure that users only pull images from trusted sources. Linux security modules (LSMs) like SELinux and AppArmor can limit the files potentially affected by this bug through policies and profiles that prevent containerd from interacting with specific files.

What

containerd is a container runtime. A bug was found in containerd versions prior to 1.4.8 and 1.5.4 where pulling and extracting a specially-crafted container image can result in Unix file permission changes for existing files in the host’s filesystem. Changes to file permissions can deny access to the expected owner of the file, widen access to others, or set extended bits like setuid, setgid, and sticky. This bug does not directly allow files to be read, modified, or executed without an additional cooperating process. This bug has been fixed in containerd 1.5.4 and 1.4.8. As a workaround, ensure that users only pull images from trusted sources. Linux security modules (LSMs) like SELinux and AppArmor can limit the files potentially affected by this bug through policies and profiles that prevent containerd from interacting with specific files.

Why

The product exposes a resource to the wrong control sphere, providing unintended actors with inappropriate access to the resource.

How

An attacker operating through a network path may attempt exploitation without authentication after a user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

containerd is a container runtime. A bug was found in containerd versions prior to 1.4.8 and 1.5.4 where pulling and extracting a specially-crafted container image can result in Unix file permission changes for existing files in the host’s filesystem. Changes to file permissions can deny access to the expected owner of the file, widen access to others, or set extended bits like setuid, setgid, and sticky. This bug does not directly allow files to be read, modified, or executed without an additional cooperating process. This bug has been fixed in containerd 1.5.4 and 1.4.8. As a workaround, ensure that users only pull images from trusted sources. Linux security modules (LSMs) like SELinux and AppArmor can limit the files potentially affected by this bug through policies and profiles that prevent containerd from interacting with specific files.

Why

The product exposes a resource to the wrong control sphere, providing unintended actors with inappropriate access to the resource.

How

An attacker operating through a network path may attempt exploitation without authentication after a user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path
a network path → Exposure of Resource to Wrong Sphere → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Network
Privileges required
None: unauthenticated exploitation is possible
User interaction
Required interaction required
Attack complexity
High: exploitation depends on specific conditions
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-668 ↗

CWE-668: Exposure of Resource to Wrong Sphere. The product exposes a resource to the wrong control sphere, providing unintended actors with inappropriate access to the resource.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:L

Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.

AVNetworkAttack vector: The vulnerable component can be reached over a network.ACHighAttack complexity: Successful exploitation depends on specific conditions outside the attacker's direct control.PRNonePrivileges required: The attacker does not need an account or existing privileges.UIRequiredUser interaction: Another user must perform an action for exploitation to succeed.SUnchangedScope: The security impact remains within the vulnerable component's authority.CLowConfidentiality impact: A successful attack can cause a limited loss.ILowIntegrity impact: A successful attack can cause a limited loss.ALowAvailability impact: A successful attack can cause a limited loss.
Post-exploitation / living off the land
No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.
NetworkUnauthenticatedCWE-668
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

BSI · German · WID-SEC-2022-1002Amazon Linux 2: Mehrere Schwachstellen

Ein lokaler Angreifer kann mehrere Schwachstellen in Amazon Linux 2 ausnutzen, um Informationen offenzulegen, Dateien zu manipulieren oder falsche Informationen darzustellen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20210721Security Bulletin 21 Jul 2021

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 21 Jul 2021, published on 21 July 2021. Open the linked bulletin for the product, severity and reference information published in that issue.

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-0590Multiples vulnérabilités dans les produits IBM

9178 Bulletin de sécurité IBM 7239247 du 09 juillet 2025 https://www.ibm.com/support/pages/node/7239247 Bulletin de sécurité IBM 7239362 du 09 juillet 2025 https://www.ibm.com/support/pages/node/7239362 Bulletin de sécurité IBM 7239475 du 11 juillet 2025 https://www.ibm.com/support/pages/node/7239475 Bulletin de sécurité IBM 7239476 du 11 juillet 2025 https://www.ibm.com/support/pages/node/7239476 Référence CVE CVE-2016-1000027 https://www.cve.org/CVERecord?id=CVE-2016-1000027 Référence CVE CVE-2019-19921 https://www.cve.org/CVERecord?id=CVE-2019-19921 Référence CVE CVE-2020-13956 https://www.cve.org/CVERecord?id=CVE-2020-13956 Référence CVE CVE-2021-32760 https://www.cve.org/CVERecord?id=CVE-2021-32760 Référence CVE CVE-2021-35515 https://www.cve.org/CVERecord?id=CVE-2021-35515 Référence CVE CVE-2021-35516 https://www.cve.org/CVERecord?id=CVE-2021-35516 Référence CVE CVE-2021-35517 https://www.cve.org/CVERecord?id=CVE-2021-35517 Référence CVE CVE-2021-36090 https://www.cve.org/CVERecord?id=CVE-2021-36090 Référence CVE CVE-2021-41103 https://www.cve.org/CVERecord?id=CVE-2021-41103 Référence CVE CVE-2021-43784 https://www.cve.org/CVERecord?id=CVE-2021-43784 Référence CVE CVE-2021-43816 https://www.cve.org/CVERecord?id=CVE-2021-43816 Référence CVE CVE-2022-23471 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2024-AVI-0350Multiples vulnérabilités dans les produits IBM

èges et un déni de service à distance. Solution Se référer au bulletin de sécurité de l'éditeur pour l'obtention des correctifs (cf. section Documentation). Documentation Bulletin de sécurité IBM 7148847 du 19 avril 2024 https://www.ibm.com/support/pages/node/7148847 Bulletin de sécurité IBM 7149055 du 22 avril 2024 https://www.ibm.com/support/pages/node/7149055 Bulletin de sécurité IBM 7149195 du 23 avril 2024 https://www.ibm.com/support/pages/node/7149195 Bulletin de sécurité IBM 7149294 du 23 avril 2024 https://www.ibm.com/support/pages/node/7149294 Référence CVE CVE-2017-11468 https://www.cve.org/CVERecord?id=CVE-2017-11468 Référence CVE CVE-2021-32760 https://www.cve.org/CVERecord?id=CVE-2021-32760 Référence CVE CVE-2021-41103 https://www.cve.org/CVERecord?id=CVE-2021-41103 Référence CVE CVE-2021-43784 https://www.cve.org/CVERecord?id=CVE-2021-43784 Référence CVE CVE-2021-43816 https://www.cve.org/CVERecord?id=CVE-2021-43816 Référence CVE CVE-2022-23471 https://www.cve.org/CVERecord?id=CVE-2022-23471 Référence CVE CVE-2022-23648 https://www.cve.org/CVERecord?id=CVE-2022-23648 Référence CVE CVE-2022-29162 https://www.cve.org/CVERecord?id=CVE-2022-29162 Référence CVE CVE-2022-31030 https://www.cve.org/CVERecord?id=CVE-2022-31030 Référence CVE CVE-2022-42969 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2024-AVI-0199Multiples vulnérabilités dans IBM

curité IBM 7129989 du 06 mars 2024 https://www.ibm.com/support/pages/node/7129989 Bulletin de sécurité IBM 7130806 du 07 mars 2024 https://www.ibm.com/support/pages/node/7130806 Référence CVE CVE-2017-16137 https://www.cve.org/CVERecord?id=CVE-2017-16137 Référence CVE CVE-2018-1099 https://www.cve.org/CVERecord?id=CVE-2018-1099 Référence CVE CVE-2018-16886 https://www.cve.org/CVERecord?id=CVE-2018-16886 Référence CVE CVE-2018-8088 https://www.cve.org/CVERecord?id=CVE-2018-8088 Référence CVE CVE-2020-15106 https://www.cve.org/CVERecord?id=CVE-2020-15106 Référence CVE CVE-2021-21334 https://www.cve.org/CVERecord?id=CVE-2021-21334 Référence CVE CVE-2021-32760 https://www.cve.org/CVERecord?id=CVE-2021-32760 Référence CVE CVE-2021-41103 https://www.cve.org/CVERecord?id=CVE-2021-41103 Référence CVE CVE-2021-43816 https://www.cve.org/CVERecord?id=CVE-2021-43816 Référence CVE CVE-2022-1471 https://www.cve.org/CVERecord?id=CVE-2022-1471 Référence CVE CVE-2022-23471 https://www.cve.org/CVERecord?id=CVE-2022-23471 Référence CVE CVE-2022-23648 https://www.cve.org/CVERecord?id=CVE-2022-23648 Référence CVE CVE-2022-25857 https://www.cve.org/CVERecord?id=CVE-2022-25857 Référence CVE CVE-2022-25883 https://www.cve.org/CVERecord?id=CVE-2022-25883 Référence CVE CVE-2022-31030 https://www.cve.org/CVERecord?id=CV

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2021-009865containerd における誤った領域へのリソースの漏えいに関する脆弱性

containerd には、誤った領域へのリソースの漏えいに関する脆弱性が存在します。

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Fix availability varies by product
Affected
Fixed
Action
Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
Workaround
No verified workaround is recorded. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.
04

Evidence and provenance

Published 19 Jul 2021 · Last source change 19 Nov 2024, 14:27 UTC · CWE-668 · Exposure of Resource to Wrong Sphere

CVE recordCVE.org · 5.1
CVSS sourceCNA
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2021-1457
Product sourceVendor CSAF · Red Hat Product Security
Remediation sourceVendor CSAF · Red Hat Product Security
CWE sourceCNA
NVD statusNVD modified after enrichment

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates ↗
  1. Affected versionsThe structured affected or fixed version information changed.
    Before
    <= 1.4.7; >= 1.5.0, <= 1.5.3 · Fixed: No fixed version is explicitly recorded in the structured CVE data.
    After
    <= 1.4.7; >= 1.5.0, <= 1.5.3 · Fixed: OSP 16.2 Release - OSP Director Operator Containers tech preview
    Red Hat Product Security ↗
  2. Remediation statusRemediation status changed from Awaiting fix to Patch available.
    Before
    Awaiting fix
    After
    Patch available
    Red Hat Product Security ↗
Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Fixed release recorded from official guidance
ENISA EUVD · EUVD-2021-1457↗Red Hat Product Security security advisory↗CVE authority or vendor reference · GitHub GHSA-C72P-9XMJ-RX3W↗Official CVE record (CNA and ADP data)↗NVD record↗
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2021-32760 · cve.blacktree.nl