Risk
8/3/2010
11:20 PM
George V. Hulme
George V. Hulme
Commentary
Connect Directly
RSS
E-Mail
50%
50%

On iPhone, Jailbreaking, And Security

It may not be the fashionable decision, but I choose not to jailbreak my iPhone. That's primarily out of security concerns. However, it turns out that Jailbreaking (read: pwning) an iPhone is now as simple as visiting a web page.

It may not be the fashionable decision, but I choose not to jailbreak my iPhone. That's primarily out of security concerns. However, it turns out that Jailbreaking (read: pwning) an iPhone is now as simple as visiting a web page.That's right. The Dev-Team, the group that made it relatively easy to jailbreak previous versions of the iPhone have done it again. This time, however, iPhone users need only visit a website, www.jailbreakme.com, from their mobile device to have the jailbreak completed.

According to this security advisory there are two vulnerabilities that affect Apple iOS for iPhone, iPad, and iPod that are making this possible:

The first issue is caused by a memory corruption error when processing Compact Font Format (CFF) data within a PDF document, which could be exploited by attackers to execute arbitrary code by tricking a user into visiting a specially crafted web page using Mobile Safari.

The second vulnerability is caused by an error in the kernel, which could allow attackers to gain elevated privileges and bypass sandbox restrictions.

Note: These flaws are currently being exploited by jailbreakme to remotely jailbreak Apple devices.

This makes the www.jailbreakme.com Web site work much the same way a drive-by Web exploit works, but only with permission of the user. So maybe we dub this service a "drive-through" exploit :-)

Now, thanks to a recent decision by the Copyright Office and Librarian of Congress regarding the Digital Millennium Copyright Act (DMCA) - jailbreaking one's iPhone is now legal. Though could result in losing your Apple warranty. While I welcome this DMCA decision, as we should be able to tinker with our gadgets, I do think this jailbreak method raises a security concern.

This is encouraging users to visit a web site to actually have their device hacked. I've no reason to believe that anything more is going on at jailbreakme.com than the rooting of the iOS devices - but exploiting these vulnerabilities does enable remote users to gain control of the device. So it's quite easy to see how malicious attackers could socially engineer users to "jailbreak" their device and also insert a keystroke logger, traffic sniffer, of bot onto the iPhone, iPod, or iPad.

Just as it's not a great idea for credit card companies and banks to e-mail users links back to their sites within e-mails, as it makes it easier for phishers to lure customers to malicious sites: it's not a good idea to have people going to web sites to have their phones jailbroken.

Speaking of malicious attackers: These vulnerabilities make it very easy to hack an iOS powered device by merely opening an Adobe PDF file. So I'd suggest avoiding them completely on the Web until Apple issues a patch.

Apple is currently "looking into" the report of the software vulnerabilities, according to this post by AppleInsider. I'd expect a patch to become available soon.

For my security and technology tweets throughout the day, find me on Twitter.

Comment  | 
Print  | 
More Insights
Register for Dark Reading Newsletters
White Papers
Flash Poll
Current Issue
Cartoon
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2013-6335
Published: 2014-08-26
The Backup-Archive client in IBM Tivoli Storage Manager (TSM) for Space Management 5.x and 6.x before 6.2.5.3, 6.3.x before 6.3.2, 6.4.x before 6.4.2, and 7.1.x before 7.1.0.3 on Linux and AIX, and 5.x and 6.x before 6.1.5.6 on Solaris and HP-UX, does not preserve file permissions across backup and ...

CVE-2014-0480
Published: 2014-08-26
The core.urlresolvers.reverse function in Django before 1.4.14, 1.5.x before 1.5.9, 1.6.x before 1.6.6, and 1.7 before release candidate 3 does not properly validate URLs, which allows remote attackers to conduct phishing attacks via a // (slash slash) in a URL, which triggers a scheme-relative URL ...

CVE-2014-0481
Published: 2014-08-26
The default configuration for the file upload handling system in Django before 1.4.14, 1.5.x before 1.5.9, 1.6.x before 1.6.6, and 1.7 before release candidate 3 uses a sequential file name generation process when a file with a conflicting name is uploaded, which allows remote attackers to cause a d...

CVE-2014-0482
Published: 2014-08-26
The contrib.auth.middleware.RemoteUserMiddleware middleware in Django before 1.4.14, 1.5.x before 1.5.9, 1.6.x before 1.6.6, and 1.7 before release candidate 3, when using the contrib.auth.backends.RemoteUserBackend backend, allows remote authenticated users to hijack web sessions via vectors relate...

CVE-2014-0483
Published: 2014-08-26
The administrative interface (contrib.admin) in Django before 1.4.14, 1.5.x before 1.5.9, 1.6.x before 1.6.6, and 1.7 before release candidate 3 does not check if a field represents a relationship between models, which allows remote authenticated users to obtain sensitive information via a to_field ...

Best of the Web
Dark Reading Radio
Archived Dark Reading Radio
This episode of Dark Reading Radio looks at infosec security from the big enterprise POV with interviews featuring Ron Plesco, Cyber Investigations, Intelligence & Analytics at KPMG; and Chris Inglis & Chris Bell of Securonix.