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.

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)

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.7.2-1. It is, therefore, affected by multiple vulnerabilities as referenced in the ALAS2DOCKER-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)

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 Fedora 37 host has a package installed that is affected by a vulnerability as referenced in the FEDORA-2023-4926525509 advisory.

    This update takes caddy from 2.5.2 to 2.6.4. The primary purpose is to resolve CVE-2022-41721. This is a     fairly significant upgrade with lots of new features and fixes, but after reviewing the upstream release     notes I believe it should comply with the Fedora updates policy. The upgrade warnings in the release notes     are described as either backwards compatible, marking a directive as deprecated without removing it, or     changes to features that are marked as experimental.

    - https://github.com/caddyserver/caddy/releases/tag/v2.6.0
    - https://github.com/caddyserver/caddy/releases/tag/v2.6.1
    - https://github.com/caddyserver/caddy/releases/tag/v2.6.2
    - https://github.com/caddyserver/caddy/releases/tag/v2.6.3
    - https://github.com/caddyserver/caddy/releases/tag/v2.6.4

Tenable has extracted the preceding description block directly from the Fedora 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 Fedora 38 host has a package installed that is affected by a vulnerability as referenced in the FEDORA-2023-74e5545901 advisory.

    This update takes caddy from 2.5.2 to 2.6.4.  The primary purpose is to resolve a long standing FTBFS     related to golang 1.20.  The current F38 package is actually a carried-foward F37 build because of that     reason.  It also resolves CVE-2022-41721.  This is a fairly significant upgrade with lots of new features     and fixes, but after reviewing the upstream release notes I believe it should comply with the Fedora     updates policy.  The upgrade warnings in the release notes are described as either backwards compatible,     marking a directive as deprecated without removing it, or changes to features that are marked as     experimental.

    - https://github.com/caddyserver/caddy/releases/tag/v2.6.0
    - https://github.com/caddyserver/caddy/releases/tag/v2.6.1
    - https://github.com/caddyserver/caddy/releases/tag/v2.6.2
    - https://github.com/caddyserver/caddy/releases/tag/v2.6.3
    - https://github.com/caddyserver/caddy/releases/tag/v2.6.4


Tenable has extracted the preceding description block directly from the Fedora 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 version of FreeBSD installed on the remote host is prior to tested version. It is, therefore, affected by a vulnerability as referenced in the 428922c9-b07e-11ed-8700-5404a68ad561 advisory.

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

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
189477	Amazon Linux 2 : containerd (ALASNITRO-ENCLAVES-2024-035)	Nessus	Amazon Linux Local Security Checks	high
189472	Amazon Linux 2 : containerd (ALASDOCKER-2024-035)	Nessus	Amazon Linux Local Security Checks	high
180204	Fedora 37 : caddy (2023-4926525509)	Nessus	Fedora Local Security Checks	high
180201	Fedora 38 : caddy (2023-74e5545901)	Nessus	Fedora Local Security Checks	high
171635	FreeBSD : traefik -- Use of vulnerable Go module x/net/http2 (428922c9-b07e-11ed-8700-5404a68ad561)	Nessus	FreeBSD Local Security Checks	high

Detections

Analytics

CVE-2022-41721

high

Tenable Plugins

high

high

high

high

high