Vulnerabilities / Threats
6/21/2011
02:34 PM
Connect Directly
LinkedIn
Twitter
Google+
RSS
E-Mail
50%
50%

Dropbox Files Left Unprotected, Open To All

A software bug rendered the account authentication mechanism non-functional for four hours, leaving customers fuming over the latest security lapse at the popular online file storage service.

Slideshow: Cloud Security Pros And Cons
Slideshow: Cloud Security Pros And Cons
(click image for larger view and for full slideshow)
Dropbox on Monday acknowledged that its vast store of files was left open to the world on Sunday for four hours as a result of a bug. During this period, any account could be accessed using any password.

The flaw, a software bug that rendered the service's authentication mechanism non-functional, only took five minutes to fix, once it was discovered.

Over 25 million customers store their files online with Dropbox, but only a few of those accounts showed activity during the four hour window of vulnerability. "A very small number of users (much less than 1 percent) logged in during that period, some of whom could have logged into an account without the correct password," said Dropbox co-founder and CTO Arash Ferdowsi, in a blog post. "As a precaution, we ended all logged in sessions."

Ferdowsi said that his company is investigating the incident and will notify account holders if any unusual activity is identified during the time when accounts were unprotected. An update to Ferdowsi's blog post indicates that these notifications have been sent out.

The issue was made public by security researcher Christopher Soghoian, who received a tip from a Dropbox user.

In May, Soghoian filed a complaint against Dropbox with the Federal Trade Commission alleging that the company's security claims have been deceptive. Previously, Dropbox had advertised that "All files stored on Dropbox servers are encrypted (AES-256) and are inaccessible without your account password." In April, the company altered its claims to make it clear that Dropbox, rather than the account holder, controls the file encryption keys, thereby enabling Dropbox to provide access to account holders' files when presented with lawful demands from authorities.

In March, the security of Dropbox's Android mobile client came under fire when security researcher Mike Cardwell revealed that the app was transmitting file metadata without SSL encryption.

The following month, Ferdowsi and Drew Houston, co-founder and CEO, explained that they had decided to favor performance over security because "enabling SSL for all metadata transfers made the app several times slower." They also acknowledged Cardwell's concerns and said they were working on a way to send metadata over SSL more efficiently in their mobile apps.

Dropbox's users have made their displeasure about Sunday's incident known in a series of comments appended to Ferdowsi's blog post. Many have said they plan to seek alternative cloud storage services.

As if on cue, Wuala, a competing cloud storage service operated by hard disk maker La Cie, published a blog post on Tuesday stating that Dropbox's problems wouldn't be an issue if files were encrypted by the client. "Encrypting your files before they are sent to the cloud makes Wuala inherently more secure than solutions that rely on server-side encryption," the company said.

It doesn't pay for small and midsize businesses to protect against security threats faced by only the largest companies. Here's how to focus your efforts on the right threats. Download our all-digital supplement. Download it now.

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-2014-6090
Published: 2015-04-27
Multiple cross-site request forgery (CSRF) vulnerabilities in the (1) DataMappingEditorCommands, (2) DatastoreEditorCommands, and (3) IEGEditorCommands servlets in IBM Curam Social Program Management (SPM) 5.2 SP6 before EP6, 6.0 SP2 before EP26, 6.0.3 before 6.0.3.0 iFix8, 6.0.4 before 6.0.4.5 iFix...

CVE-2014-6092
Published: 2015-04-27
IBM Curam Social Program Management (SPM) 5.2 before SP6 EP6, 6.0 SP2 before EP26, 6.0.4 before 6.0.4.6, and 6.0.5 before 6.0.5.6 requires failed-login handling for web-service accounts to have the same lockout policy as for standard user accounts, which makes it easier for remote attackers to cause...

CVE-2015-0113
Published: 2015-04-27
The Jazz help system in IBM Rational Collaborative Lifecycle Management 4.0 through 5.0.2, Rational Quality Manager 4.0 through 4.0.7 and 5.0 through 5.0.2, Rational Team Concert 4.0 through 4.0.7 and 5.0 through 5.0.2, Rational Requirements Composer 4.0 through 4.0.7, Rational DOORS Next Generation...

CVE-2015-0174
Published: 2015-04-27
The SNMP implementation in IBM WebSphere Application Server (WAS) 8.5 before 8.5.5.5 does not properly handle configuration data, which allows remote authenticated users to obtain sensitive information via unspecified vectors.

CVE-2015-0175
Published: 2015-04-27
IBM WebSphere Application Server (WAS) 8.5 Liberty Profile before 8.5.5.5 does not properly implement authData elements, which allows remote authenticated users to gain privileges via unspecified vectors.

Dark Reading Radio
Archived Dark Reading Radio
Join security and risk expert John Pironti and Dark Reading Editor-in-Chief Tim Wilson for a live online discussion of the sea-changing shift in security strategy and the many ways it is affecting IT and business.