Information Exposure Affecting containerd-stress-debuginfo package, versions <0:1.6.8-2.amzn2023.0.3


Severity

Recommended
medium

Based on Amazon Linux security rating.

Threat Intelligence

EPSS
1.01% (84th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-AMZN2023-CONTAINERDSTRESSDEBUGINFO-3347840
  • published7 Mar 2023
  • disclosed3 Mar 2022

Introduced: 3 Mar 2022

CVE-2022-23648  (opens in a new tab)
CWE-200  (opens in a new tab)
CWE-497  (opens in a new tab)

How to fix?

Upgrade Amazon-Linux:2023 containerd-stress-debuginfo to version 0:1.6.8-2.amzn2023.0.3 or higher.
This issue was patched in ALAS2023-2023-079.

NVD Description

Note: Versions mentioned in the description apply only to the upstream containerd-stress-debuginfo package and not the containerd-stress-debuginfo package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2023 relevant fixed versions and status.

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.

CVSS Scores

version 3.1