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.

Endpoint

12/17/2010
10:35 AM
50%
50%

Password Diversity Urged In Wake Of Gawker Attack

One of biggest threats is reuse of hacked credentials on other websites

As the fallout continues from the breach at Gawker.com that compromised 1.5 million accounts, authentication experts say the incident is a good warning for Gawker users and everyone else to better manage their passwords across Internet accounts.

According to security professionals, some of the biggest risks posed by this latest breach aren't from sensitive data being gleaned from Gawker data stores, but instead from repeated attacks elsewhere using the same username and password combinations in other sensitive locations.

"As far as value to the attackers, these credentials, as well as the credentials for other systems or intelligence that could lead to a repeat intrusion are the primary target," Seth Hanford, operations team lead for IntelliShield, wrote on the Cisco Security Blog. "Not because Gawker and its related web entities are so valuable, but because human nature remains what it is, and passwords are continually reused from site to site."

The proliferation of social media and Web 2.0 sites with protected content and comment boards requiring a log-in has certainly added more strain to the typical user's memory capacity for passwords. While the first impulse might be to reuse passwords, this can only complicate matters if a single credential is uncovered by bad actors.

Most hackers know how rampant password reuse is and will frequently take lists of credentials they've gleaned from breaches, such as those at Gawker, and cross-reference them against banking and financial website log-in pages.

"People must understand that once you provide a password to any Internet site, you are no longer able to protect it," says Thom VanHorn, vice president of global marketing for AppSec. "Yes, those social networks have a responsibility to implement proper security methodologies that include vulnerability assessment and database activity monitoring, but as an individual you also have a responsibility to use common sense and create complex and secure passwords, and vary your password with each different site."

Security adherents urge Gawker users to not only change their Gawker credentials, but any other credential that shares the same username and password. Because the hackers that stole the Gawker information has published the credentials publicly, any enterprising hacker in search of an easy score can utilize that information elsewhere.

In the future, if coming up with unique passwords for every account you have seems daunting, then consider at least prioritizing when you register.

"As stupid as this suggestion sounds, I have three levels of passwords. For sites where I don't care if my credentials are compromised, I use dumb passwords. For areas of reputation, I use a real unique password, but easy to remember and shared," says Phil Lieberman, president of identity management firm Lieberman Software. "For financial systems, I use different passwords that are strong and not guessable. Consequently, a breach on a social site cannot lead to financial loss using this strategy."

Have a comment on this story? Please click "Discuss" below. If you'd like to contact Dark Reading's editors directly, send us a message.

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Stop Defending Everything
Kevin Kurzawa, Senior Information Security Auditor,  2/12/2020
Small Business Security: 5 Tips on How and Where to Start
Mike Puglia, Chief Strategy Officer at Kaseya,  2/13/2020
5 Common Errors That Allow Attackers to Go Undetected
Matt Middleton-Leal, General Manager and Chief Security Strategist, Netwrix,  2/12/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
6 Emerging Cyber Threats That Enterprises Face in 2020
This Tech Digest gives an in-depth look at six emerging cyber threats that enterprises could face in 2020. Download your copy today!
Flash Poll
How Enterprises Are Developing and Maintaining Secure Applications
How Enterprises Are Developing and Maintaining Secure Applications
The concept of application security is well known, but application security testing and remediation processes remain unbalanced. Most organizations are confident in their approach to AppSec, although others seem to have no approach at all. Read this report to find out more.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-5613
PUBLISHED: 2020-02-18
In FreeBSD 12.0-RELEASE before 12.0-RELEASE-p13, a missing check in the ipsec packet processor allows reinjection of an old packet to be accepted by the ipsec endpoint. Depending on the higher-level protocol in use over ipsec, this could allow an action to be repeated.
CVE-2020-7450
PUBLISHED: 2020-02-18
In FreeBSD 12.1-STABLE before r357213, 12.1-RELEASE before 12.1-RELEASE-p2, 12.0-RELEASE before 12.0-RELEASE-p13, 11.3-STABLE before r357214, and 11.3-RELEASE before 11.3-RELEASE-p6, URL handling in libfetch with URLs containing username and/or password components is vulnerable to a heap buffer over...
CVE-2019-10792
PUBLISHED: 2020-02-18
bodymen before 1.1.1 is vulnerable to Prototype Pollution. The handler function could be tricked into adding or modifying properties of Object.prototype using a __proto__ payload.
CVE-2019-10793
PUBLISHED: 2020-02-18
dot-object before 2.1.3 is vulnerable to Prototype Pollution. The set function could be tricked into adding or modifying properties of Object.prototype using a __proto__ payload.
CVE-2019-10794
PUBLISHED: 2020-02-18
All versions of component-flatten are vulnerable to Prototype Pollution. The a function could be tricked into adding or modifying properties of Object.prototype using a __proto__ payload.