Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Risk

2/11/2011
10:39 AM
George V. Hulme
George V. Hulme
Commentary
50%
50%

Think That iPhone Isn't A Corporate Security Risk?

If so, you had better think again. Researchers have shown how the passwords on the iPhone can be revealed in less than six minutes.

If so, you had better think again. Researchers have shown how the passwords on the iPhone can be revealed in less than six minutes.Security managers and CIOs alike have enough to worry about when it comes to securing mobile devices. They certainly didn't need to learn that many of the passwords stored on an iPhone can be had in about half the time it takes to hard boil an egg.

But that's exactly what researchers in Germany just disclosed, and it's raising eyebrows. The cracking technique requires attackers have physical access to the device. Considering how many mobile devices are lost every year, that's not much consolation in this case.

These researchers conducted their attack against an iPhone 4 (not jailbroken) equipped with the most recent firmware. iPads are susceptible, too. Researchers said. The passwords recovered are those used for wifi networks, some applications (depending on how they were programmed) as well as the password credentials to e-mail and VPNs.

Here's a video demonstration:

The tools and techniques needed to conduct the necessary jailbreak and file access are widely available. What this team did was figure out how to extract the actual passwords.

The researchers' full paper, Lost iPhone? Lost Passwords! Practical Consideration of iOS Device Encryption Security is available here in .pdf format.

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

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
COVID-19: Latest Security News & Commentary
Dark Reading Staff 5/28/2020
Stay-at-Home Orders Coincide With Massive DNS Surge
Robert Lemos, Contributing Writer,  5/27/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: Can you smell me now?
Current Issue
How Cybersecurity Incident Response Programs Work (and Why Some Don't)
This Tech Digest takes a look at the vital role cybersecurity incident response (IR) plays in managing cyber-risk within organizations. Download the Tech Digest today to find out how well-planned IR programs can detect intrusions, contain breaches, and help an organization restore normal operations.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-11844
PUBLISHED: 2020-05-29
There is an Incorrect Authorization vulnerability in Micro Focus Service Management Automation (SMA) product affecting version 2018.05 to 2020.02. The vulnerability could be exploited to provide unauthorized access to the Container Deployment Foundation.
CVE-2020-6937
PUBLISHED: 2020-05-29
A Denial of Service vulnerability in MuleSoft Mule CE/EE 3.8.x, 3.9.x, and 4.x released before April 7, 2020, could allow remote attackers to submit data which can lead to resource exhaustion.
CVE-2020-7648
PUBLISHED: 2020-05-29
All versions of snyk-broker before 4.72.2 are vulnerable to Arbitrary File Read. It allows arbitrary file reads for users who have access to Snyk's internal network by appending the URL with a fragment identifier and a whitelisted path e.g. `#package.json`
CVE-2020-7650
PUBLISHED: 2020-05-29
All versions of snyk-broker after 4.72.0 including and before 4.73.1 are vulnerable to Arbitrary File Read. It allows arbitrary file reads to users with access to Snyk's internal network of any files ending in the following extensions: yaml, yml or json.
CVE-2020-7654
PUBLISHED: 2020-05-29
All versions of snyk-broker before 4.73.1 are vulnerable to Information Exposure. It logs private keys if logging level is set to DEBUG.