{"id":103543,"date":"2022-03-15T09:37:16","date_gmt":"2022-03-15T07:37:16","guid":{"rendered":"https:\/\/prohoster.info\/blog\/novosti-interneta\/reliz-http-servera-apache-2-4-53-s-ustraneniem-opasnyh-uyazvimostej"},"modified":"2022-03-15T09:37:16","modified_gmt":"2022-03-15T07:37:16","slug":"reliz-http-servera-apache-2-4-53-s-ustraneniem-opasnyh-uyazvimostej","status":"publish","type":"post","link":"https:\/\/prohoster.info\/en\/blog\/news\/reliz-http-servera-apache-2-4-53-s-ustraneniem-opasnyh-uyazvimostej","title":{"rendered":"Release of the Apache HTTP Server 2.4.53 addressing critical vulnerabilities","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"
The release of the Apache HTTP server 2.4.53 has been published, featuring 14 changes and fixing 4 vulnerabilities: <\/p>\n
\n
CVE-2022-22720 \u2014 a possibility for an \"HTTP Request Smuggling\" attack, allowing specially crafted client requests to interject into the content of other users' requests transmitted via mod_proxy (for instance, it is possible to inject malicious JavaScript code into another user\u2019s session on the site). The issue is caused by leaving incoming connections open after errors occur while processing an incorrectly formed request body.\n
CVE-2022-23943 \u2014 a buffer overflow in the mod_sed module, allowing the attacker to overwrite heap memory with controlled data.\n
CVE-2022-22721 \u2014 the potential for buffer overflow due to integer overflow occurring when transmitting a request body larger than 350MB. This issue manifests on 32-bit systems where the LimitXMLRequestBody setting is configured too high (default is 1MB; for the attack to succeed, the limit must be above 350MB).\n
CVE-2022-22719 \u2014 a vulnerability in mod_lua that enables the reading of arbitrary memory regions and the crashing of the process when handling specially crafted request bodies. The problem is caused by the use of uninitialized values in the r:parsebody function code. <\/ul>\n
The most notable changes not related to security: <\/p>\n
\n
In mod_proxy, the limit on the number of characters in the handler (worker) name has been increased. Selective timeout settings for backend and frontend have been added (for example, tied to the worker). For requests transmitted via websockets or the CONNECT method, the timeout is now set to the maximum value specified for the backend and frontend.\n
The processing of opening DBM files and loading the DBM driver has been separated. In case of failure, the log now displays more detailed information about the error and the driver.\n