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

Insufficiently restricted permissions on plugin directories

containerd · containerd

Official source article: GitHub GHSA-C2H3-6MXW-7MVQ ↗. Check the applicable product and release in the original source.

7.8HighCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 1 structured product or package state 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 severityHighOperational priority:Medium, lowered one band.downgradedsince 4 Aug 2024

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • Exploitation requires an existing local or physical foothold with privileges.
  • EPSS is 0.52% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict local access and enforce least privilege on affected hosts.
  • 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 1 structured product or package state 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.7-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.7-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.7-r0Alpine Security Database ↗Source updated 19 Aug 2026
Debian trixietrixie · sourcecontainerdVendor fix publishedDebian records a fixed source-package version for this release.1.5.7~ds1-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian bookwormbookworm · sourcecontainerdVendor fix publishedDebian records a fixed source-package version for this release.1.5.7~ds1-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian forkyforky · sourcecontainerdVendor fix publishedDebian records a fixed source-package version for this release.1.5.7~ds1-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · sourcecontainerdVendor fix publishedDebian records a fixed source-package version for this release.1.5.7~ds1-1Debian 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
SSA-222547 · CSAF 2.0 · revision 1 · finalSiemens ProductCERTSSA-222547: Third-Party Component Vulnerabilities in SCALANCE LPE9403 before V2.0
1 known affected

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

  • SCALANCE LPE9403
Summary
A vulnerability was found in containerd where container root directories and some plugins had insufficiently restricted permissions, allowing otherwise unprivileged Linux users to traverse directory contents and execute programs. When containers included executable programs with extended permission bits (such as setuid), unprivileged Linux users could discover and execute those programs. When the UID of an unprivileged Linux user on the host collided with the file owner or group inside a container, the unprivileged Linux user on the host could discover, read, and modify those files.
Remediation
Update to V2.0 or later version
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-2187

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

High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 1 structured product or package state 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 an open source container runtime with an emphasis on simplicity, robustness and portability. A bug was found in containerd where container root directories and some plugins had insufficiently restricted permissions, allowing otherwise unprivileged Linux users to traverse directory contents and execute programs. When containers included executable programs with extended permission bits (such as setuid), unprivileged Linux users could discover and execute those programs. When the UID of an unprivileged Linux user on the host collided with the file owner or group inside a container, the unprivileged Linux user on the host could discover, read, and modify those files. This vulnerability has been fixed in containerd 1.4.11 and containerd 1.5.7. Users should update to these version when they are released and may restart containers or update directory permissions to mitigate the vulnerability. Users unable to update should limit access to the host to trusted users. Update directory permission on container bundles directories.

What

containerd is an open source container runtime with an emphasis on simplicity, robustness and portability. A bug was found in containerd where container root directories and some plugins had insufficiently restricted permissions, allowing otherwise unprivileged Linux users to traverse directory contents and execute programs. When containers included executable programs with extended permission bits (such as setuid), unprivileged Linux users could discover and execute those programs. When the UID of an unprivileged Linux user on the host collided with the file owner or group inside a container, the unprivileged Linux user on the host could discover, read, and modify those files. This vulnerability has been fixed in containerd 1.4.11 and containerd 1.5.7. Users should update to these version when they are released and may restart containers or update directory permissions to mitigate the vulnerability. Users unable to update should limit access to the host to trusted users. Update directory permission on container bundles directories.

Why

Attacker-controlled path data is not constrained to the intended directory before the application accesses a file.

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

containerd is an open source container runtime with an emphasis on simplicity, robustness and portability. A bug was found in containerd where container root directories and some plugins had insufficiently restricted permissions, allowing otherwise unprivileged Linux users to traverse directory contents and execute programs. When containers included executable programs with extended permission bits (such as setuid), unprivileged Linux users could discover and execute those programs. When the UID of an unprivileged Linux user on the host collided with the file owner or group inside a container, the unprivileged Linux user on the host could discover, read, and modify those files. This vulnerability has been fixed in containerd 1.4.11 and containerd 1.5.7. Users should update to these version when they are released and may restart containers or update directory permissions to mitigate the vulnerability. Users unable to update should limit access to the host to trusted users. Update directory permission on container bundles directories.

