CVE-2024-47252

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.

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.

Apache HTTP Server is a powerful and flexible HTTP/1.1 compliant web server.

Security Fix(es):

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)

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)

In some mod_ssl configurations on Apache HTTP Server 2.4.35 through to 2.4.63, an access control bypass by trusted clients is possible using TLS 1.3 session resumption.

Configurations are affected when mod_ssl is configured for multiple virtual hosts, with each restricted to a different set of trusted client certificates (for example with a different SSLCACertificateFile/Path setting). In such a case, a client trusted to access one virtual host may be able to access another virtual host, if SSLStrictSNIVHostCheck is not enabled in either virtual host.(CVE-2025-23048)

In some mod_ssl configurations on Apache HTTP Server versions through to 2.4.63, an HTTP desynchronisation attack allows a man-in-the-middle attacker to hijack an HTTP session via a TLS upgrade.

Only configurations using "SSLEngine optional" to enable TLS upgrades are affected. Users are recommended to upgrade to version 2.4.64, which removes support for TLS upgrade.(CVE-2025-49812)

Apache HTTP Server is a powerful and flexible HTTP/1.1 compliant web server.

Security Fix(es):

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)

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)

In some mod_ssl configurations on Apache HTTP Server 2.4.35 through to 2.4.63, an access control bypass by trusted clients is possible using TLS 1.3 session resumption.

Configurations are affected when mod_ssl is configured for multiple virtual hosts, with each restricted to a different set of trusted client certificates (for example with a different SSLCACertificateFile/Path setting). In such a case, a client trusted to access one virtual host may be able to access another virtual host, if SSLStrictSNIVHostCheck is not enabled in either virtual host.(CVE-2025-23048)

In some mod_ssl configurations on Apache HTTP Server versions through to 2.4.63, an HTTP desynchronisation attack allows a man-in-the-middle attacker to hijack an HTTP session via a TLS upgrade.

Only configurations using "SSLEngine optional" to enable TLS upgrades are affected. Users are recommended to upgrade to version 2.4.64, which removes support for TLS upgrade.(CVE-2025-49812)

Apache HTTP Server is a powerful and flexible HTTP/1.1 compliant web server.

Security Fix(es):

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)

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)

In some mod_ssl configurations on Apache HTTP Server 2.4.35 through to 2.4.63, an access control bypass by trusted clients is possible using TLS 1.3 session resumption.

Configurations are affected when mod_ssl is configured for multiple virtual hosts, with each restricted to a different set of trusted client certificates (for example with a different SSLCACertificateFile/Path setting). In such a case, a client trusted to access one virtual host may be able to access another virtual host, if SSLStrictSNIVHostCheck is not enabled in either virtual host.(CVE-2025-23048)

In some mod_ssl configurations on Apache HTTP Server versions through to 2.4.63, an HTTP desynchronisation attack allows a man-in-the-middle attacker to hijack an HTTP session via a TLS upgrade.

Only configurations using "SSLEngine optional" to enable TLS upgrades are affected. Users are recommended to upgrade to version 2.4.64, which removes support for TLS upgrade.(CVE-2025-49812)

Apache HTTP Server is a powerful and flexible HTTP/1.1 compliant web server.

Security Fix(es):

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)

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)

In some mod_ssl configurations on Apache HTTP Server 2.4.35 through to 2.4.63, an access control bypass by trusted clients is possible using TLS 1.3 session resumption.

Configurations are affected when mod_ssl is configured for multiple virtual hosts, with each restricted to a different set of trusted client certificates (for example with a different SSLCACertificateFile/Path setting). In such a case, a client trusted to access one virtual host may be able to access another virtual host, if SSLStrictSNIVHostCheck is not enabled in either virtual host.(CVE-2025-23048)

In some mod_ssl configurations on Apache HTTP Server versions through to 2.4.63, an HTTP desynchronisation attack allows a man-in-the-middle attacker to hijack an HTTP session via a TLS upgrade.

Only configurations using "SSLEngine optional" to enable TLS upgrades are affected. Users are recommended to upgrade to version 2.4.64, which removes support for TLS upgrade.(CVE-2025-49812)

Apache HTTP Server is a powerful and flexible HTTP/1.1 compliant web server.

Security Fix(es):

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)

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)

In some mod_ssl configurations on Apache HTTP Server 2.4.35 through to 2.4.63, an access control bypass by trusted clients is possible using TLS 1.3 session resumption.

