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

1/31/2008
02:23 AM
Connect Directly
Google+
Twitter
RSS
E-Mail
50%
50%

90% of Facebook Apps Have Unnecessary Access to Private Data

Researcher is building a prototype to protect users' privacy from Facebook 'widgets'

University of Virginia researchers have discovered that 90.7 percent of Facebook's most popular applications have access to users' private data, whether they need it or not -- leaving users exposed to targeted phishing attacks and identity theft. So a UVA researcher is currently building a "privacy-by-proxy" prototype aimed at hiding a user's private information on Facebook from these apps.

Today, a third-party Facebook "widget" or application requires full user privileges to a user's account on the social networking site, including his or her name, address, friends' profiles, and photos. There's no way to specify which apps can access which personal information. So Adrienne Felt, a fourth-year computer science major at UVA, is developing an application that lets Facebook users run these widgets while keeping their private data private. It basically works like this: The Facebook server gives the application a random sequence of letters in lieu of the user's name and other private data.

Felt began developing the tool after studying the top 150 Facebook third-party platform applications last fall. It turns out 8.7 percent of these widgets didn’t need any personal information, she found, and only 9.3 percent required private data -- the remaining 82 percent used "public" Facebook data, such as the user's name, network, and list of friends. Felt and fellow researcher Andrew Spisak concluded that nearly 91 percent of these apps are getting access to more privileges than they actually need in order to run.

And when users install these widgets, their data gets stored on the widgets' third-party servers. Although Facebook's terms of service say developers can't abuse the Facebook data they access, there's no way for Facebook to enforce that, Felt says, because once that data leaves Facebook's servers, it's free game to the third-party application provider.

Privacy has always been a sticky issue for social networking sites. But Facebook's third-party apps, which anyone with a Facebook account can develop, have been considered by some security experts as an open invitation for abuse. Earlier this month, Fortinet researchers found the first evidence of such abuse, reporting spyware disguised as a Facebook application spreading around the social networking site. (See 'Secret Crush' Spreads Spyware, Not Love.)

Kevin Haley, director, of product management for Symantec Security Response, says another risk with these apps is the distribution of malware. "Now that you have a platform to create programs for these sites... malware quickly follows," he says.

Felt's prototype is providing some hope for protecting and securing Facebook users' privacy. "This is the first step," says Felt, who has built several Facebook widgets herself. "Hopefully, the research findings and proposed solution will trigger more responsible privacy and information management policies from social networking sites and will better inform users."

— Kelly Jackson Higgins, Senior Editor, Dark Reading

  • Fortinet Inc.

    Kelly Jackson Higgins is the Executive Editor of Dark Reading. She is an award-winning veteran technology and business journalist with more than two decades of experience in reporting and editing for various publications, including Network Computing, Secure Enterprise ... View Full Bio

    Comment  | 
    Print  | 
    More Insights
  • Comments
    Newest First  |  Oldest First  |  Threaded View
    Why Cyber-Risk Is a C-Suite Issue
    Marc Wilczek, Digital Strategist & CIO Advisor,  11/12/2019
    Unreasonable Security Best Practices vs. Good Risk Management
    Jack Freund, Director, Risk Science at RiskLens,  11/13/2019
    6 Small-Business Password Managers
    Curtis Franklin Jr., Senior Editor at Dark Reading,  11/8/2019
    Register for Dark Reading Newsletters
    White Papers
    Video
    Cartoon Contest
    Write a Caption, Win a Starbucks Card! Click Here
    Latest Comment: This comment is waiting for review by our moderators.
    Current Issue
    Navigating the Deluge of Security Data
    In this Tech Digest, Dark Reading shares the experiences of some top security practitioners as they navigate volumes of security data. We examine some examples of how enterprises can cull this data to find the clues they need.
    Flash Poll
    Rethinking Enterprise Data Defense
    Rethinking Enterprise Data Defense
    Frustrated with recurring intrusions and breaches, cybersecurity professionals are questioning some of the industrys conventional wisdom. Heres a look at what theyre thinking about.
    Twitter Feed
    Dark Reading - Bug Report
    Bug Report
    Enterprise Vulnerabilities
    From DHS/US-CERT's National Vulnerability Database
    CVE-2019-18986
    PUBLISHED: 2019-11-15
    Pimcore before 6.2.2 allow attackers to brute-force (guess) valid usernames by using the 'forgot password' functionality as it returns distinct messages for invalid password and non-existing users.
    CVE-2019-18981
    PUBLISHED: 2019-11-15
    Pimcore before 6.2.2 lacks an Access Denied outcome for a certain scenario of an incorrect recipient ID of a notification.
    CVE-2019-18982
    PUBLISHED: 2019-11-15
    bundles/AdminBundle/Controller/Admin/EmailController.php in Pimcore before 6.3.0 allows script execution in the Email Log preview window because of the lack of a Content-Security-Policy header.
    CVE-2019-18985
    PUBLISHED: 2019-11-15
    Pimcore before 6.2.2 lacks brute force protection for the 2FA token.
    CVE-2019-18928
    PUBLISHED: 2019-11-15
    Cyrus IMAP 2.5.x before 2.5.14 and 3.x before 3.0.12 allows privilege escalation because an HTTP request may be interpreted in the authentication context of an unrelated previous request that arrived over the same connection.