Risk
8/23/2011
09:53 AM
50%
50%

Apple: Stop Tracking iOS Users By Device IDs

Documentation changes to the iOS 5 beta tell developers to track users via their own applications, not the serial number associated with each device.

11 iPad Apps For Better Collaboration
Slideshow: 11 iPad Apps For Better Collaboration
(click image for larger view and for slideshow)
Apple has instructed third-party developers to cease tracking iPhone, iPad, and iPod Touch users via the unique serial number associated with each one of its hardware devices. Widespread use of the tracking technique had raised privacy concerns and triggered multiple lawsuits against Apple.

In particular, new language in the documentation for iOS 5--the forthcoming version of Apple's mobile OS--informs developers that tracking via the unique device identifier (UDID) has become deprecated. That's developer-speak for "we no longer encourage you to use this feature."

"Instead, create a unique identifier specific to your app," according to Apple's documentation. As that suggests, applications will still be able to track users. But deprecating UDID would make it more difficult for businesses that track user behavior online, such as advertising firms, to track a single person's behavior across different applications. Furthermore, since Apple vets all applications--via its AppStore "walled garden" model--it will be able to enforce UDID restrictions.

Does Apple's restriction on the use of UDID by third-party developers mean that Apple itself will cease using UDID? Apple wasn't immediately available to respond to that question.

Research suggests that use of UDID for tracking individual Apple iOS device users is widespread. According to a 2010 study, for example, 68% of tested iPhone apps, when they launched, shared a device's UDID with a server--connected to the application developer, or with an advertising network--while 18% returned unknown, encrypted data back to a server.

Apple has seen multiple lawsuits arise from its use of UDID. For example, the company was sued in a January class action lawsuit for transmitting data to third parties that could be used to track device users without their consent, allegedly in violation of state and federal privacy laws.

According to the related complaint, "Apple allows the UDID to be displayed to application developers, and allows the downloaded applications access to the user's browsing history each time the user clicks on an advertisement or application appearing on their mobile device." Furthermore, noted the complaint, users can't block the use of UDID by iOS applications.

Apple's iOS documentation change was reported by TechCrunch Friday, which obtained a copy of Apple's developer documentation, which is only available to registered developers.

In discussions there, developers reacted in various ways, with some noting that after a feature becomes deprecated, it typically doesn't disappear for at least a few more versions of an OS. Others, however, lamented that without UDID it would be more difficult to track users who installed their applications on multiple devices, perhaps in violation of licensing agreements. Some, however, noted that UDID wasn't the only way to track a device, and acknowledged that UDID had been widely abused as a user-tracking technique.

Information about iOS 5, which has been in beta since June, has been trickling out, most notably via developers sharing their questions and comments via online forums. Apple has been releasing a new build of the beta OS about every two weeks. The final, production version, is due out this fall.

Automation and orchestration technologies can make IT more efficient and better able to serve the business by streamlining common tasks and speeding service delivery. In this report, we outline the potential snags and share strategies and best practices to ensure successful implementation. Download our report here. (Free registration required.)

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
Five Emerging Security Threats - And What You Can Learn From Them
At Black Hat USA, researchers unveiled some nasty vulnerabilities. Is your organization ready?
Flash Poll
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2013-7445
Published: 2015-10-15
The Direct Rendering Manager (DRM) subsystem in the Linux kernel through 4.x mishandles requests for Graphics Execution Manager (GEM) objects, which allows context-dependent attackers to cause a denial of service (memory consumption) via an application that processes graphics data, as demonstrated b...

CVE-2015-4948
Published: 2015-10-15
netstat in IBM AIX 5.3, 6.1, and 7.1 and VIOS 2.2.x, when a fibre channel adapter is used, allows local users to gain privileges via unspecified vectors.

CVE-2015-5660
Published: 2015-10-15
Cross-site request forgery (CSRF) vulnerability in eXtplorer before 2.1.8 allows remote attackers to hijack the authentication of arbitrary users for requests that execute PHP code.

CVE-2015-6003
Published: 2015-10-15
Directory traversal vulnerability in QNAP QTS before 4.1.4 build 0910 and 4.2.x before 4.2.0 RC2 build 0910, when AFP is enabled, allows remote attackers to read or write to arbitrary files by leveraging access to an OS X (1) user or (2) guest account.

CVE-2015-6333
Published: 2015-10-15
Cisco Application Policy Infrastructure Controller (APIC) 1.1j allows local users to gain privileges via vectors involving addition of an SSH key, aka Bug ID CSCuw46076.

Dark Reading Radio
Archived Dark Reading Radio
Cybercrime has become a well-organized business, complete with job specialization, funding, and online customer service. Dark Reading editors speak to cybercrime experts on the evolution of the cybercrime economy and the nature of today's attackers.