Vulnerabilities / Threats

3/21/2016
05:30 PM
Connect Directly
Twitter
RSS
E-Mail
100%
0%

iMessage Encryption Cracked, But Fixed In New iOS 9.3

While FBI fights with Apple over iPhone encryption, Johns Hopkins researchers find a weakness in secure IM on iOS, OSX.

A vulnerability in the encryption method used by iOS and OSX when transmitting iMessages would allow attackers to intercept messages and snoop on photos and videos, according to researchers at Johns Hopkins University today. The flaw was repaired in iOS 9.3, officially released today, and an update was also released for Mac OS X El Capitan v. 11 through v. 13.

Researchers provided some basics to the Washington Post. In the simulated attack, researchers targeted iPhones, and using an emulated Apple iCloud server, they obtained links to photos stored in iCloud sent by those phones, as well as 64-digit encryption keys.

From the Washington Post:

Although the students could not see the key’s digits, they guessed at them by a repetitive process of changing a digit or a letter in the key and sending it back to the target phone. Each time they guessed a digit correctly, the phone accepted it. They probed the phone in this way thousands of times.

“And we kept doing that,” [lead researcher and computer science professor Dr. Matthew Green] said, “until we had the key.”

According to the researchers' report, obtained by ThreatPost, the proof-of-concept attack took roughly 130,000 edits and 72 hours. An exploit to pilfer content from iMessages in-transit requires that the attacker already have have man-in-the-middle access. The vulnerability could also be used to decrypt content stored in undelivered iMessages -- which Apple stores on iCloud for up to 30 days -- but that would require that the attacker have already obtained access to the iCloud infrastructure, either via a separate exploit, or perhaps legal means like the FBI is currently pursuing.

This particular vulnerability would not help the FBI access the phone at the center of the controversy with Apple. However, Green commented to the Post:

“Even Apple, with all their skills — and they have terrific cryptographers — wasn’t able to quite get this right,” said Green, whose team of graduate students will publish a paper describing the attack as soon as Apple issues a patch. “So it scares me that we’re having this conversation about adding back doors to encryption when we can’t even get basic encryption right.”

“This does have a parallel with the FBI vs. Apple case," says Lamar Bailey, director of security research and development for cyber security company Tripwire, "as many technologists have speculated that the FBI could access the shooter's phone, if they decide to put in the effort. For example, the secure enclave can be backed up and the CPU serial number read so that the autowipe is bypassed or the encryption can be cracked offline. This is of course undesirable for the FBI as the process takes time and money on a much different scale from what it took when Apple could simply bypass the security measures of phones."

"This finding, not surprisingly, strengthens the argument that the government does not need backdoors -- there is always buggy software to lend them access, as aptly illustrated by Green's research," says Chenxi Wang, chief strategy officer for Twistlock. "This case - FBI vs. Apple - is merely FBI's ploy to establish a legal precedent. It has very little to do with whether the agency has the ability to hack the device." 

Sara Peters is Senior Editor at Dark Reading and formerly the editor-in-chief of Enterprise Efficiency. Prior that she was senior editor for the Computer Security Institute, writing and speaking about virtualization, identity management, cybersecurity law, and a myriad ... View Full Bio

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
jastroff
50%
50%
jastroff,
User Rank: Strategist
3/22/2016 | 6:54:09 AM
Nature of the Problem
When does this become a zero-sum game, if it hasn't already?

And when this bulkhead is conquered, what is the next trouble spot in the war against terrorism vis-a-vis technology?
6 Security Trends for 2018/2019
Curtis Franklin Jr., Senior Editor at Dark Reading,  10/15/2018
6 Reasons Why Employees Violate Security Policies
Ericka Chickowski, Contributing Writer, Dark Reading,  10/16/2018
Getting Up to Speed with "Always-On SSL"
Tim Callan, Senior Fellow, Comodo CA,  10/18/2018
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Latest Comment: Too funny!
Current Issue
Flash Poll
The Risk Management Struggle
The Risk Management Struggle
The majority of organizations are struggling to implement a risk-based approach to security even though risk reduction has become the primary metric for measuring the effectiveness of enterprise security strategies. Read the report and get more details today!
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2018-10839
PUBLISHED: 2018-10-16
Qemu emulator <= 3.0.0 built with the NE2000 NIC emulation support is vulnerable to an integer overflow, which could lead to buffer overflow issue. It could occur when receiving packets over the network. A user inside guest could use this flaw to crash the Qemu process resulting in DoS.
CVE-2018-13399
PUBLISHED: 2018-10-16
The Microsoft Windows Installer for Atlassian Fisheye and Crucible before version 4.6.1 allows local attackers to escalate privileges because of weak permissions on the installation directory.
CVE-2018-18381
PUBLISHED: 2018-10-16
Z-BlogPHP 1.5.2.1935 (Zero) has a stored XSS Vulnerability in zb_system/function/c_system_admin.php via the Content-Type header during the uploading of image attachments.
CVE-2018-18382
PUBLISHED: 2018-10-16
Advanced HRM 1.6 allows Remote Code Execution via PHP code in a .php file to the user/update-user-avatar URI, which can be accessed through an "Update Profile" "Change Picture" (aka user/edit-profile) action.
CVE-2018-18374
PUBLISHED: 2018-10-16
XSS exists in the MetInfo 6.1.2 admin/index.php page via the anyid parameter.