Contents
- Vital information on this issue
- Scanning For and Finding Vulnerabilities in Apache Running Version Prior to 2.2.22
- Penetration Testing (Pentest) for this Vulnerability
- Security updates on Vulnerabilities in Apache Running Version Prior to 2.2.22
- Disclosures related to Vulnerabilities in Apache Running Version Prior to 2.2.22
- Confirming the Presence of Vulnerabilities in Apache Running Version Prior to 2.2.22
- False positive/negatives
- Patching/Repairing this vulnerability
- Exploits related to Vulnerabilities in Apache Running Version Prior to 2.2.22
Vital Information on This Issue
Vulnerabilities in Apache Running Version Prior to 2.2.22 is a Medium risk vulnerability that is one of the most frequently found on networks around the world. This issue has been around since at least 1990 but has proven either difficult to detect, difficult to resolve or prone to being overlooked entirely.
| Vulnerability Name: | Apache Running Version Prior to 2.2.22 |
| Test ID: | 14402 |
| Risk: | Medium |
| Category: | Web Servers |
| Type: | Attack |
| Summary: | Multiple vulnerabilities have been found in Apache: * The mod_proxy module in the Apache HTTP Server 1.3.x through 1.3.42, 2.0.x through 2.0.64, and 2.2.x through 2.2.21 does not properly interact with use of RewriteRule and ProxyPassMatch pattern matches for configuration of a reverse proxy, which allows remote attackers to send requests to intranet servers via a malformed URI containing an initial @ (at sign) character. * Integer overflow in the ap_pregsub function in server/util.c in the Apache HTTP Server 2.0.x through 2.0.64 and 2.2.x through 2.2.21, when the mod_setenvif module is enabled, allows local users to gain privileges via a .htaccess file with a crafted SetEnvIf directive, in conjunction with a crafted HTTP request header, leading to a heap-based buffer overflow. * The mod_proxy module in the Apache HTTP Server 1.3.x through 1.3.42, 2.0.x through 2.0.64, and 2.2.x through 2.2.21, when the Revision 1179239 patch is in place, does not properly interact with use of RewriteRule and ProxyPassMatch pattern matches for configuration of a reverse proxy, which allows remote attackers to send requests to intranet servers via a malformed URI containing an @ (at sign) character and a : (colon) character in invalid positions. NOTE: this vulnerability exists because of an incomplete fix for CVE-2011-3368. * The log_cookie function in mod_log_config.c in the mod_log_config module in the Apache HTTP Server 2.2.17 through 2.2.21, when a threaded MPM is used, does not properly handle a %{}C format string, which allows remote attackers to cause a denial of service (daemon crash) via a cookie that lacks both a name and a value. * scoreboard.c in the Apache HTTP Server 2.2.21 and earlier might allow local users to cause a denial of service (daemon crash during shutdown) or possibly have unspecified other impact by modifying a certain type field within a scoreboard shared memory segment, leading to an invalid call to the free function. * protocol.c in the Apache HTTP Server 2.2.x through 2.2.21 does not properly restrict header information during construction of Bad Request (aka 400) error documents, which allows remote attackers to obtain the values of HTTPOnly cookies via vectors involving a long or malformed header in conjunction with crafted web script. $OUTPUT |
| Impact: | Allows remote attackers to cause a denial of service (daemon crash) via a cookie that lacks both a name and a value. |
| Solution: | Upgrade to Apache version 2.2.22 or newer. |
| CVE: | CVE-2011-3368 CVE-2011-3607 CVE-2011-3639 CVE-2011-4317 CVE-2011-4415 CVE-2012-0021 CVE-2012-0031 CVE-2012-0053 |
| More Information: | http://httpd.apache.org/security/vulnerabilities_22.htm |
| Nist NVD (CVSS): | AV:N/AC:L/Au:N/C:P/I:N/A:N |
| CVSS Score: | 5.0 |
Scanning For and Finding Vulnerabilities in Apache Running Version Prior to 2.2.22
Use of Vulnerability Management tools, like AVDS, are standard practice for the discovery of this vulnerability. The primary failure of VA in finding this vulnerability is related to setting the proper scope and frequency of network scans. It is vital that the broadest range of hosts (active IPs) possible are scanned and that scanning is done frequently. We recommend weekly. Your existing scanning solution or set of test tools should make this not just possible, but easy and affordable. If that is not the case, please consider AVDS.
Penetration Testing (pentest) for this Vulnerability
The Vulnerabilities in Apache Running Version Prior to 2.2.22 is prone to false positive reports by most vulnerability assessment solutions. AVDS is alone in using behavior based testing that eliminates this issue. For all other VA tools security consultants will recommend confirmation by direct observation. In any case Penetration testing procedures for discovery of Vulnerabilities in Apache Running Version Prior to 2.2.22 produces the highest discovery accuracy rate, but the infrequency of this expensive form of testing degrades its value. The ideal would be to have pentesting accuracy and the frequency and scope possibilities of VA solutions, and this is accomplished only by AVDS.
Security Updates on Vulnerabilities in Apache Running Version Prior to 2.2.22
Given that this is one of the most frequently found vulnerabilities, there is ample information regarding mitigation online and very good reason to get it fixed. Hackers are also aware that this is a frequently found vulnerability and so its discovery and repair is that much more important. It is so well known and common that any network that has it present and unmitigated indicates “low hanging fruit” to attackers.
Disclosures related to this vulnerability
Confirming the Presence of Vulnerabilities in Apache Running Version Prior to 2.2.22
AVDS is currently testing for and finding this vulnerability with zero false positives. If your current set of tools is indicating that it is present but you think it is probably a false positive, please contact us for a demonstration of AVDS.
False positive/negatives
The secret killer of VA solution value is the false positive. There was an industry wide race to find the most vulnerabilities, including Vulnerabilities in Apache Running Version Prior to 2.2.22 ,and this resulted in benefit to poorly written tests that beef up scan reports by adding a high percentage of uncertainty. This may have sold a lot of systems some years ago, but it also stuck almost all VA solutions with deliberately inaccurate reporting that adds time to repairs that no administrator can afford. Beyond Security did not participate in this race to mutually assured destruction of the industry and to this day produces the most accurate and actionable reports available.
Patching/Repairing this Vulnerability
Vulnerabilities in Apache Running Version Prior to 2.2.22 is a Medium risk vulnerability that is also high frequency and high visibility. This is the most severe combination of security factors that exists and it is extremely important to find it on your network and fix it as soon as possible.
Exploits related to Vulnerabilities in Apache Running Version Prior to 2.2.22
https://beyndsecurty.wpengine.com/scan_pentest_network_vulnerabilities_apache_running_version_prior_2_2_28
http://www.cvedetails.com/vulnerability-list.php?product_id=66&cvssscoremin=5&cvssscoremax=5.99
https://httpd.apache.org/security/vulnerabilities_24.html