3 ms·
Since the Q-CERT site is 503ing: http://www.slashgear.com/dropbox-hack-allows-bypass-of-two-factor-authentication-05289228/ http://www.slashgear.com/dropbox-ha
by rdl 13y ago
Since the Q-CERT site is 503ing:
http://www.slashgear.com/dropbox-hack-allows-bypass-of-two-factor-authentication-05289228/ http://www.slashgear.com/dropbox-hack-allows-bypass-of-two-f...
"It turns out that as long as someone has the username and password of your Dropbox account, they can bypass the two-factor authentication and log right into your account with a couple of clever tricks. Since Dropbox doesn’t verify email addresses when users sign up for a new account, a hacker can use a new email address that’s similar to an existing one by placing a period in somewhere, similar to how Gmail addresses work.
For this fake account, two-factor authentication is enabled and an emergency code is generated in case users ever lose their phone. The hacker will then login to the victim’s account, but will be prompted to enter the code for that account. However, the hacker will simply select that the victim lost their phone and they’ll be promoted for that emergency code.
Since the email address that the hacker signed up with is similar to the victim’s email address. the emergency code will work on the victim’s account. From there, the hacker can disable two-factor authentication and gain access into the victim’s Dropbox account. This is because that “baseballboy@yahoo.com” is registered as being the same “baseball.boy@yahoo.com,” just like how Gmail handles email addresses.
Of course, you have to know the user’s password before you can do this, but once you get a hold of it, it seems relatively easy to bypass Dropbox’s two-factor authentication. However, the security team that found the vulnerability is already said to be working with Dropbox to fix the bug."
- MichaelGG 13y agoSo Dropbox has decided ALL email address work like Gmails? That's a pretty dumb-looking decision. I wonder how they came to that conclusion? Intern being clever? Or so commonplace it's actually a usability issue?
- tptacek 13y agoMy money would be on it being an abuse issue.
- 6d0debc071 13y agoI'd guess they reused some code they didn't quite understand.
- jmharvey 13y agoInteresting. It seems like there are two separate issues here: (1) Dropbox is inconsistent about whether it ignores dots in the local part of an email address, and in some cases blurs the line between accounts with similar emails. If true, this needs to be fixed. and (2) Dropbox doesn't really use two-factor authentication, in the usual sense of "something you know plus something you have." I'm guessing this is due to their users liking the idea of having two-factor authentication, but in practice want to be able to access their account even if their phone is lost. So it turns into "something you know plus something you know." I'm inclined to think that this kind of not-really-two-factor-authentication is actually the correct approach for the kind of data you store on Dropbox, but it's something to think about when you're designing an account-recovery protocol.
- parfe 13y agoYour second point isn't correct. The emergency codes are "something you have". You can only generate the codes while logged in, and keep a physical copy separate from your phone. If you lose your phone you pull the paper from your wallet, or get it from a friend or your desk drawer or wherever.
- 6d0debc071 13y agoYou could say the same of a password - which isn't what people traditionally mean by 'something you have,' e.g. some form of security token which is difficult or impossible to reproduce and of which physical possession is a requirement.
- jervisfm 13y agoDropbox is a cloud provider that hosts critical information for many people. Given this nature of their business, I'd expect that security is actually their number one primary focus (even beyond new features I'd say). With regards to point number 1, I don't understand how that bug could have existed uncaught. Yes, security is hard but when you're storing the most personal user data, you're obliged to make sure you actually keep it safe and protect it from unauthorized access. Yet, with Dropbox, it appears that every so often that some time goes by, and we have yet another security issue. The worst I remember was when for a window of time, _anyone_ could login to _any_ dropbox user account without entering a valid password. No password. Just a valid username and you're in. It's interesting to note that issue too had to do with authentication and authorization. Maybe it's time Dropbox should spend some time auditing their code to find other similar issues just waiting to be discovered?