Risk

10/19/2010
12:20 PM
50%
50%

Congressmen Poke Facebook Over Privacy Breaches

Reps. Markey, Barton demand answers on what the social network knew about unauthorized disclosure of user ID numbers and what it plans to do about it.

Best Mobile Apps For Busy Professionals
(click image for larger view)
Best Mobile Apps For Busy Professionals
In response to the recent revelations of another privacy breach at Facebook, Congress is again asking questions of the social media giant.

U.S. Reps. Edward Markey (D-Mass.) and Joe Barton (R-Texas) on Monday sent Facebook founder Mark Zuckerberg a letter pressing the company to release more details about the way in which applications handle user information. The two congressmen were prompted to act after results of Wall Street Journal investigation discovered privacy breaches affected tens of millions of users, even those who adjusted their settings to the strictest settings possible.

All 10 of the most popular apps on Facebook shared Facebook members' user ID numbers (UIDs) with outside companies, and three of the top 10 Facebook apps, such as Farmville, shared information about users' friends, too. In a post to its developer blog on Sunday, Facebook downplayed the privacy impact, even as it promised to take steps to prevent reoccurrences.

But the two politicians want more. Barton is a ranking member of the Committee on Energy and Policy, and Markey is chairman of the Energy and Environment Subcommittee.

"Given the number of current users, the rate at which that number grows worldwide, and the age range of Facebook users, combined with the amount and nature of information these users place in Facebook's trust, this series of breaches of consumer privacy is a cause for concern," the legislators wrote. "As I am sure you are aware, the Committee on Energy and Commerce is the primary House panel for oversight of consumer privacy. As I am sure you are also aware, comprehensive privacy legislation is currently pending before the Committee."

Markey and Barton asked Facebook to respond to 18 questions by Oct. 27. The congressmen's questions include the number of users impacted by the privacy breaches; the specific nature of the data transmitted from the third-party applications; when Facebook knew of the breaches; whether or not Facebook notified users of the breaches; which Facebook terms were violated; the number of third-party applications in violation; the procedures and guidelines Facebook has in place to detect and prevent this type of breach; whether similar breaches have occurred in the past; whether Facebook receives remuneration of any kind as a result of data-sharing with ad or tracking companies; whether Facebook will proactively seek the deletion of users' personal information from Internet and ad companies' databases; the extent to which minors' information was breached; the extent to which medical and financial data was breached, and any policy or procedural changes Facebook plans to ensure users have better control over their data and over their use of third-party apps, according to the letter.

Facebook responded over the weekend by blocking access to one game developer, Lolapps, but restored access shortly thereafter.

"Press reports have exaggerated the implications of sharing a UID," wrote Facebook engineer Mike Vernal. "Knowledge of a UID does not enable anyone to access private user information without explicit user consent. Nevertheless, we are committed to ensuring that even the inadvertent passing of UIDs is prevented and all applications are in compliance with our policy."

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
1.9 Billion Data Records Exposed in First Half of 2017
Kelly Jackson Higgins, Executive Editor at Dark Reading,  9/20/2017
Get Serious about IoT Security
Derek Manky, Global Security Strategist, Fortinet,  9/20/2017
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
Security Vulnerabilities: The Next Wave
Just when you thought it was safe, researchers have unveiled a new round of IT security flaws. Is your enterprise ready?
Flash Poll
[Strategic Security Report] How Enterprises Are Attacking the IT Security Problem
[Strategic Security Report] How Enterprises Are Attacking the IT Security Problem
Enterprises are spending more of their IT budgets on cybersecurity technology. How do your organization's security plans and strategies compare to what others are doing? Here's an in-depth look.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2017-0290
Published: 2017-05-09
NScript in mpengine in Microsoft Malware Protection Engine with Engine Version before 1.1.13704.0, as used in Windows Defender and other products, allows remote attackers to execute arbitrary code or cause a denial of service (type confusion and application crash) via crafted JavaScript code within ...

CVE-2016-10369
Published: 2017-05-08
unixsocket.c in lxterminal through 0.3.0 insecurely uses /tmp for a socket file, allowing a local user to cause a denial of service (preventing terminal launch), or possibly have other impact (bypassing terminal access control).

CVE-2016-8202
Published: 2017-05-08
A privilege escalation vulnerability in Brocade Fibre Channel SAN products running Brocade Fabric OS (FOS) releases earlier than v7.4.1d and v8.0.1b could allow an authenticated attacker to elevate the privileges of user accounts accessing the system via command line interface. With affected version...

CVE-2016-8209
Published: 2017-05-08
Improper checks for unusual or exceptional conditions in Brocade NetIron 05.8.00 and later releases up to and including 06.1.00, when the Management Module is continuously scanned on port 22, may allow attackers to cause a denial of service (crash and reload) of the management module.

CVE-2017-0890
Published: 2017-05-08
Nextcloud Server before 11.0.3 is vulnerable to an inadequate escaping leading to a XSS vulnerability in the search module. To be exploitable a user has to write or paste malicious content into the search dialogue.