Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Attacks/Breaches

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
Comments
Newest First  |  Oldest First  |  Threaded View
Data Leak Week: Billions of Sensitive Files Exposed Online
Kelly Jackson Higgins, Executive Editor at Dark Reading,  12/10/2019
Intel Issues Fix for 'Plundervolt' SGX Flaw
Kelly Jackson Higgins, Executive Editor at Dark Reading,  12/11/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
The Year in Security: 2019
This Tech Digest provides a wrap up and overview of the year's top cybersecurity news stories. It was a year of new twists on old threats, with fears of another WannaCry-type worm and of a possible botnet army of Wi-Fi routers. But 2019 also underscored the risk of firmware and trusted security tools harboring dangerous holes that cybercriminals and nation-state hackers could readily abuse. Read more.
Flash Poll
Rethinking Enterprise Data Defense
Rethinking Enterprise Data Defense
Frustrated with recurring intrusions and breaches, cybersecurity professionals are questioning some of the industrys conventional wisdom. Heres a look at what theyre thinking about.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-5252
PUBLISHED: 2019-12-14
There is an improper authentication vulnerability in Huawei smartphones (Y9, Honor 8X, Honor 9 Lite, Honor 9i, Y6 Pro). The applock does not perform a sufficient authentication in a rare condition. Successful exploit could allow the attacker to use the application locked by applock in an instant.
CVE-2019-5235
PUBLISHED: 2019-12-14
Some Huawei smart phones have a null pointer dereference vulnerability. An attacker crafts specific packets and sends to the affected product to exploit this vulnerability. Successful exploitation may cause the affected phone to be abnormal.
CVE-2019-5264
PUBLISHED: 2019-12-13
There is an information disclosure vulnerability in certain Huawei smartphones (Mate 10;Mate 10 Pro;Honor V10;Changxiang 7S;P-smart;Changxiang 8 Plus;Y9 2018;Honor 9 Lite;Honor 9i;Mate 9). The software does not properly handle certain information of applications locked by applock in a rare condition...
CVE-2019-5277
PUBLISHED: 2019-12-13
Huawei CloudUSM-EUA V600R006C10;V600R019C00 have an information leak vulnerability. Due to improper configuration, the attacker may cause information leak by successful exploitation.
CVE-2019-5254
PUBLISHED: 2019-12-13
Certain Huawei products (AP2000;IPS Module;NGFW Module;NIP6300;NIP6600;NIP6800;S5700;SVN5600;SVN5800;SVN5800-C;SeMG9811;Secospace AntiDDoS8000;Secospace USG6300;Secospace USG6500;Secospace USG6600;USG6000V;eSpace U1981) have an out-of-bounds read vulnerability. An attacker who logs in to the board m...