Skip to content

containerd CRI plugin: Insecure handling of image volumes

High severity GitHub Reviewed Published Mar 2, 2022 in containerd/containerd • Updated Jan 31, 2024

Package

gomod github.com/containerd/containerd (Go)

Affected versions

< 1.4.13
>= 1.5.0, < 1.5.10
>= 1.6.0, < 1.6.1

Patched versions

1.4.13
1.5.10
1.6.1

Description

Impact

A bug was found in containerd where containers launched through containerd’s CRI implementation 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.

Patches

This bug has been fixed in containerd 1.6.1, 1.5.10 and 1.4.13. Users should update to these versions to resolve the issue.

Workarounds

Ensure that only trusted images are used.

Credits

The containerd project would like to thank Felix Wilhelm of Google Project Zero for responsibly disclosing this issue in accordance with the containerd security policy.

For more information

If you have any questions or comments about this advisory:

References

@dmcgowan dmcgowan published to containerd/containerd Mar 2, 2022
Published to the GitHub Advisory Database Mar 2, 2022
Reviewed Mar 2, 2022
Published by the National Vulnerability Database Mar 3, 2022
Last updated Jan 31, 2024

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

EPSS score

0.945%
(84th percentile)

Weaknesses

CVE ID

CVE-2022-23648

GHSA ID

GHSA-crp2-qrr5-8pq7

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.