Third-party JavaScript code loaded on the page will interfere with this data and retrieve it. Although some pages collect user IDs, this ID can be transferred to Facebook ID and used to collect more information.
Scenario 2 is somewhat more complicated. If the page using 'Sign in with Facebook', a third party can embed iframe on other pages to trick the authenticated user's browser by logging into their Facebook. As in the previous case, the 3rd party monitoring script also interferes with and retrieves Facebook data.
Data collection process diagram of scenario 2
'Leaving Facebook data to a third party is not due to the error of' Sign in with Facebook 'but due to the lack of security boundaries between the 1st and 3rd party web scripts', researchers Princeton's rescue said.
'Facebook and other social networks can avoid this situation: censoring APIs to see which units access social network login data, where and how. Facebook may also disallow viewing user profiles and Facebook IDs by app-scope user ID. Maybe now should allow anonymous login (Anonymous Login) with Facebook when they have said so 4 years ago, 'the researchers said.
See more: