A new reverse proxy issue affecting Apache HTTP server can be used by attackers to access internal systems if certain rules are improperly configured, a security researcher said. . Prutha Parikh, vulnerability signature engineer at Qualys, blogged that she uncovered the issue while creating a QualysGuard vulnerability signature for another reverse proxy issue, detailed in CVE-2011-3368. While reviewing the patch for the older bug, she discovered it was still possible to use a crafted request to exploit a fully-patched Apache Web Server. The link for this article located at ThreatPost is no longer available. . An recently identified Nginx reverse proxy vulnerability may result in unauthorized internal network exposure owing to setup errors.. Apache Reverse Proxy, Misconfiguration Risks, Internal Access Threats. . LinuxSecurity.com Team
Maintainers of the open-source Apache webserver are warning that their HTTP daemon is vulnerable to exploits that expose internal servers to remote attackers who embed special commands in website addresses.. The weakness in 1.3 and all 2.x versions of the Apache HTTP Server can be exploited only under certain conditions. For one, they must be running in reverse proxy mode, a setting often used to perform load balancing or to separate static content from dynamic content. And even then, internal systems are susceptible to unauthorized access only when certain types of reverse proxy rewrite rules are used. Nonetheless, the vulnerable reverse proxy configurations are common enough that Apache maintainers issued an advisory on Wednesday recommending users examine their systems to make sure they're not at risk. The link for this article located at The Register UK is no longer available. . The weakness in 1.3 and all 2.x versions of the Apache HTTP Server can be exploited only under certa. maintainers, open-source, apache, webserver, warning, their, daemon, vulnerable. . LinuxSecurity.com Team
Apache releases security advisory following discovery of back door threat by researchers at Context Information Security. October 6th 2011 - The Apache Software Foundation yesterday issued an advisory to all of its customers following the identification by researchers at UK-based Context Information Security of a new class of security vulnerability that could allow hackers to gain full internet access to internal or DMZ systems using insecurely configured reverse web proxies. Context alerted Apache to the weakness last month and has today published a blog detailing this new class of attack that it believes is likely to affect other web servers and proxies. The blog also provides advice to mitigate the risks: https://www.accenture.com/us-en Reverse proxies are used to route external HTTP and HTTPS web requests to one of several internal web servers to access data and resources. Typical applications include load balancing, separating static from dynamic content, or to present a single interface to a number of different web servers at different paths. While other proxies may suffer from the same vulnerability, the specific attack identified by Context researchers was based on an Apache web server using the mod_rewrite proxy function, which uses a rule-based rewriting engine to modify and rewrite web requests dynamically. When the web proxies had not been configured securely, Context was able to use an easy-to-obtain hacking tool in order to force a change in the request to access internal or DMZ systems, including administration interfaces on firewalls, routers, web servers and databases. And if credentials on internal systems were weak, a full network compromise was possible including uploading Trojan WAR files to a server. The vulnerability can easily be mitigated by checking reverse proxy configurations to ensure that the rewrite rules cannot be abused to allow for the URLs to be rewritten in such a way that they can access internal systems. Context has also released the latest version of itsfree to download Context Application Tool (CAT) designed to deliver manual web application penetration testing that can be used to identify the vulnerability. The difference between the two rules can be as simple as adding an extra slash, which ensures that Apache does not interpret the domain and port parts of the request as a username and password. For example, if the Apache configuration file is configured like this: RewriteRule ^(.*) [P], and not like this: RewriteRule ^(.*) [P], then access from the internet to any internal system is possible. In its advisory to customers, Apache recommends that Apache HTTPD users should examine their configuration files to determine if they have used an insecure configuration for reverse proxying. The full Apache response can be viewed at Full Disclosure: Apache HTTP Server: mod_proxy reverse proxy exposure (CVE-2011-3368) "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," said Michael Jordon, Research and Development Manger at Context Information Security. "We have not investigated other web servers and proxies but it is reasonable to assume that the problem is more widespread." Full details of the reverse proxy bypass vulnerability with link to download the free Context Application Tool are published on the Context web site at https://www.accenture.com/gb-en/services/cybersecurity About Context Context Information Security is an independent security consultancy specialising in both technical security and information assurance services. Founded in 1998, the company. Apache has published a security notice regarding a vulnerability related to reverse proxy bypass, which was uncovered by Context Information Security.. Apache Security, Reverse Proxy Threat, Configuration Issues, Web Server Security. . Anthony Pell
The Web Security Gateway is a security-centric distribution of the Apache web server, bundled with additional security modules, and configured as a front-end (reverse) HTTP proxy. The goal is to mirror most of the features of commercial web application . The link for this article located at Darknet.org is no longer available. . The Web Security Gateway for Apache enhances web application security with access control, SSL/TLS termination, real-time monitoring, and logging features.. Web Security Gateway, Apache Security, Secure Proxy Solutions, Application Safety, Open Source Security. . LinuxSecurity.com Team
As more and more attacks are being carried out over the HTTP layer there is a growing need to push the envelope and bring Web security to new levels. Most existing tools work on the TCP/IP level, failing to use the . . . . As more and more attacks are being carried out over the HTTP layer there is a growing need to push the envelope and bring Web security to new levels. Most existing tools work on the TCP/IP level, failing to use the specifics of the HTTP protocol in their operation. The need for increased security has lead to the creation of application gateways, tools that are essentially reverse proxies with the added capability of protocol analysis. Many commercial solutions are available. This article will demonstrate how you can build your own application gateway with little effort, using open source components that are widely available. Our task is to protect one or more Web servers residing on an internal network, providing services to outside clients. Internal clients, such as employees are also considered to be outside clients for the purpose of this article. We are working under the assumption that you have at least two or more Web servers, a database server, and possibly other internal servers. The more servers there are, the more useful the reverse proxy concept becomes. A proxy, by definition, is a device that stands between two entities participating in a conversation. What is normally called a proxy in everyday life is better described as a forward proxy: a device that stands between a client and all other servers. A reverse proxy does exactly the opposite: it stands between a server and all its clients. In a wider sense, one reverse proxy will be used for all internal Web servers. The link for this article located at SecurityFocus is no longer available. . As more and more attacks are being carried out over the HTTP layer there is a growing need to push t. attacks, being, carried, layer, there, growing. . LinuxSecurity.com Team
Get the latest Linux and open source security news straight to your inbox.