The version of containerd installed on the remote host is prior to 1.7.2-1. It is, therefore, affected by multiple vulnerabilities as referenced in the ALAS2NITRO-ENCLAVES-2024-035 advisory.

  - An attacker may cause a denial of service by crafting an Accept-Language header which ParseAcceptLanguage     will take significant time to parse. (CVE-2022-32149)

  - A request smuggling attack is possible when using MaxBytesHandler. When using MaxBytesHandler, the body of     an HTTP request is not fully consumed. When the server attempts to read HTTP2 frames from the connection,     it will instead be reading the body of the HTTP request, which could be attacker-manipulated to represent     arbitrary HTTP2 requests. (CVE-2022-41721)

  - 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 Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

Detections

Analytics

Amazon Linux 2 : containerd (ALASNITRO-ENCLAVES-2024-035)

high Nessus Plugin ID 189477

Version 1.1

Version 1.0

Version 1.1 Jan 25, 2024, 2:43 PM Exploit attributes ("Exploitability ease" changed from "No known exploits are available" to "Exploits are available") Plugin Feed: 202401251443
Version 1.0 Jan 24, 2024, 11:21 PM New Plugin Feed: 202401242321