The httpd packages provide the Apache HTTP Server, a powerful, efficient, and extensible web server. Security Fix: * httpd: mod_sed: Read/write beyond bounds * httpd: Request splitting via HTTP/2 method injection and mod_proxy * httpd: NULL pointer dereference via malformed requests * httpd: mod_proxy_uwsgi: out-of-bounds read via a crafted request uri-path * httpd: Out-of-bounds write in ap_escape_quotes via malicious input * httpd: possible NULL dereference or SSRF in forward proxy configurations * httpd: mod_lua: Use of uninitialized value of in r:parsebody * httpd: core: Possible buffer overflow with very large or unlimited LimitXMLRequestBody * httpd: mod_proxy_ajp: Possible request smuggling * httpd: mod_lua: DoS in r:parsebody * httpd: mod_sed: DoS vulnerability * httpd: mod_proxy: X-Forwarded-For dropped by hop-by-hop mechanism * httpd: out-of-bounds read via ap_rwrite * httpd: out-of-bounds read in ap_strcmp_match * httpd: mod_lua: Information disclosure with websockets For more details about the security issue, including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page listed in the References section. Bug Fix: * proxy rewrite to unix socket fails with CVE-2021-40438 fix Additional changes: * To fix CVE-2022-29404, the default value for the quot;LimitRequestBodyquot; directive in the Apache HTTP Server has been changed from 0 to 1 GiB. On systems where the value of quot;LimitRequestBodyquot; is not explicitly specified in an httpd configuration file, updating the httpd package sets quot;LimitRequestBodyquot; to the default value of 1 GiB. As a consequence, if the total size of the HTTP request body exceeds this 1 GiB default limit, httpd returns the 413 Request Entity Too Large error code. If the new default allowed size of an HTTP request message body is insufficient for your use case, update your httpd configuration files within the respective context and set your preferred limit in bytes. For example, to set a new 2 GiB limit, use: LimitRequestBody 2147483648 Systems already configured to use any explicit value for the quot;LimitRequestBodyquot; directive are unaffected by this change.