containerd is an open source container runtime. A bug was found in the containerd's CRI implementation where programs inside a container can cause the containerd daemon to consume memory without bound during invocation of the `ExecSync` API. This can cause containerd to consume all available memory on the computer, denying service to other legitimate workloads. Kubernetes and crictl can both be configured to use containerd's CRI implementation; `ExecSync` may be used when running probes or when executing processes via an "exec" facility. This bug has been fixed in containerd 1.6.6 and 1.5.13. Users should update to these versions to resolve the issue. Users unable to upgrade should ensure that only trusted images and commands are used.

An update of the telegraf package has been released.

An update of the containerd package has been released.

An update of the fuse package has been released.

The remote host is affected by the vulnerability described in GLSA-202401-31 (containerd: Multiple Vulnerabilities)

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

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

  - containerd is an open source container runtime. A bug was found in containerd's CRI implementation where a     user can exhaust memory on the host. In the CRI stream server, a goroutine is launched to handle terminal     resize events if a TTY is requested. If the user's process fails to launch due to, for example, a faulty     command, the goroutine will be stuck waiting to send without a receiver, resulting in a memory leak.
    Kubernetes and crictl can both be configured to use containerd's CRI implementation and the stream server     is used for handling container IO. This bug has been fixed in containerd 1.6.12 and 1.5.16. Users should     update to these versions to resolve the issue. Users unable to upgrade should ensure that only trusted     images and commands are used and that only trusted users have permissions to execute commands in running     containers. (CVE-2022-23471)

  - containerd is a container runtime available as a daemon for Linux and Windows. A bug was found in     containerd prior to versions 1.6.1, 1.5.10, and 1.14.12 where containers launched through containerd's CRI     implementation on Linux with a specially-crafted image configuration could gain access to read-only copies     of arbitrary files and directories on the host. This may bypass any policy-based enforcement on container     setup (including a Kubernetes Pod Security Policy) and expose potentially sensitive information.
    Kubernetes and crictl can both be configured to use containerd's CRI implementation. This bug has been     fixed in containerd 1.6.1, 1.5.10, and 1.4.12. Users should update to these versions to resolve the issue.
    (CVE-2022-23648)

  - Moby is an open-source project created by Docker to enable and accelerate software containerization. A bug     was found in Moby (Docker Engine) prior to version 20.10.14 where containers were incorrectly started with     non-empty inheritable Linux process capabilities, creating an atypical Linux environment and enabling     programs with inheritable file capabilities to elevate those capabilities to the permitted set during     `execve(2)`. Normally, when executable programs have specified permitted file capabilities, otherwise     unprivileged users and processes can execute those programs and gain the specified file capabilities up to     the bounding set. Due to this bug, containers which included executable programs with inheritable file     capabilities allowed otherwise unprivileged users and processes to additionally gain these inheritable     file capabilities up to the container's bounding set. Containers which use Linux users and groups to     perform privilege separation inside the container are most directly impacted. This bug did not affect the     container security sandbox as the inheritable set never contained more capabilities than were included in     the container's bounding set. This bug has been fixed in Moby (Docker Engine) 20.10.14. Running containers     should be stopped, deleted, and recreated for the inheritable capabilities to be reset. This fix changes     Moby (Docker Engine) behavior such that containers are started with a more typical Linux environment. As a     workaround, the entry point of a container can be modified to use a utility like `capsh(1)` to drop     inheritable capabilities prior to the primary process starting. (CVE-2022-24769)

  - containerd is an open source container runtime. A bug was found in the containerd's CRI implementation     where programs inside a container can cause the containerd daemon to consume memory without bound during     invocation of the `ExecSync` API. This can cause containerd to consume all available memory on the     computer, denying service to other legitimate workloads. Kubernetes and crictl can both be configured to     use containerd's CRI implementation; `ExecSync` may be used when running probes or when executing     processes via an exec facility. This bug has been fixed in containerd 1.6.6 and 1.5.13. Users should     update to these versions to resolve the issue. Users unable to upgrade should ensure that only trusted     images and commands are used. (CVE-2022-31030)

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

