Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Risk

2/8/2013
04:49 PM
Connect Directly
LinkedIn
Twitter
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.

Facebook's 2012 Highs And Lows
Facebook's 2012 Highs And Lows
(click image for larger view and for slideshow)
Several dozen high-profile websites that allow users to login with Facebook credentials became inaccessible for a short period on Thursday afternoon as a result of a bug in Facebook's code.

Around 4 p.m. Pacific Time, the websites operated by at least 35 companies, including ABC, CNN, Gawker, Hulu, Pinterest, Reddit and Yahoo, began redirecting online visitors to a Facebook error page.

Facebook has acknowledged the problem and says that everything is working again. "For a short period of time, there was a bug that redirected people from third party sites with Facebook Login to Facebook.com," a company spokeswoman said in an email. "The issue was quickly resolved."

Asked about how the bug was introduced and whether the company has taken steps to prevent the issue from recurring, Facebook did not respond.

[ Struggling to connect with customers? Read 5 Social Best Practices From Cisco. ]

Facebook Login, previously referred to as Facebook Connect, is an API that allows developers to provide website visitors and mobile app users with the ability to log in to websites and apps using their Facebook credentials. It relies on a protocol called OAuth 2.0 for authentication and authorization and is implemented in JavaScript for Web applications or via platform-specific SDKs.

Hundreds of millions of people log in to third-party websites every month using Facebook Login. The last time anyone from Facebook provided Login usage statistics appears to be in December 2010, when the figure was 250 million people per month. As of March 2012, nine million websites and apps had integrated Facebook Login, according to the company.

But relying on third-party services such as Facebook Login or Google Analytics presents a risk. Ashkan Soltani, an independent security researcher who previously served as staff technologist at the Federal Trade Commission, warns that too few people appreciate the implications of relying on third-party code.

"The browser model allows execution of code from a variety of different sources," explained Soltani in a phone interview. "When you visit a website like CNN's and they embed a third-party service like Facebook Login, you're effectively executing code served by this third party when you visit the website. That has some interesting security implications."

Previous
1 of 2
Next
Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
lgarey@techweb.com
50%
50%
[email protected],
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
News
Former CISA Director Chris Krebs Discusses Risk Management & Threat Intel
Kelly Sheridan, Staff Editor, Dark Reading,  2/23/2021
Edge-DRsplash-10-edge-articles
Security + Fraud Protection: Your One-Two Punch Against Cyberattacks
Joshua Goldfarb, Director of Product Management at F5,  2/23/2021
News
Cybercrime Groups More Prolific, Focus on Healthcare in 2020
Robert Lemos, Contributing Writer,  2/22/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win an Amazon Gift Card! Click Here
Latest Comment: This comment is waiting for review by our moderators.
Current Issue
2021 Top Enterprise IT Trends
We've identified the key trends that are poised to impact the IT landscape in 2021. Find out why they're important and how they will affect you today!
Flash Poll
Building the SOC of the Future
Building the SOC of the Future
Digital transformation, cloud-focused attacks, and a worldwide pandemic. The past year has changed the way business works and the way security teams operate. There is no going back.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2021-27132
PUBLISHED: 2021-02-27
SerComm AG Combo VD625 AGSOT_2.1.0 devices allow CRLF injection (for HTTP header injection) in the download function via the Content-Disposition header.
CVE-2021-25284
PUBLISHED: 2021-02-27
An issue was discovered in through SaltStack Salt before 3002.5. salt.modules.cmdmod can log credentials to the info or error log level.
CVE-2021-3144
PUBLISHED: 2021-02-27
In SaltStack Salt before 3002.5, eauth tokens can be used once after expiration. (They might be used to run command against the salt master or minions.)
CVE-2021-3148
PUBLISHED: 2021-02-27
An issue was discovered in SaltStack Salt before 3002.5. Sending crafted web requests to the Salt API can result in salt.utils.thin.gen_thin() command injection because of different handling of single versus double quotes. This is related to salt/utils/thin.py.
CVE-2021-3151
PUBLISHED: 2021-02-27
i-doit before 1.16.0 is affected by Stored Cross-Site Scripting (XSS) issues that could allow remote authenticated attackers to inject arbitrary web script or HTML via C__MONITORING__CONFIG__TITLE, SM2__C__MONITORING__CONFIG__TITLE, C__MONITORING__CONFIG__PATH, SM2__C__MONITORING__CONFIG__PATH, C__M...