AntiSec Hacks Signal Same Old, Same Old In Database Insecurity

Hacktivist group takes down two law enforcement associations with ease

News of an AntiSec hack of law enforcement associations on both coasts earlier this week showed that while it might be a new year, we can pretty much expect lots of the same with respect to database security in 2012. The same insecure configurations. The same cleartext storage of passwords and sensitive information in unprotected databases. The same abysmal access control and password management practices. And, of course, the same embarrassing attacks that maybe by the year 3012 will spur organizations to make some changes in the way they approach the basics of database security.
Were just not learning from the successful attacks that keep happening, says Josh Shaul, CTO of Application Security Inc. Its astounding. It seems like almost anywhere Anonymous aims their targets to go out and penetrate, theyre able to break in without any difficulty. It just makes me wonder what happens when people who want to do this for criminal purposes -- more than hacktivist reasons, but to actually steal from organizations -- if it is just as easy for them?
This time around, AntiSec went after the email systems for New York State police chiefs and the website for the California Statewide Law Enforcement Association (CSLEA). The hacktivist group publicly dumped loads of stolen database information from both attacks on New Years Eve.
In the former case, the group dumped a password file with MD5 hashed passwords and residential addresses for more than 300 police chiefs in New York, plus personal information and residential addresses for more than 1,000 more law enforcement personnel. In the latter case, AntiSec completely shut down and defaced CSLEAs website, putting up a snarky missive about its conquest on the site and dumping all of the information stored in its membership roster of 2,500 members, including passwords and credit card numbers stored in cleartext.
In its message, the group said that even as CSLEA administrators sniffed evidence of the breach and made changes to shut down the attacks, it was too little too late.
They finally decided to set a root mysql password, but we got the new one: vanguard, AntiSec wrote. We noticed that you got rid of the credit card table, and most of the users in your database. Still havent figured out how to safely hash passwords though: we really loved your change from ‘redd555 to ‘blu444. Clever.
[Segmenting, hardening, encrypting, insuring, and planning -- a few good New Years resolutions for database administrators. See
7 Housekeeping Duties For Better Database Security In 2012
.]
While the details of exactly how the group broke into CSLEAs database arent clear, Shaul says it is a good bet that the attack built on a SQL injection to first gain access.
Thats their typical M.O. If its not SQL injection, then sometimes it is file-inclusion-type exploits, he says. They like SQL injections because its easy to find, easy to exploit, and it is all over the place.
Jeremy Conway, managing partner at SudoSecure, agrees with Shaul that these attacks are the same old attacks dressed in new clothing. He believes the industry needs to stop looking for fancier technology to stop these types of attacks and get down to the basics of database security.
If youre not implementing the basic stuff right, then youre not going to implement these cool gadgets that everybody is selling. I think we spend way too much money and put way too much confidence on the latest, greatest blinky light thing thats going to tell us when this stuff happens, Conway says. No matter what you throw in front of the database -- you can put a shiny, new object and call it an APT protector or whatever you want to call it -- but it doesnt matter if you dont do the basic stuff.
So in the CSLEA breach, that would mean hashing passwords and working on better segmenting the database information.
Segmentation of the database is probably one of the best things organizations can do, based on what weve seen from penetration-testing organizations in the past, Conway says. Little things like that could go a long way instead of just trying to build that brick wall right up to the database.
Have a comment on this story? Please click Add Your Comment below. If youd like to contact
Dark Readings
editors directly,
send us a message
.

Last News
▸ GFI Software introduces MailSecurity 2011. ◂ Discovered: 05/01/2025 Category: security	▸ Open-source project server hacked, backdoor Trojan found. ◂ Discovered: 05/01/2025 Category: security	▸ Billions of dollars lost due to missing laptops. ◂ Discovered: 05/01/2025 Category: security

**Cyber Security Categories**
Google Dorks Database	Exploits Vulnerability	Exploit Shellcodes

CVE List

Tools/Apps

News/Aarticles

Phishing Database

Deepfake Detection

Trends/Statistics & Live Infos

Tags:
AntiSec Hacks Signal Same Old, Same Old In Database Insecurity