The remote Ubuntu 16.04 ESM host has a package installed that is affected by multiple vulnerabilities as referenced in the USN-5521-1 advisory.

    It was discovered that containerd insufficiently restricted permissions on container root and plugin     directories. If a user or automated system were tricked into launching a specially crafted container     image, a remote attacker could traverse directory contents and modify files and execute programs on the     host file system, possibly leading to privilege escalation. (CVE-2021-41103)

    It was discovered that containerd incorrectly handled file permission changes. If a user or automated     system were tricked into launching a specially crafted container image, a remote attacker could change     permissions on files on the host file system and possibly escalate privileges. (CVE-2021-32760)

    It was discovered that containerd allows attackers to gain access to read- only copies of arbitrary files     and directories on the host via a specially- crafted image configuration. An attacker could possibly use     this issue to obtain sensitive information. (CVE-2022-23648)

    It was discovered that containerd incorrectly handled certain memory operations. A remote attacker could     use this to cause a denial of service. (CVE-2022-31030)

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

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 package installed, the EulerOS installation on the remote host is affected by the following vulnerabilities :

  - containerd is an open source container runtime. A bug was found in the containerd's CRI implementation     where programs inside a container can cause the containerd daemon to consume memory without bound during     invocation of the `ExecSync` API. This can cause containerd to consume all available memory on the     computer, denying service to other legitimate workloads. Kubernetes and crictl can both be configured to     use containerd's CRI implementation; `ExecSync` may be used when running probes or when executing     processes via an 'exec' facility. This bug has been fixed in containerd 1.6.6 and 1.5.13. Users should     update to these versions to resolve the issue. Users unable to upgrade should ensure that only trusted     images and commands are used. (CVE-2022-31030)

  - containerd is an open source container runtime. Before versions 1.6.18 and 1.5.18, when importing an OCI     image, there was no limit on the number of bytes read for certain files. A maliciously crafted image with     a large file where a limit was not applied could cause a denial of service. This bug has been fixed in     containerd 1.6.18 and 1.5.18. Users should update to these versions to resolve the issue. As a workaround,     ensure that only trusted images are used and that only trusted users have permissions to import images.
    (CVE-2023-25153)

  - containerd is an open source container runtime. A bug was found in containerd prior to versions 1.6.18 and     1.5.18 where supplementary groups are not set up properly inside a container. If an attacker has direct     access to a container and manipulates their supplementary group access, they may be able to use     supplementary group access to bypass primary group restrictions in some cases, potentially gaining access     to sensitive information or gaining the ability to execute code in that container. Downstream applications     that use the containerd client library may be affected as well. This bug has been fixed in containerd     v1.6.18 and v.1.5.18. Users should update to these versions and recreate containers to resolve this issue.
    Users who rely on a downstream application that uses containerd's client library should check that     application for a separate advisory and instructions. As a workaround, ensure that the `'USER $USERNAME'`     Dockerfile instruction is not used. Instead, set the container entrypoint to a value similar to     `ENTRYPOINT ['su', '-', 'user']` to allow `su` to properly set up supplementary groups. (CVE-2023-25173)

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 package installed, the EulerOS installation on the remote host is affected by the following vulnerabilities :

  - containerd is an open source container runtime. A bug was found in the containerd's CRI implementation     where programs inside a container can cause the containerd daemon to consume memory without bound during     invocation of the `ExecSync` API. This can cause containerd to consume all available memory on the     computer, denying service to other legitimate workloads. Kubernetes and crictl can both be configured to     use containerd's CRI implementation; `ExecSync` may be used when running probes or when executing     processes via an 'exec' facility. This bug has been fixed in containerd 1.6.6 and 1.5.13. Users should     update to these versions to resolve the issue. Users unable to upgrade should ensure that only trusted     images and commands are used. (CVE-2022-31030)

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.

