Risk
2/14/2012
12:35 PM
50%
50%

Looking For Love? Don't Trust Online Dating Sites

When it comes to how dating websites secure and share information about their users, be sure to read the fine print, and don't be afraid to walk away.

Beware online dating websites, at least when it comes to their data privacy practices.

That warning comes by way of the Electronic Frontier Foundation (EFF), a non-profit group devoted to protecting digital rights. According to the organization, numerous dating sites--which are for-profit businesses, after all--sell data on their customers to third parties, including Google and Facebook. Furthermore, many online dating sites suffer from poor information security practices and may not delete profiles or images in a timely manner.

Online dating websites may also allow third-party search engines to index your profile. Notably, a public profile for Julian Assange, the editor in chief of WikiLeaks, was discovered in late 2010 on the free dating website OkCupid. While the site allows users to disable such indexing, even the privacy obsessed Assange apparently didn't realize that by default, all profiles are public.

[ Facebook and other social networking sites don't do enough to protect privacy, say users. See Social Media Survey: Privacy, Security Concerns Persist. ]

People might also be surprised to find that some online dating website profiles are being sold en masse to third parties. "Often, this transaction is gift-wrapped with the promise that your individual data is 'anonymized' or sold in aggregate form, yet users should be wary of such promises," said Rainey Reitman, EFF activism director, in a blog post. "Using data from social networking sites sold to advertisers, Stanford researcher Arvind Narayanan demonstrated that it's hard to truly anonymize data before it's packaged and sold."

The data being shared may also give people pause. Notably, Stanford computer science graduate student Jonathan Mayer last year released a study showing that OkCupid was selling or sharing user information with almost 30 third-party companies. That finding came from Mayer's review of the information-sharing practices of the top 250 websites listed on Quantcast.

All told, he found that 61% of the websites in his sample shared a username or user ID with a third-party website. Those third-party sites were ComScore (for 44% of the top 250 websites), Google Analytics (42%), Quantcast (34%), Google Advertising (34%), and Facebook (24%). In the case of OkCupid, shared information also included everything from age and religion to details about pets and frequency of drinking or smoking.

Leave it to a digital rights group to pour cold water on potential Valentine's Day romance? Perhaps, but by keeping an eye on online privacy practices for dating websites may offer people better long-term satisfaction.

One place to start is by reviewing a company's privacy policies to see what it promises. Also look at a company's information security history. One case in point is Grindr, a mobile app that's been embraced by the gay community. On Jan. 20, the company confirmed that there was a vulnerability in its software that could allow an attacker to access photos and messages and impersonate other users, and promised a fix "over the next few days." The company ultimately released a fix on February 10. But in the interim, security experts had recommended that the site's 3 million users temporarily delete their Grindr profiles.

Also check whether dating websites have implemented HTTPS to secure Web sessions, especially against local attackers who are sniffing packets, for example by using a tool such as Firesheep. "Our recent survey of major online dating sites found that most of them were not properly implementing HTTPS," said EFF's Reitman. "Some online dating sites offer partial support for HTTPS, and some offer none at all. This leaves user data exposed."

One Firefox plug-in that can help, she said, is HTTPS Everywhere, which is maintained by the Tor Project and EFF. The tool automatically enables HTTPS for any site that offers it. "As more dating sites begin to provide support for HTTPS, we'll expand the ruleset for HTTPS Everywhere to include those sites so you'll be better protected."

There are no silver bullets when it comes to protecting company and customer data from loss or theft, but there are technological and procedural systems that will go a long way toward preventing a WikiLeaks-like data dump. Download our How To Prevent An Online Data Dump report. (Free registration required.)

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Bprince
50%
50%
Bprince,
User Rank: Ninja
2/15/2012 | 3:11:41 AM
re: Looking For Love? Don't Trust Online Dating Sites
Good advice would also be for people to read the terms of service before uploading any information.
Brian Prince, InformationWeek/Dark Reading Comment Moderator
Register for Dark Reading Newsletters
White Papers
Cartoon
Current Issue
Flash Poll
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2013-6501
Published: 2015-03-30
The default soap.wsdl_cache_dir setting in (1) php.ini-production and (2) php.ini-development in PHP through 5.6.7 specifies the /tmp directory, which makes it easier for local users to conduct WSDL injection attacks by creating a file under /tmp with a predictable filename that is used by the get_s...

CVE-2014-9652
Published: 2015-03-30
The mconvert function in softmagic.c in file before 5.21, as used in the Fileinfo component in PHP before 5.4.37, 5.5.x before 5.5.21, and 5.6.x before 5.6.5, does not properly handle a certain string-length field during a copy of a truncated version of a Pascal string, which might allow remote atta...

CVE-2014-9653
Published: 2015-03-30
readelf.c in file before 5.22, as used in the Fileinfo component in PHP before 5.4.37, 5.5.x before 5.5.21, and 5.6.x before 5.6.5, does not consider that pread calls sometimes read only a subset of the available data, which allows remote attackers to cause a denial of service (uninitialized memory ...

CVE-2014-9705
Published: 2015-03-30
Heap-based buffer overflow in the enchant_broker_request_dict function in ext/enchant/enchant.c in PHP before 5.4.38, 5.5.x before 5.5.22, and 5.6.x before 5.6.6 allows remote attackers to execute arbitrary code via vectors that trigger creation of multiple dictionaries.

CVE-2014-9709
Published: 2015-03-30
The GetCode_ function in gd_gif_in.c in GD 2.1.1 and earlier, as used in PHP before 5.5.21 and 5.6.x before 5.6.5, allows remote attackers to cause a denial of service (buffer over-read and application crash) via a crafted GIF image that is improperly handled by the gdImageCreateFromGif function.

Dark Reading Radio
Archived Dark Reading Radio
Good hackers--aka security researchers--are worried about the possible legal and professional ramifications of President Obama's new proposed crackdown on cyber criminals.