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

  - Moby is an open-source project created by Docker to enable software containerization. A bug was found in     Moby (Docker Engine) where attempting to copy files using `docker cp` into a specially-crafted container     can result in Unix file permission changes for existing files in the host's filesystem, widening access to     others. This bug does not directly allow files to be read, modified, or executed without an additional     cooperating process. This bug has been fixed in Moby (Docker Engine) 20.10.9. Users should update to this     version as soon as possible. Running containers do not need to be restarted. (CVE-2021-41089)

  - Moby is an open-source project created by Docker to enable software containerization. A bug was found in     Moby (Docker Engine) where the data directory (typically `/var/lib/docker`) contained subdirectories with     insufficiently restricted permissions, allowing otherwise unprivileged Linux users to traverse directory     contents and execute programs. When containers included executable programs with extended permission bits     (such as `setuid`), unprivileged Linux users could discover and execute those programs. When the UID of an     unprivileged Linux user on the host collided with the file owner or group inside a container, the     unprivileged Linux user on the host could discover, read, and modify those files. This bug has been fixed     in Moby (Docker Engine) 20.10.9. Users should update to this version as soon as possible. Running     containers should be stopped and restarted for the permissions to be fixed. For users unable to upgrade     limit access to the host to trusted users. Limit access to host volumes to trusted containers.
    (CVE-2021-41091)

  - runc is a CLI tool for spawning and running containers on Linux according to the OCI specification. In     runc, netlink is used internally as a serialization system for specifying the relevant container     configuration to the `C` portion of the code (responsible for the based namespace setup of containers). In     all versions of runc prior to 1.0.3, the encoder did not handle the possibility of an integer overflow in     the 16-bit length field for the byte array attribute type, meaning that a large enough malicious byte     array attribute could result in the length overflowing and the attribute contents being parsed as netlink     messages for container configuration. This vulnerability requires the attacker to have some control over     the configuration of the container and would allow the attacker to bypass the namespace restrictions of     the container by simply adding their own netlink payload which disables all namespaces. The main users     impacted are those who allow untrusted images with untrusted configurations to run on their machines (such     as with shared cloud infrastructure). runc version 1.0.3 contains a fix for this bug. As a workaround, one     may try disallowing untrusted namespace paths from your container. It should be noted that untrusted     namespace paths would allow the attacker to disable namespace protections entirely even in the absence of     this bug. (CVE-2021-43784)

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

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

    Docker was updated to 20.10.9-ce. (bsc#1191355)

    See upstream changelog in the packaged       /usr/share/doc/packages/docker/CHANGELOG.md.

      CVE-2021-41092 CVE-2021-41089 CVE-2021-41091 CVE-2021-41103

    container was updated to v1.4.11, to fix CVE-2021-41103. bsc#1191355

    - CVE-2021-32760: Fixed that a archive package allows chmod of file outside of unpack target directory     (bsc#1188282)

    Update to runc v1.0.2. Upstream changelog is available from

      https://github.com/opencontainers/runc/releases/tag/v1.0.2

    * Fixed a failure to set CPU quota period in some cases on cgroup v1.
    * Fixed the inability to start a container with the 'adding seccomp filter       rule for syscall ...' error, caused by redundant seccomp rules (i.e. those       that has action equal to the default one). Such redundant rules are now       skipped.
    * Made release builds reproducible from now on.
    * Fixed a rare debug log race in runc init, which can result in occasional       harmful 'failed to decode ...' errors from runc run or exec.
    * Fixed the check in cgroup v1 systemd manager if a container needs to be       frozen before Set, and add a setting to skip such freeze unconditionally.
      The previous fix for that issue, done in runc 1.0.1, was not working.

    Update to runc v1.0.1. Upstream changelog is available from

    https://github.com/opencontainers/runc/releases/tag/v1.0.1

    * Fixed occasional runc exec/run failure ('interrupted system call') on an       Azure volume.
    * Fixed 'unable to find groups ... token too long' error with /etc/group       containing lines longer than 64K characters.
    * cgroup/systemd/v1: fix leaving cgroup frozen after Set if a parent cgroup is       frozen. This is a regression in 1.0.0, not affecting runc itself but some       of libcontainer users (e.g Kubernetes).
    * cgroupv2: bpf: Ignore inaccessible existing programs in case of       permission error when handling replacement of existing bpf cgroup       programs. This fixes a regression in 1.0.0, where some SELinux       policies would block runc from being able to run entirely.
    * cgroup/systemd/v2: don't freeze cgroup on Set.
    * cgroup/systemd/v1: avoid unnecessary freeze on Set.
    - fix issues with runc under openSUSE MicroOS's SELinux policy. bsc#1187704

    Update to runc v1.0.0. Upstream changelog is available from

    https://github.com/opencontainers/runc/releases/tag/v1.0.0

    ! The usage of relative paths for mountpoints will now produce a warning       (such configurations are outside of the spec, and in future runc will       produce an error when given such configurations).
    * cgroupv2: devices: rework the filter generation to produce consistent       results with cgroupv1, and always clobber any existing eBPF       program(s) to fix runc update and avoid leaking eBPF programs       (resulting in errors when managing containers).
    * cgroupv2: correctly convert 'number of IOs' statistics in a       cgroupv1-compatible way.
    * cgroupv2: support larger than 32-bit IO statistics on 32-bit architectures.
    * cgroupv2: wait for freeze to finish before returning from the freezing       code, optimize the method for checking whether a cgroup is frozen.
    * cgroups/systemd: fixed 'retry on dbus disconnect' logic introduced in rc94
    * cgroups/systemd: fixed returning 'unit already exists' error from a systemd       cgroup manager (regression in rc94)     + cgroupv2: support SkipDevices with systemd driver     + cgroup/systemd: return, not ignore, stop unit error from Destroy     + Make 'runc --version' output sane even when built with go get or       otherwise outside of our build scripts.
    + cgroups: set SkipDevices during runc update (so we don't modify       cgroups at all during runc update).
    + cgroup1: blkio: support BFQ weights.
    + cgroupv2: set per-device io weights if BFQ IO scheduler is available.

    Update to runc v1.0.0~rc95. Upstream changelog is available from     https://github.com/opencontainers/runc/releases/tag/v1.0.0-rc95

    This release of runc contains a fix for CVE-2021-30465, and users are     strongly recommended to update (especially if you are providing     semi-limited access to spawn containers to untrusted users). (bsc#1185405)

    Update to runc v1.0.0~rc94. Upstream changelog is available from     https://github.com/opencontainers/runc/releases/tag/v1.0.0-rc94

    Breaking Changes:
    * cgroupv1: kernel memory limits are now always ignored, as kmemcg has       been effectively deprecated by the kernel. Users should make use of regular       memory cgroup controls.

    Regression Fixes:

    * seccomp: fix 32-bit compilation errors
    * runc init: fix a hang caused by deadlock in seccomp/ebpf loading code
    * runc start: fix 'chdir to cwd: permission denied' for some setups

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

Note that Nessus has not tested for these issues 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:3506-1 advisory.

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

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

  - Moby is an open-source project created by Docker to enable software containerization. A bug was found in     Moby (Docker Engine) where attempting to copy files using `docker cp` into a specially-crafted container     can result in Unix file permission changes for existing files in the host's filesystem, widening access to     others. This bug does not directly allow files to be read, modified, or executed without an additional     cooperating process. This bug has been fixed in Moby (Docker Engine) 20.10.9. Users should update to this     version as soon as possible. Running containers do not need to be restarted. (CVE-2021-41089)

  - Moby is an open-source project created by Docker to enable software containerization. A bug was found in     Moby (Docker Engine) where the data directory (typically `/var/lib/docker`) contained subdirectories with     insufficiently restricted permissions, allowing otherwise unprivileged Linux users to traverse directory     contents and execute programs. When containers included executable programs with extended permission bits     (such as `setuid`), unprivileged Linux users could discover and execute those programs. When the UID of an     unprivileged Linux user on the host collided with the file owner or group inside a container, the     unprivileged Linux user on the host could discover, read, and modify those files. This bug has been fixed     in Moby (Docker Engine) 20.10.9. Users should update to this version as soon as possible. Running     containers should be stopped and restarted for the permissions to be fixed. For users unable to upgrade     limit access to the host to trusted users. Limit access to host volumes to trusted containers.
    (CVE-2021-41091)

  - Docker CLI is the command line interface for the docker container runtime. A bug was found in the Docker     CLI where running `docker login my-private-registry.example.com` with a misconfigured configuration file     (typically `~/.docker/config.json`) listing a `credsStore` or `credHelpers` that could not be executed     would result in any provided credentials being sent to `registry-1.docker.io` rather than the intended     private registry. This bug has been fixed in Docker CLI 20.10.9. Users should update to this version as     soon as possible. For users unable to update ensure that any configured credsStore or credHelpers entries     in the configuration file reference an installed credential helper that is executable and on the PATH.
    (CVE-2021-41092)

  - containerd is an open source container runtime with an emphasis on simplicity, robustness and portability.
    A bug was found in containerd where container root directories and some plugins had insufficiently     restricted permissions, allowing otherwise unprivileged Linux users to traverse directory contents and     execute programs. When containers included executable programs with extended permission bits (such as     setuid), unprivileged Linux users could discover and execute those programs. When the UID of an     unprivileged Linux user on the host collided with the file owner or group inside a container, the     unprivileged Linux user on the host could discover, read, and modify those files. This vulnerability has     been fixed in containerd 1.4.11 and containerd 1.5.7. Users should update to these version when they are     released and may restart containers or update directory permissions to mitigate the vulnerability. Users     unable to update should limit access to the host to trusted users. Update directory permission on     container bundles directories. (CVE-2021-41103)

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:1404-1 advisory.

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

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

  - Moby is an open-source project created by Docker to enable software containerization. A bug was found in     Moby (Docker Engine) where attempting to copy files using `docker cp` into a specially-crafted container     can result in Unix file permission changes for existing files in the host's filesystem, widening access to     others. This bug does not directly allow files to be read, modified, or executed without an additional     cooperating process. This bug has been fixed in Moby (Docker Engine) 20.10.9. Users should update to this     version as soon as possible. Running containers do not need to be restarted. (CVE-2021-41089)

  - Moby is an open-source project created by Docker to enable software containerization. A bug was found in     Moby (Docker Engine) where the data directory (typically `/var/lib/docker`) contained subdirectories with     insufficiently restricted permissions, allowing otherwise unprivileged Linux users to traverse directory     contents and execute programs. When containers included executable programs with extended permission bits     (such as `setuid`), unprivileged Linux users could discover and execute those programs. When the UID of an     unprivileged Linux user on the host collided with the file owner or group inside a container, the     unprivileged Linux user on the host could discover, read, and modify those files. This bug has been fixed     in Moby (Docker Engine) 20.10.9. Users should update to this version as soon as possible. Running     containers should be stopped and restarted for the permissions to be fixed. For users unable to upgrade     limit access to the host to trusted users. Limit access to host volumes to trusted containers.
    (CVE-2021-41091)

  - Docker CLI is the command line interface for the docker container runtime. A bug was found in the Docker     CLI where running `docker login my-private-registry.example.com` with a misconfigured configuration file     (typically `~/.docker/config.json`) listing a `credsStore` or `credHelpers` that could not be executed     would result in any provided credentials being sent to `registry-1.docker.io` rather than the intended     private registry. This bug has been fixed in Docker CLI 20.10.9. Users should update to this version as     soon as possible. For users unable to update ensure that any configured credsStore or credHelpers entries     in the configuration file reference an installed credential helper that is executable and on the PATH.
    (CVE-2021-41092)

  - containerd is an open source container runtime with an emphasis on simplicity, robustness and portability.
    A bug was found in containerd where container root directories and some plugins had insufficiently     restricted permissions, allowing otherwise unprivileged Linux users to traverse directory contents and     execute programs. When containers included executable programs with extended permission bits (such as     setuid), unprivileged Linux users could discover and execute those programs. When the UID of an     unprivileged Linux user on the host collided with the file owner or group inside a container, the     unprivileged Linux user on the host could discover, read, and modify those files. This vulnerability has     been fixed in containerd 1.4.11 and containerd 1.5.7. Users should update to these version when they are     released and may restart containers or update directory permissions to mitigate the vulnerability. Users     unable to update should limit access to the host to trusted users. Update directory permission on     container bundles directories. (CVE-2021-41103)

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

ID	名称	产品	系列	发布时间	最近更新时间	严重程度
174054	NewStart CGSL CORE 5.05 / MAIN 5.05 : docker-ce Multiple Vulnerabilities (NS-SA-2023-0014)	Nessus	NewStart CGSL Local Security Checks	2023/4/11	2023/4/12	medium
154100	SUSE SLES12 Security Update : containerd, docker, runc (SUSE-SU-2021:3336-1)	Nessus	SuSE Local Security Checks	2021/10/13	2026/6/26	high
154606	openSUSE 15 Security Update : containerd, docker, runc (openSUSE-SU-2021:3506-1)	Nessus	SuSE Local Security Checks	2021/10/28	2023/11/27	high
154769	openSUSE 15 Security Update : containerd, docker, runc (openSUSE-SU-2021:1404-1)	Nessus	SuSE Local Security Checks	2021/11/1	2023/11/27	high

检测

插件搜索

medium

high

high

high