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.

The version of docker installed on the remote host is prior to 20.10.4-1. It is, therefore, affected by multiple vulnerabilities as referenced in the ALAS2ECS-2023-015 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)

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

The remote NewStart CGSL host, running version CORE 5.05 / MAIN 5.05, has docker-ce packages installed that are affected by multiple vulnerabilities:

  - runc through 1.0.0-rc8, as used in Docker through 19.03.2-ce and other products, allows AppArmor     restriction bypass because libcontainer/rootfs_linux.go incorrectly checks mount targets, and thus a     malicious Docker image can mount over a /proc directory. (CVE-2019-16884)

  - 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)

  - 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.

According to the versions of the docker-engine packages installed, the EulerOS installation on the remote host is affected by the following vulnerabilities :

  - 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)

Note that Tenable Network Security has extracted the preceding description block directly from the EulerOS security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.

According to the versions of the docker-engine packages installed, the EulerOS installation on the remote host is affected by the following vulnerabilities :

  - In containerd (an industry-standard container runtime) before version 1.2.14 there is a credential leaking     vulnerability. If a container image manifest in the OCI Image format or Docker Image V2 Schema 2 format     includes a URL for the location of a specific image layer (otherwise known as a foreign layer), the     default containerd resolver will follow that URL to attempt to download it. In v1.2.x but not 1.3.0 or     later, the default containerd resolver will provide its authentication credentials if the server where the     URL is located presents an HTTP 401 status code along with registry-specific HTTP headers. If an attacker     publishes a public image with a manifest that directs one of the layers to be fetched from a web server     they control and they trick a user or system into pulling the image, they can obtain the credentials used     for pulling that image. In some cases, this may be the user's username and password for the registry. In     other cases, this may be the credentials attached to the cloud virtual instance which can grant access to     other cloud resources in the account. The default containerd resolver is used by the cri-containerd plugin     (which can be used by Kubernetes), the ctr development tool, and other client programs that have     explicitly linked against it. This vulnerability has been fixed in containerd 1.2.14. containerd 1.3 and     later are not affected. If you are using containerd 1.3 or later, you are not affected. If you are using     cri-containerd in the 1.2 series or prior, you should ensure you only pull images from trusted sources.
    Other container runtimes built on top of containerd but not using the default resolver (such as Docker)     are not affected. (CVE-2020-15157)

  - 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)

  - containerd is a container runtime. A bug was found in containerd versions prior to 1.4.8 and 1.5.4 where     pulling and extracting a specially-crafted container image can result in Unix file permission changes for     existing files in the host's filesystem. Changes to file permissions can deny access to the expected owner     of the file, widen access to others, or set extended bits like setuid, setgid, and sticky. This bug does     not directly allow files to be read, modified, or executed without an additional cooperating process. This     bug has been fixed in containerd 1.5.4 and 1.4.8. As a workaround, ensure that users only pull images from     trusted sources. Linux security modules (LSMs) like SELinux and AppArmor can limit the files potentially     affected by this bug through policies and profiles that prevent containerd from interacting with specific     files. (CVE-2021-32760)

Note that Tenable Network Security has extracted the preceding description block directly from the EulerOS security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.

The remote host is affected by the vulnerability described in GLSA-202107-23 (Docker: Multiple vulnerabilities)

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

    Please review the referenced CVE identifiers for details.
  Workaround :

    There is no known workaround at this time.

The version of docker installed on the remote host is prior to 20.10.7-2.69. It is, therefore, affected by multiple vulnerabilities as referenced in the ALAS-2021-1550 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)

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

The remote NewStart CGSL host, running version CORE 5.04 / MAIN 5.04, has docker-ce packages installed that are affected by a vulnerability:

  - 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)

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

The remote NewStart CGSL host, running version MAIN 6.02, has docker-ce packages installed that are affected by multiple vulnerabilities:

  - 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)

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: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 docker package has been released.

Multiple security issues were discovered in Docker, a Linux container runtime, which could result in denial of service, an information leak or privilege escalation.

