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
    Oldest First  |  Newest First  |  Threaded View
    Why Cyber-Risk Is a C-Suite Issue
    Marc Wilczek, Digital Strategist & CIO Advisor,  11/12/2019
    Black Hat Q&A: Hacking a '90s Sports Car
    Black Hat Staff, ,  11/7/2019
    The Cold Truth about Cyber Insurance
    Chris Kennedy, CISO & VP Customer Success, AttackIQ,  11/7/2019
    Register for Dark Reading Newsletters
    White Papers
    Video
    Cartoon Contest
    Current Issue
    7 Threats & Disruptive Forces Changing the Face of Cybersecurity
    This Dark Reading Tech Digest gives an in-depth look at the biggest emerging threats and disruptive forces that are changing the face of cybersecurity today.
    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-16863
    PUBLISHED: 2019-11-14
    STMicroelectronics ST33TPHF2ESPI TPM devices before 2019-09-12 allow attackers to extract the ECDSA private key via a side-channel timing attack because ECDSA scalar multiplication is mishandled, aka TPM-FAIL.
    CVE-2019-18949
    PUBLISHED: 2019-11-14
    SnowHaze before 2.6.6 is sometimes too late to honor a per-site JavaScript blocking setting, which leads to unintended JavaScript execution via a chain of webpage redirections targeted to the user's browser configuration.
    CVE-2011-1930
    PUBLISHED: 2019-11-14
    In klibc 1.5.20 and 1.5.21, the DHCP options written by ipconfig to /tmp/net-$DEVICE.conf are not properly escaped. This may allow a remote attacker to send a specially crafted DHCP reply which could execute arbitrary code with the privileges of any process which sources DHCP options.
    CVE-2011-1145
    PUBLISHED: 2019-11-14
    The SQLDriverConnect() function in unixODBC before 2.2.14p2 have a possible buffer overflow condition when specifying a large value for SAVEFILE parameter in the connection string.
    CVE-2011-1488
    PUBLISHED: 2019-11-14
    A memory leak in rsyslog before 5.7.6 was found in the way deamon processed log messages are logged when $RepeatedMsgReduction was enabled. A local attacker could use this flaw to cause a denial of the rsyslogd daemon service by crashing the service via a sequence of repeated log messages sent withi...