Apache fixes server proxy flaw

By on
Apache fixes server proxy flaw

Absent forward slash leaves a gaping hole.

The Apache Software Foundation has squashed a reverse proxy flaw affecting its servers in which little more than a missing forward slash had exposed untold numbers of network devices and information to hackers.

Reverse proxies route external HTTP and HTTPS web requests to an internal web server. It is used in load balancing and to make multiple web servers at different paths appear as a single web interface. 

Buggy Apache HTTP Servers in reverse proxy mode that omitted the forward slash could allow attackers to change HTTP requests. From there they could access sensitive resources including administration access for routers, web servers, firewalls and databases.

RewriteRule ^(.*) http://internalserver:80(add forward slash here)$1 [P]

Overnight the Apache Software Foundation patched the flaw discovered last month by UK based Context Information Security during a penetration test.

But Context Information Security research and development manager Michael Jordon said the flaw could affect other web servers.

“This latest vulnerability present is a potential back door to sensitive internal or DMZ systems but is totally avoidable if the reverse proxies are properly configured.

“[We have] not investigated other web servers and proxies but it is reasonable to assume that the problem is more widespread,” he said.

Credit: Context Information Security

"When using the RewriteRule or ProxyPassMatch directives to configure a reverse proxy using a pattern match, it is possible to inadvertently expose internal servers to remote users who send carefully crafted requests,” Apache’s Joe Orton said.

“The server did not validate that the input to the pattern match was a valid path string, so a pattern could expand to an unintended target URL.”

The fix forced Apache software to validate the request URL.

Context Information Security said the vulnerability could be mitigated by changing reverse proxy configurations to ensure that rewrite rules cannot be abused. It released a vulnerability tool to identify the bug.

Adding the forward slash ensures Apache does not interpret the domain and port parts of the request as a username and password, Jordan said.

Remember to sign up to our Security bulletin for the definitive summary and analysis of Infosec threats.

Copyright © SC Magazine, Australia

Tags:
In Partnership With

Most Read Articles

Log In

Username / Email:
Password:
  |  Forgot your password?