Anonymizing RFI Attacks Through Google
netbuzz writes "Noam Rathaus on his SecuriTeam blog describes a technique by which 'Google can be utilized to hack into websites — actively exploiting them (not information gathering by the use of "Google hacking," although that is how most of the sites vulnerable to RFI attacks are found).' He cites examples in the wild and even mentions that the technique could be used as a 'covert' communications channel."
There is actually quite an interesting aside to this, would someone who used this technique actually be guilty of hacking? Afterall they don't run the exploit and arguably can't guarentee that anyone will.
If I happen to create a utility capable of cracking a site but then store it for research, never distribute and never actively use then I've not committed a crime. If I distribute it to other researchers in good faith then I'm covered - at present its only the person who actively uses it that is guilty of a crime.
However, in this scenario (even if I could be traced) its arguable that *I* never attacked a site, all I did was to place a tool that could be used in that way in a public location. I'm not sure that would completely stand up given the recent ammendment to the UKs computer misuse act (i.e. reasonable belief that the tool would not be used in that fashion), but still...
As always it comes down to people...
PS:
Aas an aside I am currently running a survey for my MSc dissertation on IT admin access to confidential information. If you'd like to help out (and would like a shot at winning a £25 or $40 amazon voucher) then please take a look at:
https://msc-survery.priogenus.com/amazon.php
Aside from triggering the attack, how does this make it anonymous?
Surely the "http://URI-with-malicious-code.php" section will still create logs on the victim server pointing to the source of the malicious code (but perhaps not who triggered it).
biopowered.co.uk - catalytically cracking triglycerides for home automotive use since 2008. Just say no to big oil!
In your server, you can code the logic to take another action if the user agent is a bot.
Here you have a db of web robots.
It's a feature, not a bug.
The Spider of Doom at The Daily WTF.
Make even shorter URLs - 8LN.org
Could someone define the RFI acronym? Neither the summary, article or google can explain it clearly.
If your web application is vulnerable to attack then I would have thought it makes no difference where that attack comes from - be it a 'real' person or a search bot. You should spend more time worrying about whether your application is secure, the how is more important than the who.
sorry... the url above should read:
https://msc-survey.priogenus.com/amazon.php
Remote File Inclusion. It's a pretty poor term for this type of attack, because it's not the act of inclusion that causes the problem, it's the act of requesting the file in the first place.
Bogtha Bogtha Bogtha
Radio Frequency Interference? Request for Information? Radio France Internationale? Rodent Fangs Implementation? WHAT?
How about explaining what such an ambigious acronym actually means initially. As neither TFA nor the summary seems to have done so, I therefore will have do it here, just to make heads and tails of the rest of the discussion and perhaps illuminate someone else. Hit Google, slog through a pile of links indicating one of the above, or some company whose name includes the three letters. There are many of these. On Page 3 I found the Wikipedia page for this TLA, on which there is a dead link to what this must be: Remote File Inclusion.
How about that.
I was wondering if it was just me, that I had been off-line for too long (like 2 days) and missed out on the latest and greatest buzzword, again?
SIGBUS @ NO-07.308
Seriously, I hate to read article like this one. They don't offer any solution.....this kind of attacks are not new at all, you can find tons of such attacks from access.log file/p> tail -f /var/log/httpd/access.log
First get rid of fat apache and use like small and secure lighttpd if you are running a *small personal* web site. Second put lighttpd / Apache in chrooted jail and no one can install *php/perl* shell. I have documented the procedure for putting lighttpd in jail:
http://www.cyberciti.biz/tips/howto-setup-lighttpBoth yahoo and google runs entire webserver in chrooted jail. Other choice is use OpenBSD which runs Apache in chrooted jail out of box.
The important thing is not to stop questioning --Albert Einstein.
Who needs google? There is always that ./ mob willing to click through any url without giving a second thought, no matter how long the way and how worthless its end.
This was done years ago
... The Daily WTF runs on ASPX. These are bold people. Very bold people.
In Soviet Russia, Google Hacks ...
I c-can't do it. *sob*. This is too easy. It's like taking candy from a baby. I'm sorry.
[walks away]
Knowledge is how to play a game, intelligence is how to win, wisdom is knowing what game to play.
While I consider the URL in the article not containing
e quest-Forgeries.html
any news the content of the following URL which is
linked from within the comments was news to me
http://blog.php-security.org/archives/49-Google-R
Check http://www.phrack.org/archives/57/p57-0x13 by Michal Zalewski from 2001
This was described in Zalewski's _Silence On The Wire_.
It's not "HACKING WITH GOOGLE" it's using google to exploit vulnerabilities via the search
In the particular example it's searching in the code where's cmd.gif to use it to enable malicious via remote site.
It's not like using google to hack a specific site but just those who are vulnerable site (it's like searching for which site has phpbb2.6 and to use known exploits to "hack it" [with sql injuction or something).
This discovery is for script kiddies, not for real hackers who wants to hack a specific site (unlike script kiddies that mostly would like to "hack" any site they can, no matter which one, only to show off to their friends or them self in case they don't have any).
Cheers.
Couldn't the gibberish (designed to defeat filters) contained in spam also be a "Covert communications channel"?
I started doing this a few years ago. Check out the link below and view source. I got the data from over a year however it is a few years old. I was studying which engines could be abused in the 'best way'. Short answer, all of them.... http://web.archive.org/web/20030426184220/http://w ww.cgisecurity.com/
Believe me, if I started murdering people, there would be none of you left.
rtfa again - this *is* used for targetting specific sites. Google is used as an anonymiser.
The article suggests searching cmd.gif to demonstrate that that method is being used, and indeed some of the results show that google's index carries urls containing attacks.
To inject those urls into google's index the attacker doesn't even need to run a search or even contact google a single time - he puts the attack (mentioning the specific host the attacker wants to attack) on some webpage and then waits for google to find it and run the attack.
Then, optionally, using google's cache, the attacker could go check the result of his attack.
In other news, vulnerabilities in your application can be exploited not just by the cracker, but also by an agent working for the cracker.
Remember, you heard it here first!
Please correct me if I got my facts wrong.