It is, therefore, affected by multiple vulnerabilities as referenced in the ALAS2023-2023-079 advisory.

  - containerd is a container runtime available as a daemon for Linux and Windows. A bug was found in     containerd prior to versions 1.6.1, 1.5.10, and 1.14.12 where containers launched through containerd's CRI     implementation on Linux with a specially-crafted image configuration could gain access to read-only copies     of arbitrary files and directories on the host. This may bypass any policy-based enforcement on container     setup (including a Kubernetes Pod Security Policy) and expose potentially sensitive information.
    Kubernetes and crictl can both be configured to use containerd's CRI implementation. This bug has been     fixed in containerd 1.6.1, 1.5.10, and 1.4.12. Users should update to these versions to resolve the issue.
    (CVE-2022-23648)

  - Moby is an open-source project created by Docker to enable and accelerate software containerization. A bug     was found in Moby (Docker Engine) prior to version 20.10.14 where containers were incorrectly started with     non-empty inheritable Linux process capabilities, creating an atypical Linux environment and enabling     programs with inheritable file capabilities to elevate those capabilities to the permitted set during     `execve(2)`. Normally, when executable programs have specified permitted file capabilities, otherwise     unprivileged users and processes can execute those programs and gain the specified file capabilities up to     the bounding set. Due to this bug, containers which included executable programs with inheritable file     capabilities allowed otherwise unprivileged users and processes to additionally gain these inheritable     file capabilities up to the container's bounding set. Containers which use Linux users and groups to     perform privilege separation inside the container are most directly impacted. This bug did not affect the     container security sandbox as the inheritable set never contained more capabilities than were included in     the container's bounding set. This bug has been fixed in Moby (Docker Engine) 20.10.14. Running containers     should be stopped, deleted, and recreated for the inheritable capabilities to be reset. This fix changes     Moby (Docker Engine) behavior such that containers are started with a more typical Linux environment. As a     workaround, the entry point of a container can be modified to use a utility like `capsh(1)` to drop     inheritable capabilities prior to the primary process starting. (CVE-2022-24769)

  - containerd is an open source container runtime. A bug was found in the containerd's CRI implementation     where programs inside a container can cause the containerd daemon to consume memory without bound during     invocation of the `ExecSync` API. This can cause containerd to consume all available memory on the     computer, denying service to other legitimate workloads. Kubernetes and crictl can both be configured to     use containerd's CRI implementation; `ExecSync` may be used when running probes or when executing     processes via an exec facility. This bug has been fixed in containerd 1.6.6 and 1.5.13. Users should     update to these versions to resolve the issue. Users unable to upgrade should ensure that only trusted     images and commands are used. (CVE-2022-31030)

  - Moby is an open-source project created by Docker to enable software containerization. A bug was found in     Moby (Docker Engine) where supplementary groups are not set up properly. If an attacker has direct access     to a container and manipulates their supplementary group access, they may be able to use supplementary     group access to bypass primary group restrictions in some cases, potentially gaining access to sensitive     information or gaining the ability to execute code in that container. This bug is fixed in Moby (Docker     Engine) 20.10.18. Running containers should be stopped and restarted for the permissions to be fixed. For     users unable to upgrade, this problem can be worked around by not using the `USER $USERNAME` Dockerfile     instruction. Instead by calling `ENTRYPOINT [su, -, user]` the supplementary groups will be set up     properly. (CVE-2022-36109)

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 containerd package installed, the EulerOS installation on the remote host is affected by the following vulnerabilities :

  - containerd is an open source container runtime. A bug was found in the containerd's CRI implementation     where programs inside a container can cause the containerd daemon to consume memory without bound during     invocation of the `ExecSync` API. This can cause containerd to consume all available memory on the     computer, denying service to other legitimate workloads. Kubernetes and crictl can both be configured to     use containerd's CRI implementation; `ExecSync` may be used when running probes or when executing     processes via an 'exec' facility. This bug has been fixed in containerd 1.6.6 and 1.5.13. Users should     update to these versions to resolve the issue. Users unable to upgrade should ensure that only trusted     images and commands are used. (CVE-2022-31030)

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.

