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.

An update of the telegraf package has been released.

The version of containerd installed on the remote host is prior to 1.4.4-1. It is, therefore, affected by a vulnerability as referenced in the ALAS2ECS-2023-014 advisory.

  - 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. (CVE-2021-21334)

Note that Nessus has not tested for this issue but has instead relied only on the application's self-reported version number.

The remote host is affected by the vulnerability described in GLSA-202105-33 (containerd: Multiple vulnerabilities)

    Multiple vulnerabilities have been discovered in containerd. Please       review the CVE identifiers referenced below for details.
  Impact :

    A local attacker, able to run a malicious container in the same network       namespace as the shim, could possibly escalate privileges. Furthermore,       an attacker could disclose sensitive information.
  Workaround :

    There is no known workaround at this time.

The remote SUSE Linux SUSE15 host has packages installed that are affected by multiple vulnerabilities as referenced in the openSUSE-SU-2021:1954-1 advisory.

  - In Docker before versions 9.03.15, 20.10.3 there is a vulnerability involving the --userns-remap option in     which access to remapped root allows privilege escalation to real root. When using --userns-remap, if     the root user in the remapped namespace has access to the host filesystem they can modify files under     /var/lib/docker/ that cause writing files with extended privileges. Versions 20.10.3 and     19.03.15 contain patches that prevent privilege escalation from remapped user. (CVE-2021-21284)

  - In Docker before versions 9.03.15, 20.10.3 there is a vulnerability in which pulling an intentionally     malformed Docker image manifest crashes the dockerd daemon. Versions 20.10.3 and 19.03.15 contain patches     that prevent the daemon from crashing. (CVE-2021-21285)

  - 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. (CVE-2021-21334)

  - runc before 1.0.0-rc95 allows a Container Filesystem Breakout via Directory Traversal. To exploit the     vulnerability, an attacker must be able to create multiple containers with a fairly specific mount     configuration. The problem occurs via a symlink-exchange attack that relies on a race condition.
    (CVE-2021-30465)

Note that Nessus has not tested for this issue but has instead relied only on the application's self-reported version number.

The remote SUSE Linux SUSE15 host has packages installed that are affected by multiple vulnerabilities as referenced in the openSUSE-SU-2021:0878-1 advisory.

  - In Docker before versions 9.03.15, 20.10.3 there is a vulnerability involving the --userns-remap option in     which access to remapped root allows privilege escalation to real root. When using --userns-remap, if     the root user in the remapped namespace has access to the host filesystem they can modify files under     /var/lib/docker/ that cause writing files with extended privileges. Versions 20.10.3 and     19.03.15 contain patches that prevent privilege escalation from remapped user. (CVE-2021-21284)

  - In Docker before versions 9.03.15, 20.10.3 there is a vulnerability in which pulling an intentionally     malformed Docker image manifest crashes the dockerd daemon. Versions 20.10.3 and 19.03.15 contain patches     that prevent the daemon from crashing. (CVE-2021-21285)

  - 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. (CVE-2021-21334)

  - runc before 1.0.0-rc95 allows a Container Filesystem Breakout via Directory Traversal. To exploit the     vulnerability, an attacker must be able to create multiple containers with a fairly specific mount     configuration. The problem occurs via a symlink-exchange attack that relies on a race condition.
    (CVE-2021-30465)

Note that Nessus has not tested for this issue but has instead relied only on the application's self-reported version number.

The remote SUSE Linux SLES15 / SLES_SAP15 host has packages installed that are affected by multiple vulnerabilities as referenced in the SUSE-SU-2021:1954-1 advisory.

  - In Docker before versions 9.03.15, 20.10.3 there is a vulnerability involving the --userns-remap option in     which access to remapped root allows privilege escalation to real root. When using --userns-remap, if     the root user in the remapped namespace has access to the host filesystem they can modify files under     /var/lib/docker/<remapping> that cause writing files with extended privileges. Versions 20.10.3 and     19.03.15 contain patches that prevent privilege escalation from remapped user. (CVE-2021-21284)

  - In Docker before versions 9.03.15, 20.10.3 there is a vulnerability in which pulling an intentionally     malformed Docker image manifest crashes the dockerd daemon. Versions 20.10.3 and 19.03.15 contain patches     that prevent the daemon from crashing. (CVE-2021-21285)

  - 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. (CVE-2021-21334)

  - runc before 1.0.0-rc95 allows a Container Filesystem Breakout via Directory Traversal. To exploit the     vulnerability, an attacker must be able to create multiple containers with a fairly specific mount     configuration. The problem occurs via a symlink-exchange attack that relies on a race condition.
    (CVE-2021-30465)

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

An update of the containerd package has been released.

The remote Ubuntu 20.04 LTS host has a package installed that is affected by a vulnerability as referenced in the USN-4881-1 advisory.

    It was discovered that containerd incorrectly handled certain environment variables. Contrary to     expectations, a container could receive environment variables defined for a different container, possibly     containing sensitive information.

Tenable has extracted the preceding description block directly from the Ubuntu security advisory.

Note that Nessus has not tested for this issue but has instead relied only on the application's self-reported version number.

The remote Fedora 33 host has a package installed that is affected by multiple vulnerabilities as referenced in the FEDORA-2021-470fa24f5b advisory.

  - 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. (CVE-2021-21334)

Note that Nessus has not tested for this issue but has instead relied only on the application's self-reported version number.

The remote Fedora 33 host has a package installed that is affected by a vulnerability as referenced in the FEDORA-2021-10ce8fcbf1 advisory.

  - 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. (CVE-2021-21334)

Note that Nessus has not tested for this issue but has instead relied only on the application's self-reported version number.

ID	Name	Product	Family	Severity
204388	Photon OS 5.0: Telegraf PHSA-2023-5.0-0041	Nessus	PhotonOS Local Security Checks	high
183449	Amazon Linux 2 : containerd (ALASECS-2023-014)	Nessus	Amazon Linux Local Security Checks	medium
156977	GLSA-202105-33 : containerd: Multiple vulnerabilities	Nessus	Gentoo Local Security Checks	medium
151692	openSUSE 15 Security Update : containerd, docker, runc (openSUSE-SU-2021:1954-1)	Nessus	SuSE Local Security Checks	high
151074	openSUSE 15 Security Update : containerd, docker, runc (openSUSE-SU-2021:0878-1)	Nessus	SuSE Local Security Checks	high
150729	SUSE SLES15 Security Update : containerd, docker, runc (SUSE-SU-2021:1954-1)	Nessus	SuSE Local Security Checks	high
148345	Photon OS 4.0: Containerd PHSA-2021-4.0-0007	Nessus	PhotonOS Local Security Checks	medium
148288	Photon OS 2.0: Containerd PHSA-2021-2.0-0333	Nessus	PhotonOS Local Security Checks	medium
148190	Photon OS 3.0: Containerd PHSA-2021-3.0-0210	Nessus	PhotonOS Local Security Checks	medium
147968	Ubuntu 20.04 LTS : containerd vulnerability (USN-4881-1)	Nessus	Ubuntu Local Security Checks	medium
147787	Fedora 33 : containerd (2021-470fa24f5b)	Nessus	Fedora Local Security Checks	medium
147769	Fedora 33 : 1:golang-github-containerd-cri (2021-10ce8fcbf1)	Nessus	Fedora Local Security Checks	medium

Detections

Analytics

CVE-2021-21334

medium

Tenable Plugins

high

medium

medium

high

high

high

medium

medium

medium

medium

medium

medium