This update for containerd, docker, docker-runc, golang-github-docker-libnetwork fixes the following issues :

Security issues fixed :

  - CVE-2020-15257: Fixed a privilege escalation in     containerd (bsc#1178969).

  - CVE-2021-21284: potential privilege escalation when the     root user in the remapped namespace has access to the     host filesystem (bsc#1181732)

  - CVE-2021-21285: pulling a malformed Docker image     manifest crashes the dockerd daemon (bsc#1181730)

Non-security issues fixed :

  - Update Docker to 19.03.15-ce. See upstream changelog in     the packaged     /usr/share/doc/packages/docker/CHANGELOG.md. This update     includes fixes for bsc#1181732 (CVE-2021-21284) and     bsc#1181730 (CVE-2021-21285).

  - Only apply the boo#1178801 libnetwork patch to handle     firewalld on openSUSE. It appears that SLES doesn't like     the patch. (bsc#1180401)

  - Update to containerd v1.3.9, which is needed for Docker     v19.03.14-ce and fixes CVE-2020-15257. bsc#1180243

  - Update to containerd v1.3.7, which is required for     Docker 19.03.13-ce. bsc#1176708

  - Update to Docker 19.03.14-ce. See upstream changelog in     the packaged     /usr/share/doc/packages/docker/CHANGELOG.md.
    CVE-2020-15257 bsc#1180243     https://github.com/docker/docker-ce/releases/tag/v19.03.
    14

  - Enable fish-completion

  - Add a patch which makes Docker compatible with firewalld     with nftables backend. Backport of     https://github.com/moby/libnetwork/pull/2548     (bsc#1178801, SLE-16460)

  - Update to Docker 19.03.13-ce. See upstream changelog in     the packaged     /usr/share/doc/packages/docker/CHANGELOG.md. bsc#1176708

  - Fixes for %_libexecdir changing to /usr/libexec     (bsc#1174075)

  - Emergency fix: %requires_eq does not work with provide     symbols, only effective package names. Convert back to     regular Requires.

  - Update to Docker 19.03.12-ce. See upstream changelog in     the packaged     /usr/share/doc/packages/docker/CHANGELOG.md.

  - Use Go 1.13 instead of Go 1.14 because Go 1.14 can cause     all sorts of spurrious errors due to Go returning -EINTR     from I/O syscalls much more often (due to Go 1.14's     pre-emptive goroutine support).

  - Add BuildRequires for all -git dependencies so that we     catch missing dependencies much more quickly.

  - Update to libnetwork 55e924b8a842, which is required for     Docker 19.03.14-ce. bsc#1180243

  - Add patch which makes libnetwork compatible with     firewalld with nftables backend. Backport of     https://github.com/moby/libnetwork/pull/2548     (bsc#1178801, SLE-16460)

This update was imported from the SUSE:SLE-15:Update update project.

This update for containerd, docker, docker-runc, golang-github-docker-libnetwork fixes the following issues :

Security issues fixed :

CVE-2020-15257: Fixed a privilege escalation in containerd (bsc#1178969).

CVE-2021-21284: potential privilege escalation when the root user in the remapped namespace has access to the host filesystem (bsc#1181732)

CVE-2021-21285: pulling a malformed Docker image manifest crashes the dockerd daemon (bsc#1181730)

Non-security issues fixed :

Update Docker to 19.03.15-ce. See upstream changelog in the packaged /usr/share/doc/packages/docker/CHANGELOG.md. This update includes fixes for bsc#1181732 (CVE-2021-21284) and bsc#1181730 (CVE-2021-21285).

Only apply the boo#1178801 libnetwork patch to handle firewalld on openSUSE. It appears that SLES doesn't like the patch. (bsc#1180401)

Update to containerd v1.3.9, which is needed for Docker v19.03.14-ce and fixes CVE-2020-15257. bsc#1180243

Update to containerd v1.3.7, which is required for Docker 19.03.13-ce.
bsc#1176708

Update to Docker 19.03.14-ce. See upstream changelog in the packaged /usr/share/doc/packages/docker/CHANGELOG.md. CVE-2020-15257 bsc#1180243 https://github.com/docker/docker-ce/releases/tag/v19.03.14

Enable fish-completion

Add a patch which makes Docker compatible with firewalld with nftables backend. Backport of https://github.com/moby/libnetwork/pull/2548 (bsc#1178801, SLE-16460)

Update to Docker 19.03.13-ce. See upstream changelog in the packaged /usr/share/doc/packages/docker/CHANGELOG.md. bsc#1176708

Fixes for %_libexecdir changing to /usr/libexec (bsc#1174075)

Emergency fix: %requires_eq does not work with provide symbols, only effective package names. Convert back to regular Requires.

Update to Docker 19.03.12-ce. See upstream changelog in the packaged /usr/share/doc/packages/docker/CHANGELOG.md.

Use Go 1.13 instead of Go 1.14 because Go 1.14 can cause all sorts of spurrious errors due to Go returning -EINTR from I/O syscalls much more often (due to Go 1.14's pre-emptive goroutine support).

Add BuildRequires for all -git dependencies so that we catch missing dependencies much more quickly.

Update to libnetwork 55e924b8a842, which is required for Docker 19.03.14-ce. bsc#1180243

Add patch which makes libnetwork compatible with firewalld with nftables backend. Backport of https://github.com/moby/libnetwork/pull/2548 (bsc#1178801, SLE-16460)

Note that Tenable Network Security has extracted the preceding description block directly from the SUSE security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.

ID	Name	Product	Family	Severity
183446	Amazon Linux 2 : docker (ALASECS-2023-015)	Nessus	Amazon Linux Local Security Checks	medium
160855	NewStart CGSL CORE 5.05 / MAIN 5.05 : docker-ce Multiple Vulnerabilities (NS-SA-2022-0033)	Nessus	NewStart CGSL Local Security Checks	high
160677	EulerOS 2.0 SP10 : docker-engine (EulerOS-SA-2022-1658)	Nessus	Huawei Local Security Checks	medium
160666	EulerOS 2.0 SP10 : docker-engine (EulerOS-SA-2022-1644)	Nessus	Huawei Local Security Checks	medium
159808	EulerOS 2.0 SP9 : docker-engine (EulerOS-SA-2022-1445)	Nessus	Huawei Local Security Checks	medium
159804	EulerOS 2.0 SP9 : docker-engine (EulerOS-SA-2022-1424)	Nessus	Huawei Local Security Checks	medium
156967	GLSA-202107-23 : Docker: Multiple vulnerabilities	Nessus	Gentoo Local Security Checks	medium
155354	Amazon Linux AMI : docker (ALAS-2021-1550)	Nessus	Amazon Linux Local Security Checks	medium
154533	NewStart CGSL CORE 5.04 / MAIN 5.04 : docker-ce Vulnerability (NS-SA-2021-0103)	Nessus	NewStart CGSL Local Security Checks	medium
154474	NewStart CGSL MAIN 6.02 : docker-ce Multiple Vulnerabilities (NS-SA-2021-0124)	Nessus	NewStart CGSL 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
149293	Photon OS 3.0: Docker PHSA-2021-3.0-0228	Nessus	PhotonOS Local Security Checks	medium
148352	Photon OS 4.0: Docker PHSA-2021-4.0-0007	Nessus	PhotonOS Local Security Checks	medium
146922	Debian DSA-4865-1 : docker.io - security update	Nessus	Debian Local Security Checks	medium
146506	openSUSE Security Update : containerd / docker / docker-runc / etc (openSUSE-2021-278)	Nessus	SuSE Local Security Checks	medium
146460	SUSE SLES15 Security Update : containerd, docker, docker-runc, golang-github-docker-libnetwork (SUSE-SU-2021:0435-1)	Nessus	SuSE Local Security Checks	medium

Detections

Analytics

CVE-2021-21284

medium

Tenable Plugins

medium

high

medium

medium

medium

medium

medium

medium

medium

medium

high

high

high

medium

medium

medium

medium

medium