It is, therefore, affected by multiple vulnerabilities as referenced in the ALAS2022-2022-210 advisory.

  - containerd is a container runtime available as a daemon for Linux and Windows. A bug was found in     containerd prior to versions 1.6.1, 1.5.10, and 1.14.12 where containers launched through containerd's CRI     implementation on Linux with a specially-crafted image configuration could gain access to read-only copies     of arbitrary files and directories on the host. This may bypass any policy-based enforcement on container     setup (including a Kubernetes Pod Security Policy) and expose potentially sensitive information.
    Kubernetes and crictl can both be configured to use containerd's CRI implementation. This bug has been     fixed in containerd 1.6.1, 1.5.10, and 1.4.12. Users should update to these versions to resolve the issue.
    (CVE-2022-23648)

  - Moby is an open-source project created by Docker to enable and accelerate software containerization. A bug     was found in Moby (Docker Engine) prior to version 20.10.14 where containers were incorrectly started with     non-empty inheritable Linux process capabilities, creating an atypical Linux environment and enabling     programs with inheritable file capabilities to elevate those capabilities to the permitted set during     `execve(2)`. Normally, when executable programs have specified permitted file capabilities, otherwise     unprivileged users and processes can execute those programs and gain the specified file capabilities up to     the bounding set. Due to this bug, containers which included executable programs with inheritable file     capabilities allowed otherwise unprivileged users and processes to additionally gain these inheritable     file capabilities up to the container's bounding set. Containers which use Linux users and groups to     perform privilege separation inside the container are most directly impacted. This bug did not affect the     container security sandbox as the inheritable set never contained more capabilities than were included in     the container's bounding set. This bug has been fixed in Moby (Docker Engine) 20.10.14. Running containers     should be stopped, deleted, and recreated for the inheritable capabilities to be reset. This fix changes     Moby (Docker Engine) behavior such that containers are started with a more typical Linux environment. As a     workaround, the entry point of a container can be modified to use a utility like `capsh(1)` to drop     inheritable capabilities prior to the primary process starting. (CVE-2022-24769)

  - containerd is an open source container runtime. A bug was found in the containerd's CRI implementation     where programs inside a container can cause the containerd daemon to consume memory without bound during     invocation of the `ExecSync` API. This can cause containerd to consume all available memory on the     computer, denying service to other legitimate workloads. Kubernetes and crictl can both be configured to     use containerd's CRI implementation; `ExecSync` may be used when running probes or when executing     processes via an exec facility. This bug has been fixed in containerd 1.6.6 and 1.5.13. Users should     update to these versions to resolve the issue. Users unable to upgrade should ensure that only trusted     images and commands are used. (CVE-2022-31030)

  - Moby is an open-source project created by Docker to enable software containerization. A bug was found in     Moby (Docker Engine) where supplementary groups are not set up properly. If an attacker has direct access     to a container and manipulates their supplementary group access, they may be able to use supplementary     group access to bypass primary group restrictions in some cases, potentially gaining access to sensitive     information or gaining the ability to execute code in that container. This bug is fixed in Moby (Docker     Engine) 20.10.18. Running containers should be stopped and restarted for the permissions to be fixed. For     users unable to upgrade, this problem can be worked around by not using the `USER $USERNAME` Dockerfile     instruction. Instead by calling `ENTRYPOINT [su, -, user]` the supplementary groups will be set up     properly. (CVE-2022-36109)

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

The remote Ubuntu 18.04 LTS / 20.04 LTS / 22.04 LTS host has packages installed that are affected by multiple vulnerabilities as referenced in the USN-5776-1 advisory.

    It was discovered that containerd incorrectly handled memory when receiving certain faulty Exec or     ExecSync commands. A remote attacker could possibly use this issue to cause a denial of service or crash     containerd. (CVE-2022-23471, CVE-2022-31030)

    It was discovered that containerd incorrectly set up inheritable file capabilities. An attacker could     possibly use this issue to escalate

    privileges inside a container. This issue only affected Ubuntu 18.04 LTS, Ubuntu 20.04 LTS and Ubuntu     22.04 LTS. (CVE-2022-24769)

    It was discovered that containerd incorrectly handled access to encrypted container images when using     imgcrypt library. A remote attacker could possibly use this issue to access encrypted images from other     users.

    This issue only affected Ubuntu 18.04 LTS, Ubuntu 20.04 LTS and Ubuntu 22.04 LTS. (CVE-2022-24778)

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

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

