Memory Leak The advisory has been revoked - it doesn't affect any version of package flux-helm-controller-0.37  (opens in a new tab)


Threat Intelligence

EPSS
1.11% (65th 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-CHAINGUARDLATEST-FLUXHELMCONTROLLER037-6241761
  • published11 Feb 2024
  • disclosed7 Dec 2022

Introduced: 7 Dec 2022

CVE-2022-23471  (opens in a new tab)
CWE-401  (opens in a new tab)

Amendment

The Chainguard security team deemed this advisory irrelevant for Chainguard:latest.

NVD Description

Note: Versions mentioned in the description apply only to the upstream flux-helm-controller-0.37 package and not the flux-helm-controller-0.37 package as distributed by Chainguard.

containerd is an open source container runtime. A bug was found in containerd's CRI implementation where a user can exhaust memory on the host. In the CRI stream server, a goroutine is launched to handle terminal resize events if a TTY is requested. If the user's process fails to launch due to, for example, a faulty command, the goroutine will be stuck waiting to send without a receiver, resulting in a memory leak. Kubernetes and crictl can both be configured to use containerd's CRI implementation and the stream server is used for handling container IO. This bug has been fixed in containerd 1.6.12 and 1.5.16. Users should update to these versions to resolve the issue. Users unable to upgrade should ensure that only trusted images and commands are used and that only trusted users have permissions to execute commands in running containers.