Exposure of Resource to Wrong Sphere Affecting ctop package, versions <0.7.7-r13


Severity

Recommended
0.0
medium
0
10

Snyk's Security Team recommends NVD's CVSS assessment. Learn more

Threat Intelligence

EPSS
0.12% (49th 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-WOLFILATEST-CTOP-6597045
  • published11 Apr 2024
  • disclosed10 Mar 2021

Introduced: 10 Mar 2021

CVE-2021-21334  (opens in a new tab)
CWE-668  (opens in a new tab)

How to fix?

Upgrade Wolfi ctop to version 0.7.7-r13 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream ctop package and not the ctop package as distributed by Wolfi. See How to fix? for Wolfi relevant fixed versions and status.

In containerd (an industry-standard container runtime) before versions 1.3.10 and 1.4.4, containers launched through containerd's CRI implementation (through Kubernetes, crictl, or any other pod/container client that uses the containerd CRI service) that share the same image may receive incorrect environment variables, including values that are defined for other containers. If the affected containers have different security contexts, this may allow sensitive information to be unintentionally shared. If you are not using containerd's CRI implementation (through one of the mechanisms described above), you are not vulnerable to this issue. If you are not launching multiple containers or Kubernetes pods from the same image which have different environment variables, you are not vulnerable to this issue. If you are not launching multiple containers or Kubernetes pods from the same image in rapid succession, you have reduced likelihood of being vulnerable to this issue This vulnerability has been fixed in containerd 1.3.10 and containerd 1.4.4. Users should update to these versions.

CVSS Scores

version 3.1