The Best Enterprise Class Cloud Computing Solution
Dark Star Cloud is the only cloud computing solution specifically designed for enterprise class applications. Dark Star Cloud is built on proven robust technology with thousands of customers who cannot tolerate failure or performance limits. Dark Star Cloud also has innovative new technology that drives efficiency, and profits, back into large-scale application development and deployment projects.
For certain departmental and Web 2.0 applications, solutions based on Windows or Linux are fine, but if the application is big, complex or mission critical and you want advantages of enterprise class cloud computing, Dark Star Cloud is the only option. Unique to Dark Star Cloud is the technology to additionally drive 3-10% of a company’s revenue to its bottom line by driving out cost.
Monday, November 28, 2011
The Mainframe Oasis
We are finding day by day that the only secure platform for digital business is the good ol' dusty powerhouse of mainframe computing.
IDG News Service - A yet-to-be-patched flaw discovered in the Apache HTTP server allows attackers to access protected resources on internal networks if some rewrite rules are not defined properly.
The vulnerability affects Apache installations that operate in reverse proxy mode, a type of configuration used for load balancing, caching and other operations that involve the distribution of resources over multiple servers.
In order to set up Apache HTTPD to run as a reverse proxy, server administrators use specialized modules like mod_proxy and mod_rewrite.
Security researchers from Qualys warn that if certain rules are not configured correctly, attackers can trick servers into performing unauthorized requests to access internal resources.
The problem isn't new and a vulnerability that allowed similar attacks was addressed back in October. However, while reviewing the patch for it, Qualys researcher Prutha Parikh realized that it can be bypassed due to a bug in the procedure for URI (Uniform Resource Identifier) scheme stripping. The scheme is the URI part that comes before the colon ":" character, such as http, ftp or file.
One relatively common rewrite and proxying rule is "^(.*) http://internal_host$1", which redirects the request to the machine internal_host. However, if this is used and the server receives, for example, a request for "host::port" (with two colons), the "host:" part is stripped and the rest is appended to http://internal_host in order to forward it internally.
The problem is that in this case, the remaining part is ":port", therefore transforming the forwarded request into http://internal_host:port, an unintended behavior that can result in the exposure of a protected resource.
In order to mitigate the problem server administrators should add a forward slash before $1 in the rewrite rule, the correct form being "^(.*) http://internal_host/$1", Parikh said.
The Apache developers are aware of the problem and are currently discussing the best method of fixing it. One possibility would be to strengthen the previous patch in the server code in order to reject such requests, however, there's no certainty that other bypass methods won't be discovered.
"We could try improve that fix, but I think it would be simpler to change the translate_name hooks in mod_proxy and mod_rewrite to enforce the requirement in the 'right' place," said Red Hat senior software engineer Joe Orton on the Apache dev mailing list. Orton proposed a patch that is currently being reviewed by the other developers.