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.

    A bug was found in 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. (CVE-2022-31030)

Tenable has extracted the preceding description block directly from the tested product 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 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.

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

    A bug was found in 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. (CVE-2022-31030)

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

Note that Nessus has not tested for this issue 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)

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.

An update of the fuse package has been released.

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

    A bug was found in 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. (CVE-2022-31030)

    A flaw was found in Moby. This flaw allows an attacker to bypass primary group restrictions due to a flaw     in the supplementary group access setup. (CVE-2022-36109)

Tenable has extracted the preceding description block directly from the tested product 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-210 advisory.

    A bug was found in containerd where containers launched through containerd's CRI implementation 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. (CVE-2022-23648)

    A flaw was found in Moby (Docker Engine), where containers were started incorrectly with non-empty     inheritable Linux process capabilities. This flaw allows an attacker with access to programs with     inheritable file capabilities to elevate those capabilities to the permitted set when execve(2) runs.
    Containers using Linux users and groups to perform privilege separation inside the container are most     directly impacted. (CVE-2022-24769)

    A bug was found in 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. (CVE-2022-31030)

    A flaw was found in Moby. This flaw allows an attacker to bypass primary group restrictions due to a flaw     in the supplementary group access setup. (CVE-2022-36109)

Tenable has extracted the preceding description block directly from the tested product 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 version of containerd installed on the remote host is prior to 1.4.13-3. The version of docker installed on the remote host is prior to 20.10.13-2. The version of ecs-init installed on the remote host is prior to 1.61.1-1. The version of runc installed on the remote host is prior to 1.0.3-3. It is, therefore, affected by multiple vulnerabilities as referenced in the ALAS2ECS-2022-001 advisory.

    A bug was found in containerd where containers launched through containerd's CRI implementation 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. (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)

    A bug was found in 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. (CVE-2022-31030)

Tenable has extracted the preceding description block directly from the tested product 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 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.

An update of the containerd package has been released.

An update of the telegraf package has been released.

ID	名称	产品	系列	发布时间	最近更新时间	严重程度
162012	Amazon Linux 2 : containerd (ALASNITRO-ENCLAVES-2022-020)	Nessus	Amazon Linux Local Security Checks	2022/6/10	2024/12/11	medium
162143	Debian DSA-5162-1 : containerd - security update	Nessus	Debian Local Security Checks	2022/6/13	2022/6/13	medium
164770	Amazon Linux 2022 : containerd, containerd-stress (ALAS2022-2022-088)	Nessus	Amazon Linux Local Security Checks	2022/9/6	2024/12/11	medium
165805	EulerOS 2.0 SP10 : docker-engine (EulerOS-SA-2022-2414)	Nessus	Huawei Local Security Checks	2022/10/8	2025/2/26	medium
203509	Photon OS 4.0: Fuse PHSA-2023-4.0-0429	Nessus	PhotonOS Local Security Checks	2024/7/23	2024/7/23	critical
166350	Amazon Linux 2022 : containerd, containerd-stress (ALAS2022-2022-156)	Nessus	Amazon Linux Local Security Checks	2022/10/20	2024/12/11	medium
170600	Amazon Linux 2022 : containerd, containerd-stress (ALAS2022-2022-210)	Nessus	Amazon Linux Local Security Checks	2023/1/25	2024/12/11	high
178301	Amazon Linux 2 : ecs-init, docker, containerd, runc (ALASECS-2022-001)	Nessus	Amazon Linux Local Security Checks	2023/7/14	2025/4/11	high
189846	GLSA-202401-31 : containerd: Multiple Vulnerabilities	Nessus	Gentoo Local Security Checks	2024/1/31	2024/1/31	high
203397	Photon OS 4.0: Containerd PHSA-2022-4.0-0195	Nessus	PhotonOS Local Security Checks	2024/7/23	2024/7/23	medium
204388	Photon OS 5.0: Telegraf PHSA-2023-5.0-0041	Nessus	PhotonOS Local Security Checks	2024/7/24	2025/8/21	high

检测

插件搜索

medium

medium

medium

medium

critical

medium

high

high

high

medium

high