Risk
12/13/2010
01:38 PM
Connect Directly
LinkedIn
Twitter
Google+
RSS
E-Mail
50%
50%

Gawker Media Hacked

The company's user database and content management system have been breached, prompting calls to change passwords.

Gawker Media on Sunday said that its user database had been hacked and encouraged all registered users of the company's Web sites to change their passwords.

Gawker Media's properties include Gawker, Gizmodo, Jalopnik, Jezebel, Kotaku, Lifehacker, Deadspin, io9, and Fleshbot.

Over 1.3 million accounts, with some 540,000 associated e-mail addresses, were exposed and the company's content management system is said to have been compromised as well. The hacked data base file, initially available on The Pirate Bay's Web site, has since been removed. Gawker says that although the passwords were encrypted, they're still potentially vulnerable to hackers.

A group identifying itself as Gnosis has claimed responsibility for the attack. The group says its motivation is to punish Gawker for being arrogant, according to Mediaite.

Someone -- apparently H.D. Moore, creator of the metasploit framework and CSO at Rapid7, whose e-mail address is listed -- has posted a CSV file of the domains of affected e-mail addresses and hashed e-mail address values as a Google Fusion Table. The file includes instructions for how to generate an MD5 hash of one's e-mail address and to search for that value among the posted list of compromised accounts. Finding one's e-mail address on this list means it's definitely time to change your password.

Gawker is also advising users who maintained linked Twitter accounts with the same password to change their passwords at Twitter.

There's currently a Twitter spam campaign that's promoting acai berries through compromised accounts and there's some speculation that Twitter accounts exposed through the Gawker database compromise are being exploited to deliver the tweet spam.

Gawker Media issued an apology for the security failure. "We're deeply embarrassed by this breach," the company said in a statement on its Web site. "We should not be in the position of relying on the goodwill of the hackers who identified the weakness in our systems. And, yes, the irony is not lost on us."

Comment  | 
Print  | 
More Insights
Register for Dark Reading Newsletters
White Papers
Cartoon
Current Issue
Dark Reading Must Reads - September 25, 2014
Dark Reading's new Must Reads is a compendium of our best recent coverage of identity and access management. Learn about access control in the age of HTML5, how to improve authentication, why Active Directory is dead, and more.
Flash Poll
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2012-5485
Published: 2014-09-30
registerConfiglet.py in Plone before 4.2.3 and 4.3 before beta 1 allows remote attackers to execute Python code via unspecified vectors, related to the admin interface.

CVE-2012-5486
Published: 2014-09-30
ZPublisher.HTTPRequest._scrubHeader in Zope 2 before 2.13.19, as used in Plone before 4.3 beta 1, allows remote attackers to inject arbitrary HTTP headers via a linefeed (LF) character.

CVE-2012-5487
Published: 2014-09-30
The sandbox whitelisting function (allowmodule.py) in Plone before 4.2.3 and 4.3 before beta 1 allows remote authenticated users with certain privileges to bypass the Python sandbox restriction and execute arbitrary Python code via vectors related to importing.

CVE-2012-5488
Published: 2014-09-30
python_scripts.py in Plone before 4.2.3 and 4.3 before beta 1 allows remote attackers to execute Python code via a crafted URL, related to createObject.

CVE-2012-5489
Published: 2014-09-30
The App.Undo.UndoSupport.get_request_var_or_attr function in Zope before 2.12.21 and 3.13.x before 2.13.11, as used in Plone before 4.2.3 and 4.3 before beta 1, allows remote authenticated users to gain access to restricted attributes via unspecified vectors.

Best of the Web
Dark Reading Radio
Archived Dark Reading Radio
In our next Dark Reading Radio broadcast, we’ll take a close look at some of the latest research and practices in application security.