Configurations are affected when mod_ssl is configured for multiple virtual hosts, with each restricted to a different set of trusted client certificates (for example with a different SSLCACertificateFile/Path setting). In such a case, a client trusted to access one virtual host may be able to access another virtual host, if SSLStrictSNIVHostCheck is not enabled in either virtual host.(CVE-2025-23048)

In some mod_ssl configurations on Apache HTTP Server versions through to 2.4.63, an HTTP desynchronisation attack allows a man-in-the-middle attacker to hijack an HTTP session via a TLS upgrade.

Only configurations using "SSLEngine optional" to enable TLS upgrades are affected. Users are recommended to upgrade to version 2.4.64, which removes support for TLS upgrade.(CVE-2025-49812)

Apache HTTP Server is a powerful and flexible HTTP/1.1 compliant web server.

Security Fix(es):

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)

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)

In some mod_ssl configurations on Apache HTTP Server 2.4.35 through to 2.4.63, an access control bypass by trusted clients is possible using TLS 1.3 session resumption.

Configurations are affected when mod_ssl is configured for multiple virtual hosts, with each restricted to a different set of trusted client certificates (for example with a different SSLCACertificateFile/Path setting). In such a case, a client trusted to access one virtual host may be able to access another virtual host, if SSLStrictSNIVHostCheck is not enabled in either virtual host.(CVE-2025-23048)

In some mod_ssl configurations on Apache HTTP Server versions through to 2.4.63, an HTTP desynchronisation attack allows a man-in-the-middle attacker to hijack an HTTP session via a TLS upgrade.

Only configurations using "SSLEngine optional" to enable TLS upgrades are affected. Users are recommended to upgrade to version 2.4.64, which removes support for TLS upgrade.(CVE-2025-49812)

The httpd packages provide the Apache HTTP Server, a powerful, efficient, and extensible web server.

Security Fix(es):

• httpd: insufficient escaping of user-supplied data in mod_ssl (CVE-2024-47252)

• httpd: mod_ssl: access control bypass by trusted clients is possible using TLS 1.3 session resumption (CVE-2025-23048)

• httpd: HTTP Session Hijack via a TLS upgrade (CVE-2025-49812)

For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.

The httpd packages provide the Apache HTTP Server, a powerful, efficient, and extensible web server.

Security Fix(es):

• httpd: insufficient escaping of user-supplied data in mod_ssl (CVE-2024-47252)

• httpd: mod_ssl: access control bypass by trusted clients is possible using TLS 1.3 session resumption (CVE-2025-23048)

• httpd: HTTP Session Hijack via a TLS upgrade (CVE-2025-49812)

For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.

The httpd packages provide the Apache HTTP Server, a powerful, efficient, and extensible web server.

Security Fix(es):

• httpd: insufficient escaping of user-supplied data in mod_ssl (CVE-2024-47252)

• httpd: mod_ssl: access control bypass by trusted clients is possible using TLS 1.3 session resumption (CVE-2025-23048)

• httpd: mod_proxy_http2: untrusted input from a client causes an assertion to fail in the Apache mod_proxy_http2 module (CVE-2025-49630)

• httpd: HTTP Session Hijack via a TLS upgrade (CVE-2025-49812)

For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.

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.

The httpd packages provide the Apache HTTP Server, a powerful, efficient, and extensible web server.

Security Fix(es):

• httpd: insufficient escaping of user-supplied data in mod_ssl (CVE-2024-47252)
• httpd: mod_ssl: access control bypass by trusted clients is possible using TLS 1.3 session resumption (CVE-2025-23048)
• httpd: HTTP Session Hijack via a TLS upgrade (CVE-2025-49812)

For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.

The httpd packages provide the Apache HTTP Server, a powerful, efficient, and extensible web server.

Security Fix(es):

• httpd: insufficient escaping of user-supplied data in mod_ssl (CVE-2024-47252)
• httpd: mod_ssl: access control bypass by trusted clients is possible using TLS 1.3 session resumption (CVE-2025-23048)
• httpd: HTTP Session Hijack via a TLS upgrade (CVE-2025-49812)

For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.

The httpd packages provide the Apache HTTP Server, a powerful, efficient, and extensible web server.

Security Fix(es):

• httpd: insufficient escaping of user-supplied data in mod_ssl (CVE-2024-47252)
• httpd: mod_ssl: access control bypass by trusted clients is possible using TLS 1.3 session resumption (CVE-2025-23048)
• httpd: mod_proxy_http2: untrusted input from a client causes an assertion to fail in the Apache mod_proxy_http2 module (CVE-2025-49630)
• httpd: HTTP Session Hijack via a TLS upgrade (CVE-2025-49812)

