CVE-2011-3639

UnknownEPSS 52.53%

Last modified

CVE-2011-3639 is a vulnerability of currently unknown severity. The mod_proxy module in the Apache HTTP Server 2.0.x through 2.0.64 and 2.2.x before 2.2.18, when the Revision 1179239 patch is in place, does not properly interact with use of (1) RewriteRule and (2) ProxyPassMatch pattern matches for configuration of a reverse proxy, which allows remote attackers to send requests to intranet servers by using the HTTP/0.9 protocol with a malformed URI containing an initial @ (at sign) character. NOTE: this vulnerability exists because of an incomplete fix for CVE-2011-3368.. EPSS estimates a 52.53% chance of exploitation in the next 30 days.

Description

The mod_proxy module in the Apache HTTP Server 2.0.x through 2.0.64 and 2.2.x before 2.2.18, when the Revision 1179239 patch is in place, does not properly interact with use of (1) RewriteRule and (2) ProxyPassMatch pattern matches for configuration of a reverse proxy, which allows remote attackers to send requests to intranet servers by using the HTTP/0.9 protocol with a malformed URI containing an initial @ (at sign) character. NOTE: this vulnerability exists because of an incomplete fix for CVE-2011-3368.

Metrics

EPSS Probability
52.53%

98.8th percentile

Probability of exploitation in the next 30 days. Learn more

Weakness Enumeration

Affected Software

VendorProductVersions
ApacheHttp Server2.0.11
ApacheHttp Server2.0.12
ApacheHttp Server2.0.13
ApacheHttp Server2.0.14
ApacheHttp Server2.0.15
ApacheHttp Server2.0.16
ApacheHttp Server2.0.17
ApacheHttp Server2.0.18
ApacheHttp Server2.0.19
ApacheHttp Server2.0.20
ApacheHttp Server2.0.21
ApacheHttp Server2.0.22
ApacheHttp Server2.0.23
ApacheHttp Server2.0.24
ApacheHttp Server2.0.25
ApacheHttp Server2.0.26
ApacheHttp Server2.0.27
ApacheHttp Server2.0.28
ApacheHttp Server2.0.29
ApacheHttp Server2.0.30
ApacheHttp Server2.0.31
ApacheHttp Server2.0.32
ApacheHttp Server2.0.33
ApacheHttp Server2.0.34
ApacheHttp Server2.0.35
ApacheHttp Server2.0.36
ApacheHttp Server2.0.37
ApacheHttp Server2.0.38
ApacheHttp Server2.0.39
ApacheHttp Server2.0.40
ApacheHttp Server2.0.41
ApacheHttp Server2.0.42
ApacheHttp Server2.0.43
ApacheHttp Server2.0.44
ApacheHttp Server2.0.45
ApacheHttp Server2.0.46
ApacheHttp Server2.0.47
ApacheHttp Server2.0.48
ApacheHttp Server2.0.49
ApacheHttp Server2.0.50
ApacheHttp Server2.0.51
ApacheHttp Server2.0.52
ApacheHttp Server2.0.53
ApacheHttp Server2.0.54
ApacheHttp Server2.0.55
ApacheHttp Server2.0.56
ApacheHttp Server2.0.57
ApacheHttp Server2.0.58
ApacheHttp Server2.0.59
ApacheHttp Server2.0.61

Showing 50 of 76 affected configurations. See NVD for the full list.

References

Timeline

Published
Last Modified
Status
Modified

Frequently Asked Questions

What is CVE-2011-3639?
The mod_proxy module in the Apache HTTP Server 2.0.x through 2.0.64 and 2.2.x before 2.2.18, when the Revision 1179239 patch is in place, does not properly interact with use of (1) RewriteRule and (2) ProxyPassMatch pattern matches for configuration of a reverse proxy, which allows remote attackers to send requests to intranet servers by using the HTTP/0.9 protocol with a malformed URI containing an initial @ (at sign) character. NOTE: this vulnerability exists because of an incomplete fix for CVE-2011-3368.
How severe is CVE-2011-3639?
Severity scoring for CVE-2011-3639 is pending analysis. The EPSS model estimates a 52.53% probability of exploitation in the next 30 days.
How do I fix CVE-2011-3639?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

Are you affected by CVE-2011-3639?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST