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-0732
Published: 2015-07-28
Cross-site scripting (XSS) vulnerability in Cisco AsyncOS on the Web Security Appliance (WSA) 9.0.0-193; Email Security Appliance (ESA) 8.5.6-113, 9.1.0-032, 9.1.1-000, and 9.6.0-000; and Content Security Management Appliance (SMA) 9.1.0-033 allows remote attackers to inject arbitrary web script or ...

CVE-2015-2974
Published: 2015-07-28
LEMON-S PHP Gazou BBS plus before 2.36 allows remote attackers to upload arbitrary HTML documents via vectors involving a crafted image file.

CVE-2015-4287
Published: 2015-07-28
Cisco Firepower Extensible Operating System 1.1(1.86) on Firepower 9000 devices allows remote attackers to bypass intended access restrictions and obtain sensitive device information by visiting an unspecified web page, aka Bug ID CSCuu82230.

CVE-2015-4288
Published: 2015-07-28
The LDAP implementation on the Cisco Web Security Appliance (WSA) 8.5.0-000, Email Security Appliance (ESA) 8.5.7-042, and Content Security Management Appliance (SMA) 8.3.6-048 does not verify X.509 certificates from SSL servers, which allows man-in-the-middle attackers to spoof servers and obtain s...

CVE-2015-4692
Published: 2015-07-27
The kvm_apic_has_events function in arch/x86/kvm/lapic.h in the Linux kernel through 4.1.3 allows local users to cause a denial of service (NULL pointer dereference and system crash) or possibly have unspecified other impact by leveraging /dev/kvm access for an ioctl call.

Dark Reading Radio
Archived Dark Reading Radio
What’s the future of the venerable firewall? We’ve invited two security industry leaders to make their case: Join us and bring your questions and opinions!