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.

Vulnerabilities / Threats

10/21/2010
06:47 PM
Connect Directly
Google+
LinkedIn
Twitter
RSS
E-Mail
50%
50%

Facebook Plans Encryption To Fix Privacy

Developers have been asked to review a proposal to encrypt information passed through Facebook application URLs.

Responding to concerns raised earlier this week that popular Facebook apps expose user identification numbers (UIDs), Facebook on Thursday proposed addressing the issue through encryption.

Facebook engineer Mike Vernal published the proposal on the Facebook developer's blog, noting that Facebook hopes to lay the groundwork to implement encrypted UIDs over the next few weeks and then to add support for encryption following community feedback. A specific migration timeline will be announced later.

The issue is that certain Facebook apps transmit UID numbers, which may be used to identify Facebook users and link actions at other Web sites to a Facebook identity. When a Facebook user requests a Web page with images or other resources, the user's browser may send HTTP header information that includes the URL of the Web page. For a particular type of Facebook Platform application, an iframe-based canvas application that includes a third-party iframe or resource, the HTTP Referrer header may include the user's UID number once the user has authorized the application.

The UID number is used to personalize Web pages. It's what allows Web pages to include information about one's friends. Unfortunately, it can also compromise user privacy, particularly if the user is not aware that his or her UID is being shared.

Vernal says that while some Facebook developers have been employing page redirection or "double framing" to remove UIDs from URLs, Facebook wants to develop a better fix for the problem.

The change will prevent the accidental sharing of UIDs through the Referer header; it won't stop deliberate UID sharing that violates Facebook's developer rules.

It also won't make HTTP Referer headers less prone to exposing information related to other Web sites or Web applications.

"While this proposal will address the inadvertent sharing of this information on Facebook, the underlying issue of data sharing via HTTP headers is a Web-wide problem," wrote Vernal. "We look forward to working with the Web standards community and browser vendors over the coming months to help address this issue."

Comment  | 
Print  | 
More Insights
Comments
Threaded  |  Newest First  |  Oldest First
I 'Hacked' My Accounts Using My Mobile Number: Here's What I Learned
Nicole Sette, Director in the Cyber Risk practice of Kroll, a division of Duff & Phelps,  11/19/2019
DevSecOps: The Answer to the Cloud Security Skills Gap
Lamont Orange, Chief Information Security Officer at Netskope,  11/15/2019
Attackers' Costs Increasing as Businesses Focus on Security
Robert Lemos, Contributing Writer,  11/15/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
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-2013-3311
PUBLISHED: 2019-11-21
Directory traversal vulnerability in the Loftek Nexus 543 IP Camera allows remote attackers to read arbitrary files via a .. (dot dot) in the URL of an HTTP GET request.
CVE-2013-3312
PUBLISHED: 2019-11-21
Multiple cross-site request forgery (CSRF) vulnerabilities in the Loftek Nexus 543 IP Camera allow remote attackers to hijack the authentication of unspecified victims for requests that change (1) passwords or (2) firewall configuration, as demonstrated by a request to set_users.cgi.
CVE-2013-3313
PUBLISHED: 2019-11-21
The Loftek Nexus 543 IP Camera stores passwords in cleartext, which allows remote attackers to obtain sensitive information via an HTTP GET request to check_users.cgi. NOTE: cleartext passwords can also be obtained from proc/kcore when leveraging the directory traversal vulnerability in CVE-2013-331...
CVE-2013-3314
PUBLISHED: 2019-11-21
The Loftek Nexus 543 IP Camera allows remote attackers to obtain (1) IP addresses via a request to get_realip.cgi or (2) firmware versions (ui and system), timestamp, serial number, p2p port number, and wifi status via a request to get_status.cgi.
CVE-2015-2793
PUBLISHED: 2019-11-21
Cross-site scripting (XSS) vulnerability in templates/openid-selector.tmpl in ikiwiki before 3.20150329 allows remote attackers to inject arbitrary web script or HTML via the openid_identifier parameter in a verify action to ikiwiki.cgi.