Attacks/Breaches
12/21/2010
02:48 PM
Connect Directly
RSS
E-Mail
50%
50%

Gawker Details Missteps Behind Security Breach

The Gnosis group apparently faced few defenses in what it called a revenge attack on the prominent online media property.

How did Gawker, a leading media property, get hacked, resulting in more than 1.3 million of its users' accounts getting publicly released and uploaded to file-sharing Web sites?

A group known as Gnosis said it came gunning for Gawker, according to Mediaite. "It took us a few hours to find a way to dump all their source code and a bit longer to find a way into their database," said the group.

Apparently, the attackers faced few defenses in what it described as a revenge attack.

An internal memo from Gawker Media CTO Thomas Plunkett to employees suggests as much, tracing the ease of the exploit to Gawker's poor security preparation. "On several fronts -- technically, as well as customer support and communication -- we found ourselves unprepared to handle this eventuality," said Plunkett's memo, which Jim Romenesko reprinted on the Poynter Web site.

According to Plunkett, the attackers exploited a vulnerability in its Web site source code. But Gawker had no processes in place to deal with that scenario and wasn't monitoring for signs of attack.

"The tech team should have been better prepared, committed more time to perform thorough audits, and grown our team's technical expertise to meet our specific business needs," said Plunkett.

Web sites affected by the breach included Gawker, Gizmodo, Jalopnik, Jezebel, Kotaku, Lifehacker, Deadspin, io9, and Fleshbot.

By late last week, Gawker said it had regained control of all systems, including Google Apps. Plunkett said all Web site code had been reviewed for known vulnerabilities, that they had been addressed, and that a more extensive code audit was also underway.

Gawker has also implemented a new security policy, which precludes sharing sensitive information on the company wiki or via chat software. In addition, it enabled SSL for Google Apps, and will require anyone who needs to access sensitive information stored in Google Apps to use two-factor authentication.

Comment  | 
Print  | 
More Insights
Register for Dark Reading Newsletters
White Papers
Flash Poll
Current Issue
Cartoon
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2014-4725
Published: 2014-07-27
The MailPoet Newsletters (wysija-newsletters) plugin before 2.6.7 for WordPress allows remote attackers to bypass authentication and execute arbitrary PHP code by uploading a crafted theme using wp-admin/admin-post.php and accessing the theme in wp-content/uploads/wysija/themes/mailp/.

CVE-2014-4726
Published: 2014-07-27
Unspecified vulnerability in the MailPoet Newsletters (wysija-newsletters) plugin before 2.6.8 for WordPress has unspecified impact and attack vectors.

CVE-2014-2363
Published: 2014-07-26
Morpho Itemiser 3 8.17 has hardcoded administrative credentials, which makes it easier for remote attackers to obtain access via a login request.

CVE-2014-2625
Published: 2014-07-26
Directory traversal vulnerability in the storedNtxFile function in HP Network Virtualization 8.6 (aka Shunra Network Virtualization) allows remote attackers to read arbitrary files via crafted input, aka ZDI-CAN-2023.

CVE-2014-2626
Published: 2014-07-26
Directory traversal vulnerability in the toServerObject function in HP Network Virtualization 8.6 (aka Shunra Network Virtualization) allows remote attackers to create files, and consequently execute arbitrary code, via crafted input, aka ZDI-CAN-2024.

Best of the Web
Dark Reading Radio
Archived Dark Reading Radio
Sara Peters hosts a conversation on Botnets and those who fight them.