Why

Attacker-controlled path data is not constrained to the intended directory before the application accesses a file.

How

An attacker operating through local access may attempt exploitation with low privileges. 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
local access → Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Local
Privileges required
Low: a basic authenticated account is required
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
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-22 ↗

CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal'). The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory.

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

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

AVLocalAttack vector: The attacker needs local access to the vulnerable system.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRLowPrivileges required: The attacker needs basic user-level privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CHighConfidentiality impact: A successful attack can cause a major loss.IHighIntegrity impact: A successful attack can cause a major loss.AHighAvailability impact: A successful attack can cause a major loss.
Post-exploitation / living off the land
The issue can support a local privilege or sandbox boundary transition; normal system utilities may then be available in the gained context.
CWE-22
A

Official authority intelligence

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

Cyber Security Agency of Singapore · English · CSA-SB-20211006Security Bulletin 06 Oct 2021

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 06 Oct 2021, published on 6 October 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

es/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=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-27664 https://www.cve.org/CVERecord?id=CVE-2022-27664 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-32149 https://www.cve.org/CVERecord?id=

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

urité 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=CVE-2022-42969 Référence CVE CVE-2023-2253 https://www.cve.org/CVERecord?id=C

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

9989 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=CVE-2022-31030 Référence CVE CVE-2022-38749 https://www.cve.org/CVERecord?id=CV

Official advisory ↗
CERT-FR · French · CERTFR-2022-AVI-547Multiples vulnérabilités dans les produits Siemens

ord?id=CVE-2021-37182 Référence CVE CVE-2021-37209 https://www.cve.org/CVERecord?id=CVE-2021-37209 Référence CVE CVE-2021-39275 https://www.cve.org/CVERecord?id=CVE-2021-39275 Référence CVE CVE-2021-39293 https://www.cve.org/CVERecord?id=CVE-2021-39293 Référence CVE CVE-2021-4034 https://www.cve.org/CVERecord?id=CVE-2021-4034 Référence CVE CVE-2021-40438 https://www.cve.org/CVERecord?id=CVE-2021-40438 Référence CVE CVE-2021-41089 https://www.cve.org/CVERecord?id=CVE-2021-41089 Référence CVE CVE-2021-41091 https://www.cve.org/CVERecord?id=CVE-2021-41091 Référence CVE CVE-2021-41092 https://www.cve.org/CVERecord?id=CVE-2021-41092 Référence CVE CVE-2021-41103 https://www.cve.org/CVERecord?id=CVE-2021-41103 Référence CVE CVE-2021-45960 https://www.cve.org/CVERecord?id=CVE-2021-45960 Référence CVE CVE-2021-46143 https://www.cve.org/CVERecord?id=CVE-2021-46143 Référence CVE CVE-2022-0778 https://www.cve.org/CVERecord?id=CVE-2022-0778 Référence CVE CVE-2022-0847 https://www.cve.org/CVERecord?id=CVE-2022-0847 Référence CVE CVE-2022-22822 https://www.cve.org/CVERecord?id=CVE-2022-22822 Référence CVE CVE-2022-22823 https://www.cve.org/CVERecord?id=CVE-2022-22823 Référence CVE CVE-2022-22824 https://www.cve.org/CVERecord?id=CVE-2022-22824 Référence CVE CVE-2022-22825 https://www.cve.org/CVERecord?id=CVE-

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2021-013252containerd におけるパストラバーサルの脆弱性

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
SCALANCE LPE9403
Fixed
An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release.
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. Limit untrusted access and use least privilege until authoritative guidance is available.
04

Evidence and provenance

Published 4 Oct 2021 · Last source change 4 Aug 2024, 02:59 UTC · CWE-22 · Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')

CVE recordCVE.org · 5.1
CVSS sourceNIST NVD
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-2187
Product sourceVendor CSAF · Siemens ProductCERT
Remediation sourceVendor CSAF · Siemens ProductCERT
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 ↗

No material field changes have been recorded since change tracking began. Routine source refreshes and cosmetic edits are intentionally excluded.

Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
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-41103 · cve.blacktree.nl