backtop


Print 9 comment(s) - last by Ammohunt.. on Nov 8 at 10:24 PM

Nearly five months of attacks went unnoticed and successful thanks to the MIT domain's strong reputation

Most content-heavy sites on the web today are driven by a mix of PHP and SQL.  Unfortunately, exploits abound from popular PHP database manager frontends like PHPMyAdmin.  Thus, "hacking" many websites has been reduced from an art down to a "brute force" search for applicable SQL vulnerabilities [1][2][3][4] [5][6][7].  And that's just was cybercriminals want.

In this bold new world of SQL injection having a reliable host for your "brute force" attack web-crawler program is essential.  A recent incident involving an infected server at the Massachusetts Institute of Technology shows how *.edu servers may be the perfect vehicle to carry out cybercriminals' attacks.

The MIT server had the perfect profile to carry out attacks.  It had bandwidth aplenty.  And it piggybacked on its school's strong reputation, making its requests automatically appear trusted and less suspicious.

MIT view
MIT's campus [Source: Aisha]

Thus it's not surprising that once a malicious softbot was planted on the MIT server that it was able to wreak havoc on the internet for nearly six months.

The attacking server was identified by Bitdefender, the antimalware arm of Romanian-based software firm Softwin.  It is unknown how the malicious software was planted on the server.  What is clear is what the attacking software has been doing.

The attacking server (CSH-2.MIT.EDU) would locate webpages and initiate a set of SQL injection attempts using GET requests and certain characters troublesome sequences like "//".  An example is seen below in the server logs:

"GET /w00tw00t.at.blackhats.romanian.anti-sec:) HTTP/1.1"
"GET /muieblackcat HTTP/1.1" 404 "GET //scripts/setup.php HTTP/1.1" 301
"GET //admin/scripts/setup.php HTTP/1.1"
"GET //admin/pma/scripts/setup.php HTTP/1.1" 404
"GET //admin/phpmyadmin/scripts/setup.php HTTP/1.1" 404
"GET //db/scripts/setup.php HTTP/1.1" 404

These attempts targeted vulnerabilities in PHPMyAdmin versions 2.5.6 to 2.8.2.  PHPMyAdmin is an open source frontend that is maintained at the popular software repository SourceForge.  It has an impressive 50k+ downloads a week.  The latest version is 3.4.7.

The attacks compromised a reported 100,000+ websites in the five months since the MIT server was compromised in June.  

The script would use injection attempts to deface pages, dumping keywords on them that would elevate their page rank.  It would also dump images from BlogSpot, DeviantART, and Tumblr, among others, on the front-page.  

MIT hacked webpage
Over 100,000 webpages were compromised by the rogue MIT server. [Source: SecurityWeek]

The telltale sign of the compromised pages was a directory  "muieblackcat", which was created on the victims' server space.

For now the attack has been silenced, but it serves as a warning of the growing dangers of SQL injection attacks and the potential of abuse of trusted *.edu servers. SecurityWeek, which wrote a piece on the attacks, suggest implementing anti-injection rewrite rules/conditionals and to rename your PHPMyAdmin script to prevent quick identification from casual attackers.

Sources: SecurityWeek, MalwareCity



Comments     Threshold


This article is over a month old, voting and posting comments is disabled

RE: Could have been avoided...
By kleinma on 11/7/2011 5:13:18 PM , Rating: 2
I agree, but often times it is easier said than done. You never know what is going to break version to version, especially if you are doing anything beyond the stock implementation. So people tend to not upgrade as often because of this. It isn't usually as simply as installing some windows updates with a mouse click.


RE: Could have been avoided...
By jang_clangle on 11/7/2011 8:21:13 PM , Rating: 4
Normally I'd agree, but we're talking about MIT -- we do kind of expect them to be on top of these things.


RE: Could have been avoided...
By Camikazi on 11/7/2011 8:37:39 PM , Rating: 2
You would think they would at the very least see what the new versions fixes and see if it's worth upgrading too. Something like this I would take the risk and upgrade (with a test environment first to make sure not much breaks or to fix ahead of time) rather then leave a hole like that open.


"You can bet that Sony built a long-term business plan about being successful in Japan and that business plan is crumbling." -- Peter Moore, 24 hours before his Microsoft resignation














botimage
Copyright 2014 DailyTech LLC. - RSS Feed | Advertise | About Us | Ethics | FAQ | Terms, Conditions & Privacy Information | Kristopher Kubicki