Skip to content
Noroxi
NVD / CVE Program· CNA GitHub_M

CVE-2021-41103: Insufficiently restricted permissions on plugin directories

Noroxi assessment

Priority: Monitor (action score 31/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.51% (FIRST EPSS).
  • 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 (Debian:11) 1.4.5~ds1-2+deb11u1; containerd (Debian:12) 1.5.7~ds1-1; github.com/containerd/containerd (Go) 1.5.7, 1.4.11.
  • Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to containerd (Debian:11) 1.4.5~ds1-2+deb11u1; containerd (Debian:12) 1.5.7~ds1-1; github.com/containerd/containerd (Go) 1.5.7, 1.4.11 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 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.

HighCVSS 7.8 · v3.1—No exploit Fix available
Published
Oct 4, 2021
Updated
Jun 17, 2026
EPSS
0.5% · 43th percentile

Report tools

JSON

Action score

31

Monitor

Low priority for now.

CVSS
31 / 40 · 7.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.5%

CNA vs NVD score

NVD
7.8
CNA · GitHub_M
5.9
1.9 point gap

CVSS:3.0/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L

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
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2021-41103

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi 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 help

Affected 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.

VendorProduct
linuxfoundationcontainerd
fedoraprojectfedora
debiandebian linux

Using containerd? Add it to your stack and be the first to know about CVEs like this one. (Docker)

Watch new CVEs for containerd

When you'll hear from us

  • when a new CVE affecting this product is published
  • when a record in your stack enters KEV or gets exploit code

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • debian debian linux11.0
  • fedoraproject fedora34
  • fedoraproject fedora35
  • linuxfoundation containerdbefore 1.4.11
  • linuxfoundation containerd1.5.0 and later · before 1.5.7

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.4.11, >= 1.5.0, < 1.5.7affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:11containerdbefore 1.4.5~ds1-2+deb11u11.4.5~ds1-2+deb11u1
Debian:12containerdbefore 1.5.7~ds1-11.5.7~ds1-1
Gogithub.com/containerd/containerdfrom 1.5.0 · before 1.5.71.5.7
Gogithub.com/containerd/containerdbefore 1.4.111.4.11
openSUSE:Leap 15.2containerdbefore 1.4.11-lp152.2.12.11.4.11-lp152.2.12.1
openSUSE:Leap 15.2dockerbefore 20.10.9_ce-lp152.2.18.120.10.9_ce-lp152.2.18.1
openSUSE:Leap 15.2runcbefore 1.0.2-lp152.2.9.11.0.2-lp152.2.9.1
openSUSE:Leap 15.3containerdbefore 1.4.11-56.11.4.11-56.1
openSUSE:Leap 15.3containerdbefore 1.4.12-60.11.4.12-60.1
openSUSE:Leap 15.3dockerbefore 20.10.12_ce-159.120.10.12_ce-159.1
openSUSE:Leap 15.3dockerbefore 20.10.9_ce-156.120.10.9_ce-156.1
openSUSE:Leap 15.3docker-kubicbefore 20.10.9_ce-156.120.10.9_ce-156.1
openSUSE:Leap 15.3docker-kubicbefore 20.10.12_ce-159.120.10.12_ce-159.1
openSUSE:Leap 15.3runcbefore 1.0.2-23.11.0.2-23.1
openSUSE:Tumbleweedcontainerdbefore 1.4.11-1.11.4.11-1.1
SUSE:Linux Enterprise Module for Containers 12containerdbefore 1.4.11-16.45.11.4.11-16.45.1
SUSE:Linux Enterprise Module for Containers 12containerdbefore 1.4.12-16.49.11.4.12-16.49.1
SUSE:Linux Enterprise Module for Containers 12dockerbefore 20.10.12_ce-98.75.120.10.12_ce-98.75.1
SUSE:Linux Enterprise Module for Containers 12dockerbefore 20.10.9_ce-98.72.120.10.9_ce-98.72.1
SUSE:Linux Enterprise Module for Containers 12runcbefore 1.0.2-16.14.11.0.2-16.14.1
SUSE:Linux Enterprise Module for Containers 15 SP2containerdbefore 1.4.11-56.11.4.11-56.1
SUSE:Linux Enterprise Module for Containers 15 SP2dockerbefore 20.10.9_ce-156.120.10.9_ce-156.1
SUSE:Linux Enterprise Module for Containers 15 SP2runcbefore 1.0.2-23.11.0.2-23.1
SUSE:Linux Enterprise Module for Containers 15 SP3containerdbefore 1.4.12-60.11.4.12-60.1

+1

Other highest-scoring records for the same primary product.

  • CVE-2022-23648Insecure handling of image volumes in containerd CRI plugin
    38Monitor
  • CVE-2026-53488containerd CRI plugin: — image-config `LABEL` flows to restart-monitor `binary://` logger: host-root command execution from an image pull
    37Monitor
  • CVE-2021-43816Improper Preservation of Permissions in containerd
    37Monitor

Published before and after this one in the same product

  • ← EarlierCVE-2021-21334Mar 10, 2021 · environment variable leak
    26Monitor
  • ← EarlierCVE-2021-32760Jul 19, 2021 · Archive package allows chmod of file outside of unpack target directory
    25Monitor
  • Later →CVE-2022-31030Jun 9, 2022 · containerd CRI plugin: Host memory exhaustion through ExecSync
    22Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
debian:containerd1.5.7~ds1-1 · Debian:12Package registry (OSV)
Go:github.com/containerd/containerd1.4.11Package registry (OSV)
Go:github.com/containerd/containerd1.5.7Package registry (OSV)
opensuse:containerd1.4.11-lp152.2.12.1 · openSUSE:Leap 15.2Package registry (OSV)
opensuse:docker20.10.9_ce-lp152.2.18.1 · openSUSE:Leap 15.2Package registry (OSV)
opensuse:docker-kubic20.10.9_ce-156.1 · openSUSE:Leap 15.3Package registry (OSV)
opensuse:runc1.0.2-lp152.2.9.1 · openSUSE:Leap 15.2Package registry (OSV)
suse:containerd1.4.11-16.45.1 · SUSE:Linux Enterprise Module for Containers 12Package registry (OSV)
suse:docker20.10.9_ce-98.72.1 · SUSE:Linux Enterprise Module for Containers 12Package registry (OSV)
suse:runc1.0.2-16.14.1 · SUSE:Linux Enterprise Module for Containers 12Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

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.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

All national notices →

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
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

nvd-primary

Root cause

A user-supplied file name is joined with the allowed directory, but the result is never checked to confirm it is still inside that directory.

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

ts
const file = path.join(ROOT, req.query.name);res.sendFile(file);

Fixed

ts
const file = path.resolve(ROOT, req.query.name);if (!file.startsWith(ROOT + path.sep)) {  return res.sendStatus(400);}res.sendFile(file);

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records