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 Linux/Unix host has one or more packages installed that are impacted by a vulnerability without a vendor supplied patch available.

  - 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 relies on the presence of the package as reported by the vendor.

There are packages installed that are affected by a vulnerability referenced in the following CVE:

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

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
224989	Linux Distros Unpatched Vulnerability : CVE-2022-41721	Nessus	Misc.	high
414762	SCA: security update for golang.org/x/net (GHSA-fxg5-wq6x-vr4w)	Tenable Cloud Security	SCA Checks	high
414762	SCA: security update for golang.org/x/net (GHSA-fxg5-wq6x-vr4w)	Tenable Self-Hosted Container Security	SCA 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

high