RHSA-2022:6753: Moderate: httpd24-httpd security and bug fix update

First published: Thu Sep 29 2022(Updated: )

The httpd packages provide the Apache HTTP Server, a powerful, efficient, and extensible web server.<br>Security Fix(es):<br><li> httpd: mod_sed: Read/write beyond bounds (CVE-2022-23943)</li> <li> httpd: Request splitting via HTTP/2 method injection and mod_proxy (CVE-2021-33193)</li> <li> httpd: NULL pointer dereference via malformed requests (CVE-2021-34798)</li> <li> httpd: mod_proxy_uwsgi: out-of-bounds read via a crafted request uri-path (CVE-2021-36160)</li> <li> httpd: Out-of-bounds write in ap_escape_quotes() via malicious input (CVE-2021-39275)</li> <li> httpd: possible NULL dereference or SSRF in forward proxy configurations (CVE-2021-44224)</li> <li> httpd: mod_lua: Use of uninitialized value of in r:parsebody (CVE-2022-22719)</li> <li> httpd: core: Possible buffer overflow with very large or unlimited LimitXMLRequestBody (CVE-2022-22721)</li> <li> httpd: mod_proxy_ajp: Possible request smuggling (CVE-2022-26377)</li> <li> httpd: mod_lua: DoS in r:parsebody (CVE-2022-29404)</li> <li> httpd: mod_sed: DoS vulnerability (CVE-2022-30522)</li> <li> httpd: mod_proxy: X-Forwarded-For dropped by hop-by-hop mechanism (CVE-2022-31813)</li> <li> httpd: out-of-bounds read via ap_rwrite() (CVE-2022-28614)</li> <li> httpd: out-of-bounds read in ap_strcmp_match() (CVE-2022-28615)</li> <li> httpd: mod_lua: Information disclosure with websockets (CVE-2022-30556)</li> 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.<br>Bug Fix(es):<br><li> proxy rewrite to unix socket fails with CVE-2021-40438 fix (BZ#2022319)</li> Additional changes:<br><li> To fix CVE-2022-29404, the default value for the "LimitRequestBody" directive in the Apache HTTP Server has been changed from 0 (unlimited) to 1 GiB. </li> On systems where the value of "LimitRequestBody" is not explicitly specified in an httpd configuration file, updating the httpd package sets "LimitRequestBody" 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.<br>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 (server, per-directory, per-file, or per-location) and set your preferred limit in bytes. For example, to set a new 2 GiB limit, use:<br>LimitRequestBody 2147483648<br>Systems already configured to use any explicit value for the "LimitRequestBody" directive are unaffected by this change.

Never miss a vulnerability like this again

Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.

Read MoreStart Free Trial

• agent/references
• agent/severity
• agent/type
• agent/softwarecombine
• agent/last-modified-date
• agent/first-publish-date
• agent/weakness
• agent/remedy
• agent/title
• agent/description
• agent/tags
• agent/event
• collector/redhat-errata
• source/Red Hat
• anchor-id/RHSA-2022:6753
• agent/software-canonical-lookup
• package-manager/redhat