- 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 (1) RewriteRule and (2) 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. <br/><br/> A configuration like one of the following examples: <br/> <br/> <code> RewriteRule (.*)\.(jpg|gif|png) http://images.example.com$1.$2 [P]<br/> ProxyPassMatch (.*)\.(jpg|gif|png) http://images.example.com$1.$2<br/> </code> <br/> could result in an exposure of internal servers. A request of the form: <br/> <br/> <code> GET @other.example.com/something.png HTTP/1.1<br/> </code> <br/> would get translated to a target of:<br/> <br/> <code> http://email@example.com/something.png </code> <br/><br/> This will cause the proxy to connect to the hostname "other.example.com", as the "images.example.com@" segment would be treated as user credentials when parsing the URL. This would allow a remote attacker the ability to proxy to hosts other than those expected, which could be a security exposure in some circumstances.
- Apache HTTPD users should examine their configuration files to determine if they have used an insecure configuration for reverse proxying. Affected users can update their configuration, or apply the patch.<br/><br/> For example, the above RewriteRule could be changed to: <br/> <br/> <code> RewriteRule /(.*)\.(jpg|gif|png) http://images.example.com/$1.$2 [P]<br/> </code> <br/> to ensure the pattern only matches against paths with a leading "/".