BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2022
CVE-2022-23648High confidence

Insecure handling of image volumes in containerd CRI plugin

containerd · containerd

7.5HighCVSS 3.1
Recommended action
Within 7 days

High technical severity with public exploit material referenced by a structured source; prioritise exposed affected systems while verifying vendor guidance.

Patch available
Optional official sources

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

Select the national-authority views to include. The exact source language is shown on each matched advisory. Your choice is remembered on this device and encoded in the shareable URL.

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-2022-1411

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 actionWithin 7 days

High technical severity with public exploit material referenced by a structured source; prioritise exposed affected systems while verifying vendor guidance.

Patch available
01

What, why and how

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.

What

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.

Why

The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may obtain information outside the intended access boundary.

What

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.

Why

The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may obtain information outside the intended access boundary.

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.
Reference recorded

A structured CVE source labels at least one public reference as exploit material. BlackTree has not independently validated that it is safe, reliable or weaponised.

Likely attack path
a network path → Exposure of Sensitive Information to an Unauthorized Actor → obtain information outside the intended access boundary
Attack surface
Network
Privileges required
None: unauthenticated exploitation is possible
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-200 ↗

CWE-200: Exposure of Sensitive Information to an Unauthorized Actor. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.

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:L/PR:N/UI:N/S:U/C:H/I:N/A:N

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.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRNonePrivileges required: The attacker does not need an account or existing 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.INoneIntegrity impact: No direct loss is represented by this metric.ANoneAvailability impact: No direct loss is represented by this metric.
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-200Public exploit reference
A

Official authority intelligence

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

BSI · German · WID-SEC-2022-1375JFrog Artifactory: Mehrere Schwachstellen

Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in JFrog Artifactory ausnutzen, um seine Privilegien zu erweitern, beliebigen Code auszuführen, Sicherheitsmaßnahmen zu umgehen, vertrauliche Informationen offenzulegen und einen Denial-of-Service-Zustand auszulösen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20220309Security Bulletin 09 Mar 2022

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 09 Mar 2022, published on 9 March 2022. Open the linked bulletin for the product, severity and reference information published in that issue.

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0199Multiples vulnérabilités dans les produits VMware

cord?id=CVE-2022-2068 Référence CVE CVE-2022-2097 https://www.cve.org/CVERecord?id=CVE-2022-2097 Référence CVE CVE-2022-21619 https://www.cve.org/CVERecord?id=CVE-2022-21619 Référence CVE CVE-2022-21624 https://www.cve.org/CVERecord?id=CVE-2022-21624 Référence CVE CVE-2022-21626 https://www.cve.org/CVERecord?id=CVE-2022-21626 Référence CVE CVE-2022-21628 https://www.cve.org/CVERecord?id=CVE-2022-21628 Référence CVE CVE-2022-21698 https://www.cve.org/CVERecord?id=CVE-2022-21698 Référence CVE CVE-2022-22576 https://www.cve.org/CVERecord?id=CVE-2022-22576 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-23772 https://www.cve.org/CVERecord?id=CVE-2022-23772 Référence CVE CVE-2022-23773 https://www.cve.org/CVERecord?id=CVE-2022-23773 Référence CVE CVE-2022-23806 https://www.cve.org/CVERecord?id=CVE-2022-23806 Référence CVE CVE-2022-24450 https://www.cve.org/CVERecord?id=CVE-2022-24450 Référence CVE CVE-2022-24675 https://www.cve.org/CVERecord?id=CVE-2022-24675 Référence CVE CVE-2022-24769 https://www.cve.org/CVERecord?id=CVE-2022-24769 Référence CVE CVE-2022-24921 https://www.cve.org/CVERecord?id=CVE-2022-24921 Référence CVE CVE-2022-25857 https://www.cve.org/CVERecord?id=

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

d?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=CVE-2022-32149 Référence CVE CVE-2022-41721 https://www.cve.org/CVERecord?id=CVE-2022-41721 Référence CVE CVE-2022-41723 https://www.cve.org/CVERecord?id=CVE-2022-41723 Référence CVE CVE-2023-21830 https://www.cve.org/CVERecord?id=CVE-2023-21830 Référence CVE CVE-2023-25153 https://www.cve.org/CVERecord?id=

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

