Breaches show database insecurity is still the norm, despite rash of attacks by hacktivists.
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.
"We're just not learning from the successful attacks that keep happening," said Josh Shaul, CTO of Application Security. "It's astounding. It seems like almost anywhere Anonymous aims their targets to go out and penetrate, they're 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 Year's 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 CSLEA's 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.
In this new Tech Center report, we profile five database breaches--and extract the lessons to be learned from each. Plus: A rundown of six technologies to reduce your risk. Download it here (registration required).
In a digital world inundated with advanced security threats, Intel Security seeks to transform how we live and work to keep our information secure. Through hardware and software development, Intel Security delivers robust solutions that integrate security into every layer of every digital device. In combining the security expertise of McAfee with the innovation, performance, and trust of Intel, this vision becomes a reality.
As we rely on technology to enhance our everyday and business life, we must too consider the security of the intellectual property and confidential data that is housed on these devices. As we increase the number of devices we use, we increase the number of gateways and opportunity for security threats. Intel Security takes the “security connected” approach to ensure that every device is secure, and that all security solutions are seamlessly integrated.
Published: 2014-10-21 Directory traversal vulnerability in functions/suggest.php in Banana Dance B.2.6 and earlier allows remote attackers to include and execute arbitrary local files via a .. (dot dot) in the name parameter in a get_template action.
Published: 2014-10-21 Multiple cross-site scripting (XSS) vulnerabilities in dotProject before 2.1.7 allow remote attackers to inject arbitrary web script or HTML via the (1) callback parameter in a color_selector action, (2) field parameter in a date_format action, or (3) company_name parameter in an addedit action to i...
Published: 2014-10-21 SQL injection vulnerability in xhr.php in InterWorx Web Control Panel (aka InterWorx Hosting Control Panel and InterWorx-CP) before 5.0.14 build 577 allows remote authenticated users to execute arbitrary SQL commands via the i parameter in a search action to the (1) NodeWorx , (2) SiteWorx, or (3) R...