Perimeter
6/11/2012
03:57 PM
Amy DeCarlo
Amy DeCarlo
Commentary
Connect Directly
RSS
E-Mail
50%
50%

LinkedIn: Making Insecure Connections

The recent breach of millions of LinkedIn passwords highlights an all-too-common issue

We spend a considerable amount of time in the security industry talking about sophisticated security protections and innovative practices that can be applied to protect critical information. Biometrics, cryptography, secure tokens, and a variety of other technologies can go a long way toward assuring organizations their data is safe. Yet for all the emphasis on innovations in security and safeguarding the highest value data, too often the basics are left uncovered.

The breach of a reported 6.5 million LinkedIn passwords last week is a prime example of what at least initially appears to be a failure at three levels: in policy, in practice, and in communication.

LinkedIn, which doesn’t have a chief information officer, much less a chief information security officer, clearly applied what appears to be a substandard policy to securing passwords of users, many of which may be high-value targets in and of themselves given the power and influence of many of the professionals associated with those access codes. The breach, which was discovered when the passwords showed up on a Russian hacking forum last week, exposed whatever cryptographic controls the social business network used to secure the passwords was far too simplistic.

Communications from LinkedIn about the breach were also unclear. In a blog post written by Vicente Silveira, a director at the company, LinkedIn admitted that “a small subset of the hashed passwords was decoded and published.” It wasn’t able to quantify how many. While the company is investigating the incident, the company’s ambiguity about the breach -- or apparent security expertise or leadership -- is hardly a confidence-inducing move. In the meantime, LinkedIn cancelled the passwords it believed were “at the greatest risk.” Also in a somewhat confusing move, the company says it “is disabling the passwords of any other members that we believe could potentially be affected.”

LinkedIn dug a deeper hole for itself by admitting that it isn’t sure whether any other data was compromised. Nor apparently does the company seem to understand that just because the hackers haven’t apparently been able to crack the cryptographic code for all the passwords that they won’t be able to do so eventually. After all, they have the most important element in their possession already: the passwords themselves.

Most data breaches like the one that befell LinkedIn are too commonplace to make headlines. What distinguished this from the run-of-the-mill password hack attack was the target. Essentially, the breach revealed surprisingly poorly executed security controls by a company that until now has been trusted by millions of professionals to keep them connected.

If anything positive comes of the incident, it is that it serves a reminder to everyone about the importance of being vigilant about managing their own passwords well. Simple tips like resetting passwords frequently and not reusing passwords can go a long way toward protecting their data, and with it, their identities.

Amy DeCarlo is principal analyst for security and data center services at Current Analysis

Amy brings 17 years of IT industry experience to her position as Principal Analyst, Security and Data Center Services. Amy assesses the managed IT services sector, with an emphasis on security and data center solutions delivered through the cloud including on demand ... View Full Bio

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-2013-2595
Published: 2014-08-31
The device-initialization functionality in the MSM camera driver for the Linux kernel 2.6.x and 3.x, as used in Qualcomm Innovation Center (QuIC) Android contributions for MSM devices and other products, enables MSM_CAM_IOCTL_SET_MEM_MAP_INFO ioctl calls for an unrestricted mmap interface, which all...

CVE-2013-2597
Published: 2014-08-31
Stack-based buffer overflow in the acdb_ioctl function in audio_acdb.c in the acdb audio driver for the Linux kernel 2.6.x and 3.x, as used in Qualcomm Innovation Center (QuIC) Android contributions for MSM devices and other products, allows attackers to gain privileges via an application that lever...

CVE-2013-2598
Published: 2014-08-31
app/aboot/aboot.c in the Little Kernel (LK) bootloader, as distributed with Qualcomm Innovation Center (QuIC) Android contributions for MSM devices and other products, allows attackers to overwrite signature-verification code via crafted boot-image load-destination header values that specify memory ...

CVE-2013-2599
Published: 2014-08-31
A certain Qualcomm Innovation Center (QuIC) patch to the NativeDaemonConnector class in services/java/com/android/server/NativeDaemonConnector.java in Code Aurora Forum (CAF) releases of Android 4.1.x through 4.3.x enables debug logging, which allows attackers to obtain sensitive disk-encryption pas...

CVE-2013-6124
Published: 2014-08-31
The Qualcomm Innovation Center (QuIC) init scripts in Code Aurora Forum (CAF) releases of Android 4.1.x through 4.4.x allow local users to modify file metadata via a symlink attack on a file accessed by a (1) chown or (2) chmod command, as demonstrated by changing the permissions of an arbitrary fil...

Best of the Web
Dark Reading Radio
Archived Dark Reading Radio
This episode of Dark Reading Radio looks at infosec security from the big enterprise POV with interviews featuring Ron Plesco, Cyber Investigations, Intelligence & Analytics at KPMG; and Chris Inglis & Chris Bell of Securonix.