Public mode

No access to your tenant or devices. Every item links to its source. What this means

Sources need attention Customize Public modeDiscuss ChangeIntel on Discord

environment variable leak

CVSS 3.1 6.3 MEDIUMEUVD CVSS 3.1 6.3 CVSS 3.1 · [email protected] · Secondary 6.3 MEDIUMCVSS 3.1 · [email protected] · Primary 6.3 MEDIUMCVSS 2.0 · [email protected] · Primary 4.3 MEDIUMCVSS_V3 Publisher rating MODERATEFixed by github.com/containerd/containerd 1.4.4Fixed by github.com/containerd/containerd 1.3.10KEV status unknown

cve-program · CVE-2021-21334

Published

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.

Read the publisher's advisory

euvd · EUVD-2024-0272

Published

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.

Read the publisher's advisory

nvd · CVE-2021-21334

Published

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.

Read the publisher's advisory

osv · GHSA-6g2q-w5j3-fwh4

Published

## 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: * [Open an issue](https://github.com/containerd/containerd/issues/new/choose) * Email us at [email protected] if you think you’ve found a security bug.

Read the publisher's advisory

Affected versions, risk and source history

cve-program · CVE-2021-21334

Published

containerd

Vendor product

Publisher's version information

Shown as published. These rules are not interpreted as NuGet package version ranges.

{
                    "product": "containerd",
                    "vendor": "containerd",
                    "versions": [
                        {
                            "status": "affected",
                            "version": "< 1.3.10"
                        },
                        {
                            "status": "affected",
                            "version": ">= 1.4.0, < 1.4.4"
                        }
                    ]
                }

Original source record · Cite this exact observation · Complete original publisher JSON

euvd · EUVD-2024-0272

Published

EUVD source date text has no stated timezone and is retained without inventing a UTC instant. Related bulletin membership is not an alias, common cause or applicability claim. A missing vector with a zero score is treated as unrated. Complete vendor/product and underlying source evidence remains in the original JSON.

Original publisher date fields

datePublished: Mar 10, 2021, 9:30:18 PM

dateUpdated: Aug 3, 2024, 6:09:15 PM

7 related source bulletins · separate from aliases

openSUSE-SU-2021:1954-1: Security update for containerd, docker, runc

CVE-2021-21284 · CVE-2021-21285 · CVE-2021-21334 · CVE-2021-30465

SUSE-SU-2021:1458-1: Security update for containerd, docker, runc

CVE-2018-16873 · CVE-2018-16874 · CVE-2018-16875 · CVE-2019-16884 · CVE-2019-19921 · CVE-2019-5736 · CVE-2021-21284 · CVE-2021-21285 · CVE-2021-21334

msrc_CVE-2021-21334: environment variable leak

CVE-2021-21334

WID-SEC-W-2022-1002: Amazon Linux 2: Mehrere Schwachstellen

CVE-2021-21334 · CVE-2021-32760 · CVE-2021-41190 · CVE-2020-15157

SUSE-SU-2021:1954-1: Security update for containerd, docker, runc

CVE-2021-21284 · CVE-2021-21285 · CVE-2021-21334 · CVE-2021-30465

openSUSE-SU-2024:10693-1: containerd-1.4.8-2.2 on GA media

CVE-2016-9962 · CVE-2018-16873 · CVE-2018-16874 · CVE-2018-16875 · CVE-2019-5736 · CVE-2020-15157 · CVE-2020-15257 · CVE-2021-21334 · CVE-2021-32760

openSUSE-SU-2021:0878-1: Security update for containerd, docker, runc

CVE-2021-21284 · CVE-2021-21285 · CVE-2021-21334 · CVE-2021-30465

No normalized affected-package data is projected for this source revision. The original publisher record may contain additional product and version evidence; this does not establish that a package is unaffected.

Original source record · Cite this exact observation · Complete original publisher JSON

nvd · CVE-2021-21334

Published

NVD analysis and CPE criteria are source context, not proof that a package or your environment is affected. Complete affected data, logical configurations and SSVC are retained in the original JSON.

Source analysis status: Modified

Weakness classifications: CWE-668

Original publisher date fields

published: 2021-03-10T22:15:12.183

lastModified: 2026-06-17T03:35:19.197

3 source CPE criteria · context only
  • cpe:2.3:a:linuxfoundation:containerd:*:*:*:*:*:*:*:*
  • cpe:2.3:o:fedoraproject:fedora:33:*:*:*:*:*:*:*
  • cpe:2.3:o:fedoraproject:fedora:34:*:*:*:*:*:*:*

The original JSON retains the logical configuration operators, exclusions and version bounds.

No normalized affected-package data is projected for this source revision. The original publisher record may contain additional product and version evidence; this does not establish that a package is unaffected.

Original source record · Cite this exact observation · Complete original publisher JSON

osv · GHSA-6g2q-w5j3-fwh4

Published

github.com/containerd/containerd

Go

SEMVER · introduced 1.4.0 → fixed 1.4.4

github.com/containerd/containerd

Go

SEMVER · introduced 0 → fixed 1.3.10

Original source record · Cite this exact observation · Complete original publisher JSON

ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 16 Nov 22:31 UTC · 274 of 275 readable · 250 fully read · 20 waiting for GitHub's hourly limit · documentation 469/469 current