Risk
8/23/2011
09:53 AM
Connect Directly
RSS
E-Mail
50%
50%
Repost This

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
Register for Dark Reading Newsletters
White Papers
Flash Poll
Current Issue
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2013-5704
Published: 2014-04-15
The mod_headers module in the Apache HTTP Server 2.2.22 allows remote attackers to bypass "RequestHeader unset" directives by placing a header in the trailer portion of data sent with chunked transfer coding. NOTE: the vendor states "this is not a security issue in httpd as such."

CVE-2013-5705
Published: 2014-04-15
apache2/modsecurity.c in ModSecurity before 2.7.6 allows remote attackers to bypass rules by using chunked transfer coding with a capitalized Chunked value in the Transfer-Encoding HTTP header.

CVE-2014-0341
Published: 2014-04-15
Multiple cross-site scripting (XSS) vulnerabilities in PivotX before 2.3.9 allow remote authenticated users to inject arbitrary web script or HTML via the title field to (1) templates_internal/pages.tpl, (2) templates_internal/home.tpl, or (3) templates_internal/entries.tpl; (4) an event field to ob...

CVE-2014-0342
Published: 2014-04-15
Multiple unrestricted file upload vulnerabilities in fileupload.php in PivotX before 2.3.9 allow remote authenticated users to execute arbitrary PHP code by uploading a file with a (1) .php or (2) .php# extension, and then accessing it via unspecified vectors.

CVE-2014-0348
Published: 2014-04-15
The Artiva Agency Single Sign-On (SSO) implementation in Artiva Workstation 1.3.x before 1.3.9, Artiva Rm 3.1 MR7, Artiva Healthcare 5.2 MR5, and Artiva Architect 3.2 MR5, when the domain-name option is enabled, allows remote attackers to login to arbitrary domain accounts by using the corresponding...

Best of the Web