For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.

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.

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.

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.

• SECURITY UPDATE: insufficient escaping of user-supplied data in logging configurations
  • debian/patches/CVE-2024-47252.patch: Escape ssl vars to prevent potential security vulnerabilities
  • CVE-2024-47252

• CVE-2024-47252: escape user-supplied data in mod_ssl to prevent untrusted SSL/TLS clients from inserting escape characters into log files
• CVE-2025-49812: remove support for TLS upgrade to prevent HTTP desynchronisation attack

• CVE-2024-47252: escape characters are now properly handled in mod_ssl to prevent untrusted SSL/TLS clients from inserting escape characters into log files
• CVE-2025-49812: remove support for TLS upgrade to mitigate HTTP desynchronisation attack

• CVE-2024-47252: escape user-supplied data in mod_ssl to prevent untrusted SSL/TLS clients from inserting escape characters into log files
• CVE-2025-49812: remove support for TLS upgrade to prevent HTTP desynchronisation attack

• CVE-2024-47252: escape user-supplied data in mod_ssl to prevent untrusted SSL/TLS clients from inserting escape characters into log files
• CVE-2025-49812: remove support for TLS upgrade to prevent HTTP desynchronisation attack

• CVE-2024-47252: escape characters are now properly handled in mod_ssl to prevent untrusted SSL/TLS clients from inserting escape characters into log files
• CVE-2025-49812: remove support for TLS upgrade to mitigate HTTP desynchronisation attack

• CVE-2025-49630: fix denial of service attack triggered by untrusted clients causing an assertion in mod_proxy_http2
• CVE-2025-23048: fix access control bypass by trusted clients in mod_ssl configurations
• CVE-2024-47252: escape user-supplied data in mod_ssl to prevent untrusted SSL/TLS clients from inserting escape characters into log file
• CVE-2025-49812: remove support for TLS upgrade to mitigate HTTP desynchronisation attack

• CVE-2025-49630: fix assertion caused by untrusted clients triggering denial of service attack in mod_proxy_http2
• CVE-2025-23048: fix access control bypass by trusted clients using TLS 1.3 session resumption
• CVE-2024-47252: escape user-supplied data to prevent log file injection in mod_ssl
• CVE-2025-49812: remove support for TLS upgrade to prevent HTTP desynchronisation attack

• CVE-2025-49630: fix denial of service attack triggered by untrusted clients causing an assertion in mod_proxy_http2
• CVE-2025-23048: fix access control bypass by trusted clients in mod_ssl configurations
• CVE-2025-49812: remove support for TLS upgrade to mitigate HTTP desynchronisation attack
• CVE-2024-47252: escape user-supplied data in mod_ssl to prevent untrusted SSL/TLS clients from inserting escape characters into log files

• SECURITY UPDATE: query string passed to SSI "#exec cmd" via mod_cgid
  • debian/patches/CVE-2025-58098.patch: in cgid_server() in modules/generators/mod_cgid.c, do not pass the request query string (r->args) to create_argv() for Server Side Includes requests by passing NULL when cgid_req.req_type == SSI_REQ, and add a NULL guard to create_argv() so a shell-escaped query string can no longer be split into extra arguments of an SSI "#exec cmd" command. Backported from httpd commit ecc1b8f3817e3dcab9c1f24f905752d3c0a279af (SVN r1930161).
  • CVE-2025-58098
• SECURITY UPDATE: log injection via unescaped mod_ssl log variables
  • debian/patches/CVE-2024-47252.patch: in ssl_var_log_handler_c() and ssl_var_log_handler_x() in modules/ssl/ssl_engine_vars.c, escape the SSL/TLS variables returned by these mod_ssl log handlers with ap_escape_logitem() so client-supplied values such as SSL_TLS_SNI logged via "%{varname}c"/"%{varname}x" can no longer insert escape characters into log files. Backported from httpd commit c01e60707048be14a510f0a92128a5227923215c (SVN r1927042).
  • CVE-2024-47252