It is, therefore, affected by multiple vulnerabilities as referenced in the ALAS2022-2022-156 advisory.

  - containerd is an open source container runtime. A bug was found in the containerd's CRI implementation     where programs inside a container can cause the containerd daemon to consume memory without bound during     invocation of the `ExecSync` API. This can cause containerd to consume all available memory on the     computer, denying service to other legitimate workloads. Kubernetes and crictl can both be configured to     use containerd's CRI implementation; `ExecSync` may be used when running probes or when executing     processes via an exec facility. This bug has been fixed in containerd 1.6.6 and 1.5.13. Users should     update to these versions to resolve the issue. Users unable to upgrade should ensure that only trusted     images and commands are used. (CVE-2022-31030)

  - Moby is an open-source project created by Docker to enable software containerization. A bug was found in     Moby (Docker Engine) where supplementary groups are not set up properly. If an attacker has direct access     to a container and manipulates their supplementary group access, they may be able to use supplementary     group access to bypass primary group restrictions in some cases, potentially gaining access to sensitive     information or gaining the ability to execute code in that container. This bug is fixed in Moby (Docker     Engine) 20.10.18. Running containers should be stopped and restarted for the permissions to be fixed. For     users unable to upgrade, this problem can be worked around by not using the `USER $USERNAME` Dockerfile     instruction. Instead by calling `ENTRYPOINT [su, -, user]` the supplementary groups will be set up     properly. (CVE-2022-36109)

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

It is, therefore, affected by a vulnerability as referenced in the ALAS2022-2022-088 advisory.

  - containerd is an open source container runtime. A bug was found in the containerd's CRI implementation     where programs inside a container can cause the containerd daemon to consume memory without bound during     invocation of the `ExecSync` API. This can cause containerd to consume all available memory on the     computer, denying service to other legitimate workloads. Kubernetes and crictl can both be configured to     use containerd's CRI implementation; `ExecSync` may be used when running probes or when executing     processes via an exec facility. This bug has been fixed in containerd 1.6.6 and 1.5.13. Users should     update to these versions to resolve the issue. Users unable to upgrade should ensure that only trusted     images and commands are used. (CVE-2022-31030)

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

  - runc is a CLI tool for spawning and running containers on Linux according to the OCI specification. A bug     was found in runc prior to version 1.1.2 where `runc exec --cap` created processes with non-empty     inheritable Linux process capabilities, creating an atypical Linux environment and enabling programs with     inheritable file capabilities to elevate those capabilities to the permitted set during execve(2). This     bug did not affect the container security sandbox as the inheritable set never contained more capabilities     than were included in the container's bounding set. This bug has been fixed in runc 1.1.2. This fix     changes `runc exec --cap` behavior such that the additional capabilities granted to the process being     executed (as specified via `--cap` arguments) do not include inheritable capabilities. In addition, `runc     spec` is changed to not set any inheritable capabilities in the created example OCI spec (`config.json`)     file. (CVE-2022-29162)

  - containerd is an open source container runtime. A bug was found in the containerd's CRI implementation     where programs inside a container can cause the containerd daemon to consume memory without bound during     invocation of the `ExecSync` API. This can cause containerd to consume all available memory on the     computer, denying service to other legitimate workloads. Kubernetes and crictl can both be configured to     use containerd's CRI implementation; `ExecSync` may be used when running probes or when executing     processes via an exec facility. This bug has been fixed in containerd 1.6.6 and 1.5.13. Users should     update to these versions to resolve the issue. Users unable to upgrade should ensure that only trusted     images and commands are used. (CVE-2022-31030)

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 / SLES_SAP12 host has packages installed that are affected by multiple vulnerabilities as referenced in the SUSE-SU-2022:2165-1 advisory.

  - runc is a CLI tool for spawning and running containers on Linux according to the OCI specification. A bug     was found in runc prior to version 1.1.2 where `runc exec --cap` created processes with non-empty     inheritable Linux process capabilities, creating an atypical Linux environment and enabling programs with     inheritable file capabilities to elevate those capabilities to the permitted set during execve(2). This     bug did not affect the container security sandbox as the inheritable set never contained more capabilities     than were included in the container's bounding set. This bug has been fixed in runc 1.1.2. This fix     changes `runc exec --cap` behavior such that the additional capabilities granted to the process being     executed (as specified via `--cap` arguments) do not include inheritable capabilities. In addition, `runc     spec` is changed to not set any inheritable capabilities in the created example OCI spec (`config.json`)     file. (CVE-2022-29162)

  - containerd is an open source container runtime. A bug was found in the containerd's CRI implementation     where programs inside a container can cause the containerd daemon to consume memory without bound during     invocation of the `ExecSync` API. This can cause containerd to consume all available memory on the     computer, denying service to other legitimate workloads. Kubernetes and crictl can both be configured to     use containerd's CRI implementation; `ExecSync` may be used when running probes or when executing     processes via an exec facility. This bug has been fixed in containerd 1.6.6 and 1.5.13. Users should     update to these versions to resolve the issue. Users unable to upgrade should ensure that only trusted     images and commands are used. (CVE-2022-31030)

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

