Re:Cloudflare Attack Post Mortem; Apparent Google Apps/Gmail...
by eli on Saturday June 02, 2012 @10:20AM
(#4058108)
How is that social engineering? It doesn't seem like human behavior played any role in this at all. The hacker interacted only with automated systems.
This is a security bug that was exploited. It should not be possible to reset a password without the 2-factor auth code, period. If that is possible, then that the 2 factor auth is broken.
Re:Cloudflare Attack Post Mortem; Apparent Google Apps/Gmail...
by danielpal on Saturday June 02, 2012 @08:20PM
(#4059649)
When people say 2-factor auth code is broken, it implies there was an issue with the 2-factor authentication code itself.
That would mean things like RSA and other Token based authentication might be at risk. So no 2-factor auth is not broken. Authentication in Google is broken.
-disclaimer: I am the founder of Authy.com.
Re:Cloudflare Attack Post Mortem; Apparent Google Apps/Gmail...
by eli on Saturday June 02, 2012 @08:46PM
(#4059685)
Well of course the concept of 2-factor auth is still sound. No inherent flaws in the math or the theory. But this particular implementation is quite broken.
Re:Cloudflare Attack Post Mortem; Apparent Google Apps/Gmail...
by Strom on Saturday June 02, 2012 @07:38AM
(#4057846)
It's not misleading. It should not be possible to recover your way past 2-factor auth, which was enabled for the company account.
Re:Cloudflare Attack Post Mortem; Apparent Google Apps/Gmail...
by stephengillie on Saturday June 02, 2012 @07:29AM
(#4057825)
The title of the article doesn't even mention 2-factor: Post Mortem: Today's Attack; Apparent Google Apps/Gmail Vulnerability; and How to Protect Yourself
Don't commingle business and personal accounts.
tl;dr; Hacker used social engineering to add a secondary recovery email address to the victims Google account.
2-factor wasn't even enabled on the victims personal account but the hacker didn't need a 2-factor code to reset the password on the victims company account.
From the article:
Google reports that they discovered a "subtle flaw affecting not 2-step verification itself, but the account recovery flow for some accounts. We've now blocked that attack vector to prevent further abuse."