dbcve.org
Debian LinuxOperating system · Debian

CVE-2022-23648

HIGH · 7.5 CVSS v3.1 Published 2022-03-03
Fix available
A fix is available. Upgrade to 1.4.13 / 1.5.10 or later.
See remediation →
84/100
Remediation priority · High
Public exploit Remotely reachable No privileges Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
containerd is a container runtime available as a daemon for Linux and Windows. A bug was found in containerd prior to versions 1.6.1, 1.5.10, and 1.14.12 where containers launched through containerd’s CRI implementation on Linux with a specially-crafted image configuration could gain access to read-only copies of arbitrary files and directories on the host. This may bypass any policy-based enforcement on container setup (including a Kubernetes Pod Security Policy) and expose potentially sensitive information. Kubernetes and crictl can both be configured to use containerd’s CRI implementation. This bug has been fixed in containerd 1.6.1, 1.5.10, and 1.4.12. Users should update to these versions to resolve the issue.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis
How this class of weakness works · CWE-200

The application discloses data — error detail, internal paths, tokens, or other users' records — to someone who shouldn't see it. On its own it can look minor, but it hands attackers the map they need for a larger attack. Remediation is about minimising what's returned and enforcing authorization on every piece of data.

General guidance for the information exposure class — the official description and references above are authoritative for this specific CVE. Want a bespoke review and a reviewed fix? Ask our team →

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Debian LinuxOperating system
Affected:= 11.0
FedoraOperating system
Affected:= 34= 35= 36
ContainerdApplication
Affected:< 1.4.13>= 1.5.0, < 1.5.10>= 1.6.0, < 1.6.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

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

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1.4.13 / 1.5.10 / 1.6.1 or later
Fixed in 1.4.131.5.101.6.1
Vendor patch github.com →
Recommended fix High confidence

containerd 1.6.1 (or 1.5.10 or 1.4.12 depending on your release line)

  1. Identify the currently installed containerd version using 'containerd --version' or 'ctr version'
  2. Determine which containerd release line is in use (1.4.x, 1.5.x, or 1.6.x) based on the current version
  3. For containerd 1.6.x installations: upgrade to version 1.6.1 or later
  4. For containerd 1.5.x installations: upgrade to version 1.5.10 or later
  5. For containerd 1.4.x installations: upgrade to version 1.4.12 or later
  6. Restart the containerd daemon after upgrade using 'systemctl restart containerd' or the appropriate service manager command
  7. Verify the new version is running with 'containerd --version'
  8. If using Kubernetes, verify pods can still be scheduled and running correctly
Caveat Containerd minor version upgrades are generally backward compatible; however, review release notes for any changes to CRI API or configuration syntax before upgrading production systems

Generated from the published advisory — verify against the referenced sources before acting.

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $1,250. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-23648 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-23648 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data