• SECURITY UPDATE: potential SSRF in mod_rewrite via RewriteRule substitutions that produce a scheme-like target
  • debian/patches/CVE-2024-39573.patch: add the previously stripped per-directory prefix, or an implicit '/' root prefix, to the substituted URI before the query args are split in apply_rewrite_rule() in modules/mappers/mod_rewrite.c; otherwise a rule such as "RewriteRule ^/some/path(.*) $1" turns "/some/pathscheme:..." into the fully qualified URL "scheme:...", which mod_proxy then handles. Upstream fix 93aec0e3ca451bcc97f6d91c14d5399d13a73365 (SVN r1918600).
  • CVE-2024-39573
• SECURITY UPDATE: insufficient escaping of mod_ssl variables written to the log by CustomLog
  • debian/patches/CVE-2024-47252.patch: pass the results of ssl_var_log_handler_c() and ssl_var_log_handler_x() through ap_escape_logitem() in modules/ssl/ssl_engine_vars.c, so an untrusted TLS client can no longer insert escape characters into log files through the %{varname}c and %{varname}x formats logging mod_ssl variables such as SSL_TLS_SNI. Upstream fix c01e60707048be14a510f0a92128a5227923215c (SVN r1927042).
  • CVE-2024-47252
• SECURITY UPDATE: access control bypass by trusted clients through TLS 1.3 session resumption in mod_ssl
  • debian/patches/CVE-2025-23048.patch: move the ssl_server_compatible() check in ssl_hook_ReadReq() in modules/ssl/ssl_engine_kernel.c out of the SNI-present branch, so the handshake virtual host and the request virtual host are compared even when the client sent no SNI, as happens on a resumed TLS 1.3 session; previously such a request could reach a virtual host with different client certificate restrictions when SSLStrictSNIVHostCheck was off. Upstream fix c4cfa50c9068e8b8134c530ab21674e77d1278a2 (SVN r1927043).
  • CVE-2025-23048
• SECURITY UPDATE: denial of service through an assertion failure in mod_proxy_http2
  • debian/patches/CVE-2025-49630.patch: fall back to the server hostname when ProxyPreserveHost is on but the incoming request carried no Host: header, in open_stream() in modules/http2/h2_proxy_session.c, instead of passing a NULL authority on to the HTTP/2 backend and tripping an assertion. Upstream fix 88304321841a2fe8bd5eacc70e69418b0b545ca5 (SVN r1927044).
  • CVE-2025-49630
• SECURITY UPDATE: query string passed by mod_cgid to Server Side Includes #exec cmd= commands
  • debian/patches/CVE-2025-58098.patch: pass NULL instead of r->args to create_argv() for SSI_REQ requests in cgid_server(), and tolerate a NULL args in create_argv(), in modules/generators/mod_cgid.c; otherwise the shell-escaped query string is appended as arguments to the command line of an SSI "#exec cmd=..." directive. Upstream fix ecc1b8f3817e3dcab9c1f24f905752d3c0a279af (SVN r1930161).
  • CVE-2025-58098
• SECURITY UPDATE: integer overflow in the mod_md ACME renewal backoff timer
  • debian/patches/CVE-2025-55753.patch: double the retry delay step by step with an overflow and cap check in md_job_delay_on_errors() in modules/md/md_status.c instead of shifting job->min_delay left by err_count-1 in one go; otherwise after roughly 30 days of consecutive renewal failures the shift wraps the signed apr_time_t, the backoff collapses to 0 and the server retries against the ACME CA in a tight loop. Upstream fix 20666cfb765b8ad14efa3d97bc92d344b9395c89 (SVN r1929515).
  • CVE-2025-55753

• rebase to 2.4.6-99.0.9.el7_9.1
• replace the TuxCare backports for CVE-2024-47252, CVE-2025-49812 and CVE-2025-58098 (Patch326-328) with the vendor's own patches (Patch400-402), which carry the identical upstream changes
• all other TuxCare CVE patches are unchanged: Patch300-330 and Patch1000-1014 remain declared and applied

• rebase to 2.4.6-99.0.9.el7_9.1
• replace the TuxCare backports for CVE-2024-47252, CVE-2025-49812 and CVE-2025-58098 (Patch326-328) with the vendor's own patches (Patch400-402), which carry the identical upstream changes
• all other TuxCare CVE patches are unchanged: Patch300-330 and Patch1000-1014 remain declared and applied

• rebase to 2.4.6-99.0.9.el7_9.1
• replace the TuxCare backports for CVE-2024-47252, CVE-2025-49812 and CVE-2025-58098 (Patch326-328) with the vendor's own patches (Patch400-402), which carry the identical upstream changes
• all other TuxCare CVE patches are unchanged: Patch300-330 and Patch1000-1014 remain declared and applied

