Risk
2/1/2011
07:22 PM
Connect Directly
Google+
LinkedIn
Twitter
RSS
E-Mail
50%
50%

Usage Of Flash To Recreate Deleted Cookies Minimal

But research suggests regulation may be needed to deal with that companies that track Internet users in contravention of privacy controls.

The good news is that zombie cookies -- deleted HTTP cookies that have been resurrected through Adobe Flash Local Shared Objects (LSOs) -- are rare.

The bad news is that lack of visibility into Internet marketers' tracking practices makes self-regulation a dubious strategy for averting potential privacy problems.

A study published on Monday by Carnegie Mellon researchers Aleecia M. McDonald and Lorrie Faith Cranor, "A Survey of the Use of Adobe Flash Local Shared Objects to Respawn HTTP Cookies," has found that misuse of Adobe's Flash technology to rebuild deleted HTTP cookies isn't as widespread as some have feared.

LSOs are Flash's version of HTTP cookies. Few computer users are familiar with them but they present even greater potential for privacy problems because they can be read from any browser, because they're don't expire, and because they can store more data and more complex data types than HTTP cookies.

Because they can be uniquely identified, LSOs present similar privacy problems to cookies while being less affected by user choice. As the study explains, marketers turned to LSOs to address the data quality problems created by the deletion of cookies by Internet users. But doing so flouts users' expressed desire for privacy.

The researchers found no evidence of cookie respawning at 500 randomly selected Web sites and only two instances of resurrected cookies at the 100 most popular Web sites. They also found that LSOs were being used as unique identifiers at 9% of the most popular 100 Web sites and at 3.4% of the 500 randomly selected Web sites.

"We found respawning is currently rare but sites still use LSOs as persistent identifiers..., which may or may not have privacy implications...," the study states.

The researchers suggest that Adobe should take a more proactive role in making it clear that LSOs should not be used to uniquely identify computers and in providing developers with strong privacy guidance and tools. The researchers claim that just over 40% of sites save LSO data, which they interpret as a sign that Flash developers may not understand the privacy implications of LSOs.

They also express skepticism about the ongoing viability of self-regulation. "It is difficult to find calls for a purely industry self-regulation approach to Internet privacy credible when industry demonstrates willingness to violate user intent and privacy as demonstrated by using LSOs to respawn HTTP cookies or individually identify computers," they state.

With the Federal Trade Commission mulling privacy rules after years of hands-off policy, not to mention a slew of recent lawsuits over alleged privacy violations related to tracking, the era of lightly regulated online marketing may be coming to an end.

Comment  | 
Print  | 
More Insights
Comments
Threaded  |  Newest First  |  Oldest First
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
Security Operations and IT Operations: Finding the Path to Collaboration
A wide gulf has emerged between SOC and NOC teams that's keeping both of them from assuring the confidentiality, integrity, and availability of IT systems. Here's how experts think it should be bridged.
Flash Poll
New Best Practices for Secure App Development
New Best Practices for Secure App Development
The transition from DevOps to SecDevOps is combining with the move toward cloud computing to create new challenges - and new opportunities - for the information security team. Download this report, to learn about the new best practices for secure application development.
Slideshows
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.

Dark Reading Radio
Archived Dark Reading Radio
In past years, security researchers have discovered ways to hack cars, medical devices, automated teller machines, and many other targets. Dark Reading Executive Editor Kelly Jackson Higgins hosts researcher Samy Kamkar and Levi Gundert, vice president of threat intelligence at Recorded Future, to discuss some of 2016's most unusual and creative hacks by white hats, and what these new vulnerabilities might mean for the coming year.