Risk
2/8/2013
04:49 PM
Connect Directly
LinkedIn
Twitter
Google+
RSS
E-Mail
50%
50%

Facebook Login Bug: Lessons Learned

Service interruption at dozens of prominent websites including CNN and Hulu reminds that third-party code integration carries risks.

Soltani likens the situation to using giving a speech using the Mad Libs format. You allow a third-party to supply you with words periodically and hope that those words don't alter what you meant to say or embarrass you.

"As a result of a Facebook bug, entire domains were redirected," said Soltani. "That's an incredible amount of power to have."

Facebook presumably isn't going to be introducing similar bugs on a frequent basis. But the online ad industry deals with code trust problems every day.

Websites allow ads to be injected into their webpage code in the same way that many sites allow Facebook Login code to be injected. And in the ad business, the tenuous chain of connections across multiple domains and servers makes trust much more difficult. Cyber criminals routinely attempt to subvert ad network security, through hacking and fraudulent business practices, to distribute malicious code.

Soltani said that combined with other malicious activity such as DNS hijacking, reliance on third-party injected code can be even more of a problem.

There's also the issue of performance. Until December 2009, Google Analytics -- incorporated into many websites -- wasn't asynchronous, meaning that calls to Google's servers made webpages load more slowly. Other widget code inserted into webpages often has a similar effect.

In a blog post last October, Aarron Walter, director of user experience at email marketing service MailChimp, argued that social logins aren't worth it, a position others have taken before him. The social login buttons offered by Facebook and Twitter, he said, put security in someone else's hands and present the risk of brand damage if problems occur.

Moreover, the rationale for implementing social login buttons -- user convenience and ease of use -- might not be justified. Walter found that a 66% decrease in failed logins and a 42% decrease in password resets at Mail Chimp last year were the result of user interface design improvements and better programming, or "better error handling and copywriting" as he put it. Social logins contributed to only 3.4% of the drop in login problems.

Further complicating the question of whether to use a social login is the finding that many companies have implemented Facebook Login ineffectively. Research published by marketing consultancy Social Labs in September 2012 indicates that among the top 500 online retailers, only 30 have implemented a social login -- 77% of these being Facebook Login -- and a fair number of these have done so incorrectly. For example, 30% of the 30 online retailers using a social login require a website password in tandem with a visitor's social username and password, and 15 of these online retailers don't offer a social login during the checkout process, making for an inconsistent user experience. Finally, none of online retailers surveyed have implemented Facebook's login persistence, which automatically logs users in when they return to the website.

Despite these issues, Sociable Labs expects adoption of social logins to increase over time.

Previous
2 of 2
Next
Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
lgarey@techweb.com
50%
50%
lgarey@techweb.com,
User Rank: Apprentice
2/11/2013 | 4:04:36 PM
re: Facebook Login Bug: Lessons Learned
The Mad Libs example is excellent. Is there any indication that this was not just a bug but a hack? Lorna Garey, IW Reports
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-2015-2849
Published: 2015-07-07
SQL injection vulnerability in main.ant in the ANTlabs InnGate firmware on IG 3100, InnGate 3.01 E, InnGate 3.10 E, InnGate 3.10 M, SG 4, and SSG 4 devices, when https is used, allows remote attackers to execute arbitrary SQL commands via the ppli parameter.

CVE-2015-2850
Published: 2015-07-07
Cross-site scripting (XSS) vulnerability in index-login.ant in the ANTlabs InnGate firmware on IG 3100, InnGate 3.01 E, InnGate 3.10 E, InnGate 3.10 M, SG 4, and SSG 4 devices allows remote attackers to inject arbitrary web script or HTML via the msg parameter.

CVE-2015-3216
Published: 2015-07-07
Race condition in a certain Red Hat patch to the PRNG lock implementation in the ssleay_rand_bytes function in OpenSSL, as distributed in openssl-1.0.1e-25.el7 in Red Hat Enterprise Linux (RHEL) 7 and other products, allows remote attackers to cause a denial of service (application crash) by establi...

CVE-2014-3653
Published: 2015-07-06
Cross-site scripting (XSS) vulnerability in the template preview function in Foreman before 1.6.1 allows remote attackers to inject arbitrary web script or HTML via a crafted provisioning template.

CVE-2014-5406
Published: 2015-07-06
The Hospira LifeCare PCA Infusion System before 7.0 does not validate network traffic associated with sending a (1) drug library, (2) software update, or (3) configuration change, which allows remote attackers to modify settings or medication data via packets on the (a) TELNET, (b) HTTP, (c) HTTPS, ...

Dark Reading Radio
Archived Dark Reading Radio
Marc Spitler, co-author of the Verizon DBIR will share some of the lesser-known but most intriguing tidbits from the massive report