HTTP response splitting. (CVE-2024-42516) SSRF with mod_headers setting Content-Type header. (CVE-2024-43204) mod_ssl error log variable escaping. (CVE-2024-47252) mod_proxy_http2 denial of service. (CVE-2025-49630) mod_ssl access control bypass with session resumption. (CVE-2025-23048) mod_ssl TLS upgrade attack. (CVE-2025-49812) HTTP/2 DoS by Memory Increase. (CVE-2025-53020) 'RewriteCond expr' always evaluates to true in 2.4.64. (CVE-2025-54090) You will find the update delay sometimes causes a failure; just restart the service after the update.

These are all security issues fixed in the apache2-2.4.64-1.1 package on the GA media of openSUSE Tumbleweed.

This update for apache2 fixes the following issues:

Changes in apache2:

Version update to 2.4.66 (jsc#PED-16181)

*) SECURITY: CVE-2025-66200: Apache HTTP Server: mod_userdir+suexec bypass via AllowOverride FileInfo. mod_userdir+suexec bypass via AllowOverride FileInfo vulnerability in Apache HTTP Server. Users with access to use the RequestHeader directive in htaccess can cause some CGI scripts to run under an unexpected userid. This issue affects Apache HTTP Server: from 2.4.7 through 2.4.65. *) SECURITY: CVE-2025-65082: Apache HTTP Server: CGI environment variable override. Improper Neutralization of Escape, Meta, or Control Sequences vulnerability in Apache HTTP Server through environment variables set via the Apache configuration unexpectedly superseding variables calculated by the server for CGI programs. This issue affects Apache HTTP Server from 2.4.0 through 2.4.65. *) SECURITY: CVE-2025-59775: Apache HTTP Server: NTLM Leakage on Windows through UNC SSRF. Server-Side Request Forgery (SSRF) vulnerability in Apache HTTP Server on Windows with AllowEncodedSlashes On and MergeSlashes Off allows to potentially leak NTLM hashes to a malicious server via SSRF and malicious requests or content *) SECURITY: CVE-2025-58098: Apache HTTP Server: Server Side Includes adds query string to #exec cmd=... Apache HTTP Server 2.4.65 and earlier with Server Side Includes (SSI) enabled and mod_cgid (but not mod_cgi) passes the shell-escaped query string to #exec cmd="..." directives. This issue affects Apache HTTP Server before 2.4.66. *) SECURITY: CVE-2025-55753: Apache HTTP Server: mod_md (ACME), unintended retry intervals An integer overflow in the case of failed ACME certificate renewal leads, after a number of failures (~30 days in default configurations), to the backoff timer becoming 0. Attempts to renew the certificate then are repeated without delays until it succeeds. This issue affects Apache HTTP Server: from 2.4.30 before 2.4.66. *) mod_http2: Fix handling of 304 responses from mod_cache. *) mod_http2/mod_proxy_http2: fix a bug in calculating the log2 value of integers, used in push diaries and proxy window size calculations. *) mod_md: update to version 2.6.5 - New directive MDInitialDelay, controlling how longer to wait after a server restart before checking certificates for renewal. [Michael Kaufmann] - Hardening: when build with OpenSSL older than 1.0.2 or old libressl versions, the parsing of ASN.1 time strings did not do a length check. - Hardening: when reading back OCSP responses stored in the local JSON store, missing 'valid' key led to uninitialized values, resulting in wrong refresh behaviour. *) mod_md: update to version 2.6.6 - Fix a small memory leak when using OpenSSL's BIGNUMs. - Fix reuse of curl easy handles by resetting them. *) mod_http2: update to version 2.0.35 New directive H2MaxStreamErrors to control how much bad behaviour by clients is tolerated before the connection is closed. *) mod_proxy_http2: add support for ProxyErrorOverride directive. *) mpm_common: Add new ListenTCPDeferAccept directive that allows to specify the value set for the TCP_DEFER_ACCEPT socket option on listen sockets. *) mod_ssl: Add SSLVHostSNIPolicy directive to control the virtual host compatibility policy. *) mod_md: update to version 2.6.2 - Fix error retry delay calculation to not already doubling the wait on the first error. *) mod_md: update to version 2.6.1 - Increasing default MDRetryDelay to 30 seconds to generate less bursty traffic on errored renewals for the ACME CA. This leads to error retries of 30s, 1 minute, 2, 4, etc. up to daily attempts. - Checking that configuring MDRetryDelay will result in a…