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-1544
Published: 2014-07-23
Use-after-free vulnerability in the CERT_DestroyCertificate function in libnss3.so in Mozilla Network Security Services (NSS) 3.x, as used in Firefox before 31.0, Firefox ESR 24.x before 24.7, and Thunderbird before 24.7, allows remote attackers to execute arbitrary code via vectors that trigger cer...

CVE-2014-1547
Published: 2014-07-23
Multiple unspecified vulnerabilities in the browser engine in Mozilla Firefox before 31.0, Firefox ESR 24.x before 24.7, and Thunderbird before 24.7 allow remote attackers to cause a denial of service (memory corruption and application crash) or possibly execute arbitrary code via unknown vectors.

CVE-2014-1548
Published: 2014-07-23
Multiple unspecified vulnerabilities in the browser engine in Mozilla Firefox before 31.0 and Thunderbird before 31.0 allow remote attackers to cause a denial of service (memory corruption and application crash) or possibly execute arbitrary code via unknown vectors.

CVE-2014-1549
Published: 2014-07-23
The mozilla::dom::AudioBufferSourceNodeEngine::CopyFromInputBuffer function in Mozilla Firefox before 31.0 and Thunderbird before 31.0 does not properly allocate Web Audio buffer memory, which allows remote attackers to execute arbitrary code or cause a denial of service (buffer overflow and applica...

CVE-2014-1550
Published: 2014-07-23
Use-after-free vulnerability in the MediaInputPort class in Mozilla Firefox before 31.0 and Thunderbird before 31.0 allows remote attackers to execute arbitrary code or cause a denial of service (heap memory corruption) by leveraging incorrect Web Audio control-message ordering.

Best of the Web
Dark Reading Radio
Archived Dark Reading Radio
Where do information security startups come from? More important, how can I tell a good one from a flash in the pan? Learn how to separate ITSec wheat from chaff in this episode.