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.

Operational Security //

Data Leakage

4/20/2018
09:35 AM
Larry Loeb
Larry Loeb
Larry Loeb
50%
50%

Login With Facebook & Watch Your Personal Data Leak

A common feature on many popular websites allows users to login with their Facebook profile. However, a trio of Princeton researchers show that this feature allows personal information to leak and be collected.

It's now common for websites to use a "Login with Facebook" button on their sites as a convenience for users. However, security researchers from Princeton University have discovered that some advertising and analytics services are siphoning user data from these pages when such a button is present.

In their posting, Princeton's Steven Englehardt, Gunes Acar and Arvind Narayanan found insecure design practices allowed at least seven third parties to abuse the websites' access to Facebook user data on 434 of the top 1 million sites.

What happens is that the user clicks the Facebook button, and the Facebook servers will respond with the Facebook account data, which has been previously authorized for that specific site.

However, there may be third-party JavaScript code on the login page, which can intercept this authorized data and extract user details from it.

Trusted websites can request the user's email address and "public profile" -- name, age range, gender, locale and profile photo -- without triggering a review by Facebook. Once the user allows the website to access Facebook, the researchers found that any third-party Javascript embedded in the page can also retrieve the user's Facebook information as if they were the website.

In their report, the three researchers noted: "We believe the websites embedding these scripts are likely unaware of this particular data access."

Even though the user ID collected through the Facebook API will be specific to the requesting website -- this would limit cross-site tracking -- the IDs can be used to retrieve the global Facebook ID, user's profile photo and other public profile information.

This information can then be used to identify and track users across websites and devices.

Another misuse of this Facebook login that the researchers found could trick a user to logging in with Facebook without realizing that they were doing so. They discovered that there was a hidden iframe that was injected, and this would pass the user's information to the embedding script indiscriminately. That meant that any malicious site could have used that iframe to identify visitors.


The fundamentals of network security are being redefined -- don't get left in the dark by a DDoS attack! Join us in Austin from May 14-16 at the fifth-annual Big Communications Event. There's still time to register and communications service providers get in free!

The researchers think this is a bigger problem than just one that can be laid at Facebook's feet. They wrote in their blog:

This unintended exposure of Facebook data to third parties is not due to a bug in Facebook's Login feature. Rather, it is due to the lack of security boundaries between the first-party and third-party scripts in today's web.

The Princeton team realize that what they have described is likely to exist for most social login providers and on mobile devices. Indeed, they found scripts which appear to grab user identifiers from the Google Plus API, as well as from the Russian social media site VK, but did not go into detail about them.

It's the social network that will ultimately have to deal with these problems. Tightening the use of app-scoped IDs may help.

Related posts:

— Larry Loeb has written for many of the last century's major "dead tree" computer magazines, having been, among other things, a consulting editor for BYTE magazine and senior editor for the launch of WebWeek.

Comment  | 
Print  | 
More Insights
Comments
Oldest First  |  Newest First  |  Threaded View
COVID-19: Latest Security News & Commentary
Dark Reading Staff 9/21/2020
Cybersecurity Bounces Back, but Talent Still Absent
Simone Petrella, Chief Executive Officer, CyberVista,  9/16/2020
Meet the Computer Scientist Who Helped Push for Paper Ballots
Kelly Jackson Higgins, Executive Editor at Dark Reading,  9/16/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Latest Comment: Exactly
Current Issue
Special Report: Computing's New Normal
This special report examines how IT security organizations have adapted to the "new normal" of computing and what the long-term effects will be. Read it and get a unique set of perspectives on issues ranging from new threats & vulnerabilities as a result of remote working to how enterprise security strategy will be affected long term.
Flash Poll
How IT Security Organizations are Attacking the Cybersecurity Problem
How IT Security Organizations are Attacking the Cybersecurity Problem
The COVID-19 pandemic turned the world -- and enterprise computing -- on end. Here's a look at how cybersecurity teams are retrenching their defense strategies, rebuilding their teams, and selecting new technologies to stop the oncoming rise of online attacks.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-7734
PUBLISHED: 2020-09-22
All versions of package cabot are vulnerable to Cross-site Scripting (XSS) via the Endpoint column.
CVE-2020-6564
PUBLISHED: 2020-09-21
Inappropriate implementation in permissions in Google Chrome prior to 85.0.4183.83 allowed a remote attacker to spoof the contents of a permission dialog via a crafted HTML page.
CVE-2020-6565
PUBLISHED: 2020-09-21
Inappropriate implementation in Omnibox in Google Chrome on iOS prior to 85.0.4183.83 allowed a remote attacker to spoof the contents of the Omnibox (URL bar) via a crafted HTML page.
CVE-2020-6566
PUBLISHED: 2020-09-21
Insufficient policy enforcement in media in Google Chrome prior to 85.0.4183.83 allowed a remote attacker to leak cross-origin data via a crafted HTML page.
CVE-2020-6567
PUBLISHED: 2020-09-21
Insufficient validation of untrusted input in command line handling in Google Chrome on Windows prior to 85.0.4183.83 allowed a remote attacker to bypass navigation restrictions via a crafted HTML page.