The remote Debian 11 host has packages installed that are affected by multiple vulnerabilities as referenced in the dsa-5162 advisory.

  - Moby is an open-source project created by Docker to enable and accelerate software containerization. A bug     was found in Moby (Docker Engine) prior to version 20.10.14 where containers were incorrectly started with     non-empty inheritable Linux process capabilities, creating an atypical Linux environment and enabling     programs with inheritable file capabilities to elevate those capabilities to the permitted set during     `execve(2)`. Normally, when executable programs have specified permitted file capabilities, otherwise     unprivileged users and processes can execute those programs and gain the specified file capabilities up to     the bounding set. Due to this bug, containers which included executable programs with inheritable file     capabilities allowed otherwise unprivileged users and processes to additionally gain these inheritable     file capabilities up to the container's bounding set. Containers which use Linux users and groups to     perform privilege separation inside the container are most directly impacted. This bug did not affect the     container security sandbox as the inheritable set never contained more capabilities than were included in     the container's bounding set. This bug has been fixed in Moby (Docker Engine) 20.10.14. Running containers     should be stopped, deleted, and recreated for the inheritable capabilities to be reset. This fix changes     Moby (Docker Engine) behavior such that containers are started with a more typical Linux environment. As a     workaround, the entry point of a container can be modified to use a utility like `capsh(1)` to drop     inheritable capabilities prior to the primary process starting. (CVE-2022-24769)

  - containerd is an open source container runtime. A bug was found in the containerd's CRI implementation     where programs inside a container can cause the containerd daemon to consume memory without bound during     invocation of the `ExecSync` API. This can cause containerd to consume all available memory on the     computer, denying service to other legitimate workloads. Kubernetes and crictl can both be configured to     use containerd's CRI implementation; `ExecSync` may be used when running probes or when executing     processes via an exec facility. This bug has been fixed in containerd 1.6.6 and 1.5.13. Users should     update to these versions to resolve the issue. Users unable to upgrade should ensure that only trusted     images and commands are used. (CVE-2022-31030)

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

The version of containerd installed on the remote host is prior to 1.4.13-3. It is, therefore, affected by a vulnerability as referenced in the ALAS2NITRO-ENCLAVES-2022-020 advisory.

  - containerd is an open source container runtime. A bug was found in the containerd's CRI implementation     where programs inside a container can cause the containerd daemon to consume memory without bound during     invocation of the `ExecSync` API. This can cause containerd to consume all available memory on the     computer, denying service to other legitimate workloads. Kubernetes and crictl can both be configured to     use containerd's CRI implementation; `ExecSync` may be used when running probes or when executing     processes via an exec facility. This bug has been fixed in containerd 1.6.6 and 1.5.13. Users should     update to these versions to resolve the issue. Users unable to upgrade should ensure that only trusted     images and commands are used. (CVE-2022-31030)

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

The version of containerd installed on the remote host is prior to 1.4.13-3. It is, therefore, affected by a vulnerability as referenced in the ALAS2DOCKER-2022-019 advisory.

  - containerd is an open source container runtime. A bug was found in the containerd's CRI implementation     where programs inside a container can cause the containerd daemon to consume memory without bound during     invocation of the `ExecSync` API. This can cause containerd to consume all available memory on the     computer, denying service to other legitimate workloads. Kubernetes and crictl can both be configured to     use containerd's CRI implementation; `ExecSync` may be used when running probes or when executing     processes via an exec facility. This bug has been fixed in containerd 1.6.6 and 1.5.13. Users should     update to these versions to resolve the issue. Users unable to upgrade should ensure that only trusted     images and commands are used. (CVE-2022-31030)

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