écurité IBM 7238824 du 03 juillet 2025 https://www.ibm.com/support/pages/node/7238824 Bulletin de sécurité IBM 7238826 du 03 juillet 2025 https://www.ibm.com/support/pages/node/7238826 Bulletin de sécurité IBM 7238830 du 03 juillet 2025 https://www.ibm.com/support/pages/node/7238830 Bulletin de sécurité IBM 7238831 du 03 juillet 2025 https://www.ibm.com/support/pages/node/7238831 Bulletin de sécurité IBM 7238833 du 03 juillet 2025 https://www.ibm.com/support/pages/node/7238833 Référence CVE CVE-2021-43816 https://www.cve.org/CVERecord?id=CVE-2021-43816 Référence CVE CVE-2022-21698 https://www.cve.org/CVERecord?id=CVE-2022-21698 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-32149 https://www.cve.org/CVERecord?id=CVE-2022-32149 Référence CVE CVE-2022-41721 https://www.cve.org/CVERecord?id=CVE-2022-41721 Référence CVE CVE-2023-39325 https://www.cve.org/CVERecord?id=CVE-2023-39325 Référence CVE CVE-2024-10917 https://www.cve.org/CVERecord?id=CVE-2024-10917 Référence CVE CVE-2024-21131 https://www.cve.org/CVERecord?id=CVE-2024-21131 Référence CVE CVE-2024-21144 https://www.cve.org/CVERecord?id=CVE-2024-21144 Référence CVE CVE-2024-21145 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2021-47449 Référence CVE CVE-2021-47461 https://www.cve.org/CVERecord?id=CVE-2021-47461 Référence CVE CVE-2021-47468 https://www.cve.org/CVERecord?id=CVE-2021-47468 Référence CVE CVE-2021-47491 https://www.cve.org/CVERecord?id=CVE-2021-47491 Référence CVE CVE-2021-47548 https://www.cve.org/CVERecord?id=CVE-2021-47548 Référence CVE CVE-2021-47579 https://www.cve.org/CVERecord?id=CVE-2021-47579 Référence CVE CVE-2021-47624 https://www.cve.org/CVERecord?id=CVE-2021-47624 Référence CVE CVE-2022-23181 https://www.cve.org/CVERecord?id=CVE-2022-23181 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-24999 https://www.cve.org/CVERecord?id=CVE-2022-24999 Référence CVE CVE-2022-25762 https://www.cve.org/CVERecord?id=CVE-2022-25762 Référence CVE CVE-2022-29885 https://www.cve.org/CVERecord?id=CVE-2022-29885 Référence CVE CVE-2022-31030 https://www.cve.org/CVERecord?id=CVE-2022-31030 Référence CVE CVE-2022-34305 https://www.cve.org/CVERecord?id=CVE-2022-34305 Référence CVE CVE-2022-40897 https://www.cve.org/CVERecord?id=CVE-2022-40897 Référence CVE CVE-2022-42252 https://www.cve.org/CVERecord?id=CVE-2022-42252 Référence CVE CVE-2022-48632 https://www.cve.org/CVERecord?id=

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

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=CVE-2023-2253 Référence CVE CVE-2023-25153 https://www.cve.org/CVERecord?id=CVE-2023-25153 Référence CVE CVE-2023-25173 https://www.cve.org/CVERecord?id=CVE-2023-25173 Référence CVE CVE-2023-25809 https://www.cve.org/CVERecord?id=CVE-2023-25809 Référence CVE CVE-2023-26136 https://www.cve.org/CVERecord?id=CV

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

ecord?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=CVE-2022-38749 Référence CVE CVE-2022-38750 https://www.cve.org/CVERecord?id=CVE-2022-38750 Référence CVE CVE-2022-38751 https://www.cve.org/CVERecord?id=CVE-2022-38751 Référence CVE CVE-2022-38752 https://www.cve.org/CVERecord?id=CVE-2022-38752 Référence CVE CVE-2022-41854 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2022-006387Linux Foundation の containerd 他複数ベンダの製品における脆弱性

Linux Foundation の 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.
Patch available
Affected
containerd: < 1.4.13, >= 1.5.0, < 1.5.10, >= 1.6.0, < 1.6.1
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
Review the linked authoritative reference and apply the recorded fixed release appropriate to the affected product branch.
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 3 Mar 2022 · Last source change 3 Aug 2024, 03:51 UTC · CWE-200 · Exposure of Sensitive Information to an Unauthorized Actor

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-2022-1411
Product sourceCNA
Remediation sourceCVE/CNA references
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
CVE published
Fixed release or patch reference recorded
ENISA EUVD · EUVD-2022-1411↗Patch or update reference↗Patch or update reference↗Patch or update reference↗Patch or update reference↗CVE authority or vendor reference↗Public exploit reference↗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-2022-23648 · cve.blacktree.nl