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).
Published: 2017-05-08 unixsocket.c in lxterminal through 0.3.0 insecurely uses /tmp for a socket file, allowing a local user to cause a denial of service (preventing terminal launch), or possibly have other impact (bypassing terminal access control).
Published: 2017-05-08 A privilege escalation vulnerability in Brocade Fibre Channel SAN products running Brocade Fabric OS (FOS) releases earlier than v7.4.1d and v8.0.1b could allow an authenticated attacker to elevate the privileges of user accounts accessing the system via command line interface. With affected version...
Published: 2017-05-08 Improper checks for unusual or exceptional conditions in Brocade NetIron 05.8.00 and later releases up to and including 06.1.00, when the Management Module is continuously scanned on port 22, may allow attackers to cause a denial of service (crash and reload) of the management module.
Published: 2017-05-08 Nextcloud Server before 11.0.3 is vulnerable to an inadequate escaping leading to a XSS vulnerability in the search module. To be exploitable a user has to write or paste malicious content into the search dialogue.