Endpoint //

Authentication

8/3/2018
09:00 AM
Connect Directly
Twitter
Twitter
RSS
E-Mail
50%
50%

Is SMS 2FA Enough Login Protection?

Experts say Reddit breach offers a prime example of the risks of depending on one-time passwords sent via text.

The "serious attack" against Reddit, disclosed earlier this week, may have only resulted in a limited breach, but Reddit's engineering team and many experts in the security industry believe it should be a strong wake-up call for organizations to bolster their methods of two-factor authentication (2FA). 

According to Reddit's engineering staff, "we suspect weaknesses inherent to SMS-based 2FA to be the root cause of this incident," which exposed old user data and hashed credentials. In its announcement of the scope of the breach, the firm encouraged fellow security professionals to move to token-based authentication. 

That lesson was heard in a loud refrain from security pundits following Reddit's disclosure. 

"While lots of organizations think 2FA is a silver bullet for authentication, it actually isn’t, thanks to weaknesses in mobile networks that allow SMSes to be intercepted," says Leigh-Anne Galloway, cybersecurity resilience lead at Positive Technologies.

The way Reddit was breached is a common attack that takes advantage of unwarranted faith in SMS-based 2FA, she adds. "SMS alone is not enough to constitute adequate defense of customer and employee data," Galloway says. "Two-factor authentication that involves standalone hardware token generators is needed to mitigate the risk of such attacks."

The vulnerabilities of SMS one-time password (OTP) tokens to interception are hardly a secret, says Andy Smith, vice president of product marketing at Centrify. He sees another lesson here about how important it is for security and IT teams to stay abreast of the latest security standards. For example, he points to the fact that the National Institute of Standards and Technologies in its Special Publication 800-63 Guidelines recommends restricting the use of SMS for OTP and advises to completely remove OTP generation via email. 

"Instead, NIST is propagating the use of either application-enabled or hardware-based security keys that are leveraging the FIDO standard," he says.

In fact, hardware-based security keys utilizing FIDO's Universal Second Factor (U2F) standard have been gaining some very high-profile traction from big brands using them both for customers and employees. For example, in January Facebook extended support for U2F to customers that wanted to start protecting their accounts with more secure 2FA methods.

Meantime, just last month Google said it has managed to keep all of its 85,000-plus employees from being phished for over a year since it started making them use U2F-based security keys for logins. The program has been so successful that Google plans on rolling out its own branded security keys to Google Cloud corporate customers.

Nevertheless, some security evangelists believe that the industry shouldn't pile too much on SMS-based 2FA.

"In many cases, it's still better than nothing," says Ilia Kolochenko, CEO of High-Tech Bridge. "Moreover, when most of business-critical applications have serious vulnerabilities varying from injections to RCE, 2FA hardening is definitely not the most important task to take care of." 

SANS senior instructor Jake Williams agrees, stating in a Twitter post that "2FA hard token zealots" should tone it down.

"Stop discouraging orgs from implementing 'good-enough' security," he wrote.

Nevertheless, while SMS 2FA is indeed better than a password alone, it is important for organizations not to be lulled into a false sense of security using it, says Craig Young, computer security researcher for Tripwire's Vulnerability and Exposure Research Team (VERT).

"Although any form of multifactor authentication is a considerable improvement on simple password models, SMS-based verification tokens can be stolen with a variety of well-known techniques, including social engineering, mobile malware, or by directly intercepting and decrypting signals from cell towers," he says.

The interesting aspect of the Reddit breach, Young adds, is that it is not a financial institution, which traditionally is the target for these types of attacks.

Related Content:

 

 

 

Black Hat USA returns to Las Vegas with hands-on technical Trainings, cutting-edge Briefings, Arsenal open-source tool demonstrations, top-tier security solutions and service providers in the Business Hall. Click for information on the conference and to register.

Ericka Chickowski specializes in coverage of information technology and business innovation. She has focused on information security for the better part of a decade and regularly writes about the security industry as a contributor to Dark Reading.  View Full Bio

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Election Websites, Back-End Systems Most at Risk of Cyberattack in Midterms
Kelly Jackson Higgins, Executive Editor at Dark Reading,  8/14/2018
Intel Reveals New Spectre-Like Vulnerability
Curtis Franklin Jr., Senior Editor at Dark Reading,  8/15/2018
Australian Teen Hacked Apple Network
Dark Reading Staff 8/17/2018
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
Flash Poll
New Best Practices for Secure App Development
New Best Practices for Secure App Development
The transition from DevOps to SecDevOps is combining with the move toward cloud computing to create new challenges - and new opportunities - for the information security team. Download this report, to learn about the new best practices for secure application development.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2018-15504
PUBLISHED: 2018-08-18
An issue was discovered in Embedthis GoAhead before 4.0.1 and Appweb before 7.0.2. The server mishandles some HTTP request fields associated with time, which results in a NULL pointer dereference, as demonstrated by If-Modified-Since or If-Unmodified-Since with a month greater than 11.
CVE-2018-15505
PUBLISHED: 2018-08-18
An issue was discovered in Embedthis GoAhead before 4.0.1 and Appweb before 7.0.2. An HTTP POST request with a specially crafted "Host" header field may cause a NULL pointer dereference and thus cause a denial of service, as demonstrated by the lack of a trailing ']' character in an IPv6 a...
CVE-2018-15492
PUBLISHED: 2018-08-18
A vulnerability in the lservnt.exe component of Sentinel License Manager version 8.5.3.35 (fixed in 8.5.3.2403) causes UDP amplification.
CVE-2018-15494
PUBLISHED: 2018-08-18
In Dojo Toolkit before 1.14, there is unescaped string injection in dojox/Grid/DataGrid.
CVE-2018-15495
PUBLISHED: 2018-08-18
/filemanager/upload.php in Responsive FileManager before 9.13.3 allows Directory Traversal and SSRF because the url parameter is used directly in a curl_exec call, as demonstrated by a file:///etc/passwd value.