The most recent Verizon Data Breach report states:
- Of the 174 million records lost, 100 million (or 58%) were the result of hacktivism against large organizations.
- No losses had been attributed to hacktivism in previous years.
Will 2012 be any different? So far, it seems the answer isn’t just no, but rather “hell no.”
Last year, we described with precision how the first instantiation Lulzsec performed their attacks using common application vulnerabilities such as SQL injection, cross site scripting, directory traversal, remote file inclusion/local file inclusion (RFI/LFI) coupled with DDoS. This year, we detailed how Anonymous attacks using SQL injection, cross site scripting, directory traversal and DDoS. With the “new” Lulzsec announcing operations, the question is: how will they attack? Answer, so far, isn’t different from Lulzsec’s forefathers. One of their first victims? Militarysingles.com, a dating site for military personnel. We cannot know for certain – but with high probability it was by using Local File Inclusion (LFI) / local code upload.
Our first Hacker Intelligence Initiative (HII) report described RFI/LFI and warned it was a favorite exploit among hackers but neglected by the security community. Today, we released another HII report on RFI/LFI to reiterate exactly the same message: RFI/LFI is a favorite among hackers but is neglected by the security community. For more on why RFI/LFI gets no respect, see our explanation here.
But here’s the gist:
The main reason we don't see LFI/RFI in code review is because many website owners/security officers are not necessarily aware of the underlying tech that powers their website. For example, if you install Wordpress, the most popular content management system on the Internet, you get PHP on your server. Not surprisingly, no one is paying attention to PHP code—especially when it comes to code scanning. This is because most organizations who invest in code review technologies (or serious web scanning) are not using PHP for their core application. On the other hand, PHP applications are the most prevalent (in terms of absolute numbers) in the web, hence a strong interest by attackers.
How many of the internet’s websites are written in PHP? Nearly 70 percent.
To make the point again, we've redone our report on RFI/LFI and it can downloaded here. Not coincidentally, hacktivists are using RFI/LFI again. With the rebirth of Lulzsec (we use the term “rebirth” with caution, only time will tell if they’re successful), exactly how was militarysingles.com hacked by Lulzsec II? Here’s how we think the RFI/LFI attack went down…
The web app, a dating site, allows the upload of profile picture, a crucial functionality for a modern dating site. In order to prevent rogue uploads a filter exists to allow only picture files:
This filter has two flaws
- It validates picture format by extension only. For this reason, we can upload a currupted file:
- The filter seems to trust the content type as passed by the browser which is a client side control instead of checking it on server side. So by using a proxy we can change it to be an "image." And our arbitrary file gets uploaded
An attacker could do the same – but change file extension to be php – and therefore executable on victim's machine. We found record of such uploads:
That's the probably the how "LulzSec" attacker has obtained control over the server. The info that was leaked was around 150K user's data that included real names, usernames, e-mail addresses, IP addresses, MD5 hashed passwords, real world addresses (for some users full address) , phone # (some users), birthday (some users).

