Attacks/Breaches
12/21/2010
02:48 PM
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
Cartoon
Current Issue
Flash Poll
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2015-0714
Published: 2015-05-02
Multiple cross-site scripting (XSS) vulnerabilities in Cisco Finesse Server 10.0(1), 10.5(1), 10.6(1), and 11.0(1) allow remote attackers to inject arbitrary web script or HTML via unspecified parameters, aka Bug ID CSCut53595.

CVE-2014-3598
Published: 2015-05-01
The Jpeg2KImagePlugin plugin in Pillow before 2.5.3 allows remote attackers to cause a denial of service via a crafted image.

CVE-2014-8361
Published: 2015-05-01
The miniigd SOAP service in Realtek SDK allows remote attackers to execute arbitrary code via a crafted NewInternalClient request.

CVE-2015-0237
Published: 2015-05-01
Red Hat Enterprise Virtualization (RHEV) Manager before 3.5.1 ignores the permission to deny snapshot creation during live storage migration between domains, which allows remote authenticated users to cause a denial of service (prevent host start) by creating a long snapshot chain.

CVE-2015-0257
Published: 2015-05-01
Red Hat Enterprise Virtualization (RHEV) Manager before 3.5.1 uses weak permissions on the directories shared by the ovirt-engine-dwhd service and a plugin during service startup, which allows local users to obtain sensitive information by reading files in the directory.

Dark Reading Radio
Archived Dark Reading Radio
Join security and risk expert John Pironti and Dark Reading Editor-in-Chief Tim Wilson for a live online discussion of the sea-changing shift in security strategy and the many ways it is affecting IT and business.