httpd-2.4.56

[Bruce Dubbs]

New point version.

[Bruce Dubbs]

Changes with Apache 2.4.56

• SECURITY: CVE-2023-27522: Apache HTTP Server: mod_proxy_uwsgi HTTP response splitting (cve.mitre.org) HTTP Response Smuggling vulnerability in Apache HTTP Server via mod_proxy_uwsgi. This issue affects Apache HTTP Server: from 2.4.30 through 2.4.55. Special characters in the origin response header can truncate/split the response forwarded to the client.

• SECURITY: CVE-2023-25690: HTTP request splitting with mod_rewrite and mod_proxy (cve.mitre.org) Some mod_proxy configurations on Apache HTTP Server versions 2.4.0 through 2.4.55 allow a HTTP Request Smuggling attack. Configurations are affected when mod_proxy is enabled along with some form of RewriteRule or ProxyPassMatch in which a non-specific pattern matches some portion of the user-supplied request-target (URL) data and is then re-inserted into the proxied request-target using variable substitution. For example, something like:

       RewriteEngine on
       RewriteRule "^/here/(.*)" "
       http://example.com:8080/elsewhere?$1"
       http://example.com:8080/elsewhere ; [P]
       ProxyPassReverse /here/  http://example.com:8080/
       http://example.com:8080/
  

Request splitting/smuggling could result in bypass of access controls in the proxy server, proxying unintended URLs to existing origin servers, and cache poisoning.

• rotatelogs: Add -T flag to allow subsequent rotated logfiles to be truncated without the initial logfile being truncated.

• mod_ldap: LDAPConnectionPoolTTL should accept negative values in order to allow connections of any age to be reused. Up to now, a negative value was handled as an error when parsing the configuration file.

• mod_proxy_ajp: Report an error if the AJP backend sends an invalid number of headers.

• mod_md:
  • Enabling ED25519 support and certificate transparency information when building with libressl v3.5.0 and newer.
  • MDChallengeDns01 can now be configured for individual domains.
  • Fixed a bug that caused the challenge teardown not being invoked as it should.

• mod_http2: client resets of HTTP/2 streams led to unwanted 500 errors reported in access logs and error documents. The processing of the reset was correct, only unneccesary reporting was caused.

• mod_proxy_uwsgi: Stricter backend HTTP response parsing/validation.

[Douglas R. Reno]

CVE-2023-27522

Severity: important

Description:

Some mod_proxy configurations on Apache HTTP Server versions 2.4.0 through 2.4.55 allow 
a HTTP Request Smuggling attack.

Configurations are affected when mod_proxy is enabled along with some form of RewriteRule
 or ProxyPassMatch in which a non-specific pattern matches
 some portion of the user-supplied request-target (URL) data and is then
 re-inserted into the proxied request-target using variable 
substitution. For example, something like:

RewriteEngine on
RewriteRule "^/here/(.*)" " http://example.com:8080/elsewhere?$1" 
http://example.com:8080/elsewhere ; [P]
ProxyPassReverse /here/  http://example.com:8080/ http://example.com:8080/ 


Request splitting/smuggling could result in bypass of access controls in the proxy 
server, proxying unintended URLs to existing origin servers, and cache poisoning.

CVE-2023-27522

Severity: moderate

Description:

HTTP Response Smuggling vulnerability in Apache HTTP Server via mod_proxy_uwsgi. This 
issue affects Apache HTTP Server: from 2.4.30 through 2.4.55.

Special characters in the origin response header can truncate/split the response 
forwarded to the client.

[Douglas R. Reno]

Fixed at c56bd8b60496e88ac2ff4a7afe03120c94fde36d

SA-11.3-002 issued

[Bruce Dubbs]

Milestone renamed