RHSA-2012:0542: Moderate: httpd security and bug fix update

Published May 7, 2012
·
Updated

The Apache HTTP Server ("httpd") is the namesake project of The ApacheSoftware Foundation.It was discovered that the Apache HTTP Server did not properly validate therequest URI for proxied requests. In certain configurations, if a reverseproxy used the ProxyPassMatch directive, or if it used the RewriteRuledirective with the proxy flag, a remote attacker could make the proxyconnect to an arbitrary server, possibly disclosing sensitive informationfrom internal web servers not directly accessible to the attacker.(CVE-2011-3368)It was discovered that modproxyajp incorrectly returned an "InternalServer Error" response when processing certain malformed HTTP requests,which caused the back-end server to be marked as failed in configurationswhere modproxy was used in load balancer mode. A remote attacker couldcause modproxy to not send requests to back-end AJP (Apache JServProtocol) servers for the retry timeout period or until all back-endservers were marked as failed. (CVE-2011-3348)The httpd server included the full HTTP header line in the default errorpage generated when receiving an excessively long or malformed header.Malicious JavaScript running in the server's domain context could use thisflaw to gain access to httpOnly cookies. (CVE-2012-0053)An integer overflow flaw, leading to a heap-based buffer overflow, wasfound in the way httpd performed substitutions in regular expressions. Anattacker able to set certain httpd settings, such as a user permitted tooverride the httpd configuration for a specific directory using a".htaccess" file, could use this flaw to crash the httpd child process or,possibly, execute arbitrary code with the privileges of the "apache" user.(CVE-2011-3607)A NULL pointer dereference flaw was found in the httpd modlogconfigmodule. In configurations where cookie logging is enabled, a remoteattacker could use this flaw to crash the httpd child process via an HTTPrequest with a malformed Cookie header. (CVE-2012-0021)A flaw was found in the way httpd handled child process status information.A malicious program running with httpd child process privileges (such as aPHP or CGI script) could use this flaw to cause the parent httpd process tocrash during httpd service shutdown. (CVE-2012-0031)Red Hat would like to thank Context Information Security for reporting theCVE-2011-3368 issue.This update also fixes the following bug: The fix for CVE-2011-3192 provided by the RHSA-2011:1329 update introduced a regression in the way httpd handled certain Range HTTP headervalues. This update corrects this regression. (BZ#749071)All users of JBoss Enterprise Web Server 1.0.2 should upgrade to theseupdated packages, which contain backported patches to correct these issues.After installing the updated packages, users must restart the httpdservice for the update to take effect.

Affected Software

14 affected componentsFixes available
redhat/httpd<2.2.17-15.4.ep5.el6
2.2.17-15.4.ep5.el6
redhat/httpd<2.2.17-15.4.ep5.el6
2.2.17-15.4.ep5.el6
redhat/httpd-devel<2.2.17-15.4.ep5.el6
2.2.17-15.4.ep5.el6
redhat/httpd-manual<2.2.17-15.4.ep5.el6
2.2.17-15.4.ep5.el6
redhat/httpd-tools<2.2.17-15.4.ep5.el6
2.2.17-15.4.ep5.el6
redhat/httpd-devel<2.2.17-15.4.ep5.el6
2.2.17-15.4.ep5.el6
redhat/httpd-manual<2.2.17-15.4.ep5.el6
2.2.17-15.4.ep5.el6
redhat/httpd-tools<2.2.17-15.4.ep5.el6
2.2.17-15.4.ep5.el6
redhat/httpd<2.2.17-15.4.ep5.el5
2.2.17-15.4.ep5.el5
redhat/httpd<2.2.17-15.4.ep5.el5
2.2.17-15.4.ep5.el5
redhat/httpd-devel<2.2.17-15.4.ep5.el5
2.2.17-15.4.ep5.el5
redhat/httpd-manual<2.2.17-15.4.ep5.el5
2.2.17-15.4.ep5.el5
redhat/httpd-devel<2.2.17-15.4.ep5.el5
2.2.17-15.4.ep5.el5
redhat/httpd-manual<2.2.17-15.4.ep5.el5
2.2.17-15.4.ep5.el5

Remediation

Event History

May 7, 2012
Advisory Published
12:00 AM

Frequently Asked Questions

1

What is the severity of RHSA-2012:0542?

The severity of RHSA-2012:0542 is classified as critical due to potential security risks associated with improper request URI validation.

2

How do I fix RHSA-2012:0542?

To fix RHSA-2012:0542, update your Apache HTTP Server to version 2.2.17-15.4.ep5.el6 or later.

3

Which versions of Apache are affected by RHSA-2012:0542?

RHSA-2012:0542 affects Apache HTTP Server version 2.2.17 and earlier.

4

Is there a workaround for RHSA-2012:0542?

A temporary workaround for RHSA-2012:0542 is to disable the use of ProxyPassMatch in your Apache configuration.

5

What packages are impacted by RHSA-2012:0542?

RHSA-2012:0542 impacts the httpd, httpd-devel, httpd-manual, and httpd-tools packages.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203