The version of containerd installed on the remote host is prior to 1.4.13-3. It is, therefore, affected by a vulnerability as referenced in the ALAS-2022-1600 advisory.

  - containerd is an open source container runtime. A bug was found in the containerd's CRI implementation     where programs inside a container can cause the containerd daemon to consume memory without bound during     invocation of the `ExecSync` API. This can cause containerd to consume all available memory on the     computer, denying service to other legitimate workloads. Kubernetes and crictl can both be configured to     use containerd's CRI implementation; `ExecSync` may be used when running probes or when executing     processes via an exec facility. This bug has been fixed in containerd 1.6.6 and 1.5.13. Users should     update to these versions to resolve the issue. Users unable to upgrade should ensure that only trusted     images and commands are used. (CVE-2022-31030)

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
203766	Photon OS 3.0: Containerd PHSA-2022-3.0-0402	Nessus	PhotonOS Local Security Checks	medium
203509	Photon OS 4.0: Fuse PHSA-2023-4.0-0429	Nessus	PhotonOS Local Security Checks	critical
203397	Photon OS 4.0: Containerd PHSA-2022-4.0-0195	Nessus	PhotonOS Local Security Checks	medium
189846	GLSA-202401-31 : containerd: Multiple Vulnerabilities	Nessus	Gentoo Local Security Checks	high
183540	Ubuntu 16.04 ESM : containerd vulnerabilities (USN-5521-1)	Nessus	Ubuntu Local Security Checks	high
177029	EulerOS 2.0 SP5 : docker-engine (EulerOS-SA-2023-2142)	Nessus	Huawei Local Security Checks	high
177010	EulerOS 2.0 SP8 : docker-engine (EulerOS-SA-2023-2190)	Nessus	Huawei Local Security Checks	medium
173188	Amazon Linux 2023 : containerd, containerd-stress (ALAS2023-2023-079)	Nessus	Amazon Linux Local Security Checks	high
172218	EulerOS 2.0 SP11 : containerd (EulerOS-SA-2023-1406)	Nessus	Huawei Local Security Checks	medium
172189	EulerOS 2.0 SP11 : containerd (EulerOS-SA-2023-1421)	Nessus	Huawei Local Security Checks	medium
170600	Amazon Linux 2022 : (ALAS2022-2022-210)	Nessus	Amazon Linux Local Security Checks	high
168653	Ubuntu 18.04 LTS / 20.04 LTS / 22.04 LTS : containerd vulnerabilities (USN-5776-1)	Nessus	Ubuntu Local Security Checks	high
166350	Amazon Linux 2022 : (ALAS2022-2022-156)	Nessus	Amazon Linux Local Security Checks	medium
165823	EulerOS 2.0 SP10 : docker-engine (EulerOS-SA-2022-2427)	Nessus	Huawei Local Security Checks	medium
165805	EulerOS 2.0 SP10 : docker-engine (EulerOS-SA-2022-2414)	Nessus	Huawei Local Security Checks	medium
164770	Amazon Linux 2022 : (ALAS2022-2022-088)	Nessus	Amazon Linux Local Security Checks	medium
162999	SUSE SLES15 Security Update : containerd, docker and runc (SUSE-SU-2022:2341-1)	Nessus	SuSE Local Security Checks	high
162517	SUSE SLES12 Security Update : containerd (SUSE-SU-2022:2165-1)	Nessus	SuSE Local Security Checks	high
162143	Debian DSA-5162-1 : containerd - security update	Nessus	Debian Local Security Checks	medium
162012	Amazon Linux 2 : containerd (ALASNITRO-ENCLAVES-2022-020)	Nessus	Amazon Linux Local Security Checks	medium
162011	Amazon Linux 2 : containerd (ALASDOCKER-2022-019)	Nessus	Amazon Linux Local Security Checks	medium
161997	Amazon Linux AMI : containerd (ALAS-2022-1600)	Nessus	Amazon Linux Local Security Checks	medium

Detections

Analytics

CVE-2022-31030

medium

Tenable Plugins

high

medium

critical

medium

high

high

high

medium

high

medium

medium

high

high

medium

medium

medium

medium

high

high

medium

medium

medium

medium