The version of Apache httpd installed on the remote host is prior to 2.4.64. It is, therefore, affected by multiple vulnerabilities as referenced in the 2.4.64 advisory.

  - In certain proxy configurations, a denial of service attack against Apache HTTP Server versions 2.4.26     through to 2.4.63 can be triggered by untrusted clients causing an assertion in mod_proxy_http2.
    Configurations affected are a reverse proxy is configured for an HTTP/2 backend, with ProxyPreserveHost     set to on. (CVE-2025-49630)

  - HTTP response splitting in the core of Apache HTTP Server allows an attacker who can manipulate the     Content-Type response headers of applications hosted or proxied by the server can split the HTTP response.
    This vulnerability was described as CVE-2023-38709 but the patch included in Apache HTTP Server 2.4.59 did     not address the issue. Users are recommended to upgrade to version 2.4.64, which fixes this issue.
    (CVE-2024-42516)

  - SSRF in Apache HTTP Server with mod_proxy loaded allows an attacker to send outbound proxy requests to a     URL controlled by the attacker. Requires an unlikely configuration where mod_headers is configured to     modify the Content-Type request or response header with a value provided in the HTTP request. Users are     recommended to upgrade to version 2.4.64 which fixes this issue. (CVE-2024-43204)

  - Server-Side Request Forgery (SSRF) in Apache HTTP Server on Windows allows to potentially leak NTLM hashes     to a malicious server via mod_rewrite or apache expressions that pass unvalidated request input. This     issue affects Apache HTTP Server: from 2.4.0 through 2.4.63. Note: The Apache HTTP Server Project will be     setting a higher bar for accepting vulnerability reports regarding SSRF via UNC paths. The server offers     limited protection against administrators directing the server to open UNC paths. Windows servers should     limit the hosts they will connect over via SMB based on the nature of NTLM authentication.
    (CVE-2024-43394)

  - Insufficient escaping of user-supplied data in mod_ssl in Apache HTTP Server 2.4.63 and earlier allows an     untrusted SSL/TLS client to insert escape characters into log files in some configurations. In a logging     configuration where CustomLog is used with %{varname}x or %{varname}c to log variables provided by     mod_ssl such as SSL_TLS_SNI, no escaping is performed by either mod_log_config or mod_ssl and unsanitized     data provided by the client may appear in log files. (CVE-2024-47252)

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