Advisory

GHSA-6g2q-w5j3-fwh4

Also known as: CVE-2021-21334

Summary

containerd environment variable leak

Details

Impact

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

Patches

This vulnerability has been fixed in containerd 1.3.10 and containerd 1.4.4. Users should update to these versions as soon as they are released.

Workarounds

There are no known workarounds.

For more information

If you have any questions or comments about this advisory:

Severity

Medium Basis: The source's own band: MODERATE

Dates

Published
2024-01-31 23:22 UTC
Modified
2026-09-10 03:50 UTC

Affected packages and fixes

github.com/containerd/containerd

Go · All systems

Affected

  • introduced 1.4.0, fixed 1.4.4 (semver)

Fixed versions

1.4.4

Fix

github.com/containerd/containerd

Go · All systems

Affected

  • introduced 0, fixed 1.3.10 (semver)

Fixed versions

1.3.10

Fix

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences