RHSA-2022:8067: Moderate: httpd security, bug fix, and enhancement update
The httpd packages provide the Apache HTTP Server, a powerful, efficient, and extensible web server.The following packages have been upgraded to a later upstream version: httpd (2.4.53). (BZ#2079939)Security Fix(es): httpd: mod_sed: Read/write beyond bounds (CVE-2022-23943) httpd: mod_lua: Use of uninitialized value of in r:parsebody (CVE-2022-22719) httpd: core: Possible buffer overflow with very large or unlimited LimitXMLRequestBody (CVE-2022-22721) httpd: mod_proxy_ajp: Possible request smuggling (CVE-2022-26377) httpd: mod_lua: DoS in r:parsebody (CVE-2022-29404) httpd: mod_sed: DoS vulnerability (CVE-2022-30522) httpd: mod_proxy: X-Forwarded-For dropped by hop-by-hop mechanism (CVE-2022-31813) httpd: Out-of-bounds read via ap_rwrite() (CVE-2022-28614) httpd: Out-of-bounds read in ap_strcmp_match() (CVE-2022-28615) httpd: mod_lua: Information disclosure with websockets (CVE-2022-30556) 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.Additional Changes:For detailed information on changes in this release, see the Red Hat Enterprise Linux 9.1 Release Notes linked from the References section.
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of RHSA-2022:8067?
The severity of RHSA-2022:8067 is considered high due to potential vulnerabilities in the Apache HTTP Server affecting the mod_sed module.
How do I fix RHSA-2022:8067?
To fix RHSA-2022:8067, upgrade your httpd packages to version 2.4.53-7.el9 as recommended in the advisory.
What vulnerabilities are addressed in RHSA-2022:8067?
RHSA-2022:8067 addresses vulnerabilities including a read/write beyond bounds issue in the mod_sed module.
Which packages are affected by RHSA-2022:8067?
The affected packages include httpd, httpd-core, httpd-devel, and various related packages in versions prior to 2.4.53-7.el9.
Is there a workaround for RHSA-2022:8067?
While the best solution is to apply the updates, if that's not immediately feasible, consider implementing access controls to limit exposure.