RHSA-2010:0175: Low: httpd security, bug fix, and enhancement update
The Apache HTTP Server is a popular web server.A use-after-free flaw was discovered in the way the Apache HTTP Serverhandled request headers in subrequests. In configurations where subrequestsare used, a multithreaded MPM (Multi-Processing Module) could possibly leakinformation from other requests in request replies. (CVE-2010-0434)This update also fixes the following bug: a bug was found in the moddav module. If a PUT request for an existing file failed, that file would be unexpectedly deleted and a "Could not getnext bucket brigade" error logged. With this update, failed PUT requests nolonger cause moddav to delete files, which resolves this issue.(BZ#572932)As well, this update adds the following enhancement: with the updated openssl packages from RHSA-2010:0163 installed, modssl will refuse to renegotiate a TLS/SSL connection with an unpatched clientthat does not support RFC 5746. This update adds the"SSLInsecureRenegotiation" configuration directive. If this directive isenabled, modssl will renegotiate insecurely with unpatched clients.(BZ#575805)Refer to the following Red Hat Knowledgebase article for more details aboutthe changed modssl behavior: http://kbase.redhat.com/faq/docs/DOC-20491 All httpd users should upgrade to these updated packages, which containbackported patches to correct these issues and add this enhancement. Afterinstalling the updated packages, the httpd daemon must be restarted for theupdate to take effect.
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of RHSA-2010:0175?
The severity of RHSA-2010:0175 is classified as moderate due to the potential for data leaks in specific configurations of the Apache HTTP Server.
How do I fix RHSA-2010:0175?
To fix RHSA-2010:0175, you should update your Apache HTTP Server to the latest version that addresses this use-after-free vulnerability.
What is the vulnerability type of RHSA-2010:0175?
The vulnerability type of RHSA-2010:0175 is a use-after-free flaw in the handling of request headers.
Which versions of Apache HTTP Server are affected by RHSA-2010:0175?
RHSA-2010:0175 affects specific versions of the Apache HTTP Server that utilize multithreaded MPM configurations.
What potential impact could RHSA-2010:0175 have on my system?
The potential impact of RHSA-2010:0175 includes data leaks and possible exposure of sensitive information during subrequest handling.