Attacks/Breaches
8/7/2013
11:20 AM
50%
50%

Twitter Overhauls Two Factor Authentication System

Take two: Twitter drops SMS for private keys stored on Android or iPhone smartphones, adds previously missing recovery capability.

Smolen said the move to an SMS-free system defends against the potential that the server being used to generate one-time codes might be compromised. "We chose a design that is resilient to a compromise of the server-side data's confidentiality: Twitter doesn't persistently store secrets, and the private key material needed for approving login requests never leaves your phone," he said.

The approach also sidesteps the problem of smartphones being infected by malware that could intercept one-time SMS codes. That capability already has been seen with Android malware that's designed to intercept mobile transaction authorization numbers (mTANs) -- one-time codes -- sent by some banks to customers before approving a high-value transaction request.

"No malware that I know of has gone after non-bank SMS codes. But to do so would be extremely trivial for such malware," said Sean Sullivan, security advisor at F-Secure Labs, via email, who called Twitter's SMS-free approach "a useful feature."

Referring to the Syrian Electronic Army (SEA), Sullivan added, "The SEA kind of cooled off, at least on Twitter -- if not Channel 4 -- but there will definitely be attempts on high-profile accounts in the future."

Twitter first began offering two-factor authentication in May, following a number of embarrassing high-profile takeovers of Twitter accounts by the likes of the SEA. Those takeovers included a hoax post via the Associated Press (AP) account about a bomb at the White House that lead to a temporary plunge in the Dow Jones industrial average.

But Twitter's first two-factor authentication system was relatively basic, and many security experts recommended avoiding it. That system involved sending a one-time code to a mobile phone via SMS, which a user then needed to input into the Twitter website. But the system offered no compatibility with authentication software -- such as Google Authenticator -- that might already reside on a user's mobile device. Furthermore, it offered no backup access to accounts if the phone got lost, and was limited to one phone per account, which made it unsuitable for use with group accounts.

Twitter's revamped system seems to have addressed those problems, and perhaps more. "We wanted to come up with a design where it is only stored on the client side; the secret's only stored on the phone," Smolen told Wired.

But in the wake of National Security Agency whistleblower Edward Snowden's revelations into the U.S. government's current surveillance programs, there might be more to that statement than first meets the eye, said F-Secure's Sullivan. "The secret is only on the client side," he said. "So I guess the NSA cannot ask Twitter for the secret? That definitely seems to fit Twitter's way of doing things. Maybe the security gag orders have kept Twitter from saying just why they're doing it this way?"

Previous
2 of 2
Next
Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Thomas Claburn
50%
50%
Thomas Claburn,
User Rank: Ninja
8/8/2013 | 2:19:03 AM
re: Twitter Overhauls Two Factor Authentication System
Seems like a promising approach.
Register for Dark Reading Newsletters
White Papers
Cartoon
Current Issue
Dark Reading Tech Digest, Dec. 19, 2014
Software-defined networking can be a net plus for security. The key: Work with the network team to implement gradually, test as you go, and take the opportunity to overhaul your security strategy.
Flash Poll
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2014-2188
Published: 2015-02-26
The Authentication Proxy feature in Cisco IOS does not properly handle invalid AAA return codes from RADIUS and TACACS+ servers, which allows remote attackers to bypass authentication in opportunistic circumstances via a connection attempt that triggers an invalid code, as demonstrated by a connecti...

CVE-2015-0594
Published: 2015-02-26
Multiple cross-site scripting (XSS) vulnerabilities in the help pages in Cisco Common Services, as used in Cisco Prime LAN Management Solution (LMS) and Cisco Security Manager, allow remote attackers to inject arbitrary web script or HTML via unspecified parameters, aka Bug IDs CSCuq54654 and CSCun1...

CVE-2015-0632
Published: 2015-02-26
Race condition in the Neighbor Discovery (ND) protocol implementation in Cisco IOS and IOS XE allows remote attackers to cause a denial of service via a flood of Router Solicitation messages on the local network, aka Bug ID CSCuo67770.

CVE-2015-0651
Published: 2015-02-26
Cross-site request forgery (CSRF) vulnerability in the web GUI in Cisco Application Networking Manager (ANM), and Device Manager (DM) on Cisco 4710 Application Control Engine (ACE) appliances, allows remote attackers to hijack the authentication of arbitrary users, aka Bug ID CSCuo99753.

CVE-2015-0882
Published: 2015-02-26
Multiple cross-site scripting (XSS) vulnerabilities in zencart-ja (aka Zen Cart Japanese edition) 1.3 jp through 1.3.0.2 jp8 and 1.5 ja through 1.5.1 ja allow remote attackers to inject arbitrary web script or HTML via a crafted parameter, related to admin/includes/init_includes/init_sanitize.php an...

Dark Reading Radio
Archived Dark Reading Radio
How can security professionals better engage with their peers, both in person and online? In this Dark Reading Radio show, we will talk to leaders at some of the security industry’s professional organizations about how security pros can get more involved – with their colleagues in the same industry, with their peers in other industries, and with the IT security community as a whole.