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.

Vulnerabilities / Threats

8/20/2019
05:21 PM
Connect Directly
Twitter
LinkedIn
RSS
E-Mail
50%
50%

Apple Misstep Leaves iPhones Open to Jailbreak

Newest version of iOS contains a critical bug that the company had previously already patched.

In a somewhat uncharacteristic blunder, Apple has left iPhones running iOS 12.4, the latest version of its mobile operating system, open to a security bug that the company previously had fixed.

One security researcher has quickly taken advantage of the opportunity to develop and publicly release an exploit for jail-breaking iPhones running iOS 12.4.

This is believed to be the first time in several years that a jailbreak for the most updated version of iOS has become publicly available before a patch for it has been released. Typically, such unpatched Apple exploits can fetch hundreds of thousands of dollars and sometimes, even millions of dollars in dark markets.

Jailbreaking gives iPhone users a way to get past Apple's restrictions and install unapproved applications and services on their devices or to change settings that they normally wouldn't be able to change.

Some security researchers are concerned that attackers could use the unpatched exploit to try and launch attacks on iPhone users via tainted apps, remote exploits, and other methods. Others believe such concerns are overblown.

Apple did not respond immediately to a request seeking comment on the issue or on what the company is doing to address it. But some believe it will issue an update quickly, considering the risks to iPhone users.

News of the latest issue somewhat ironically comes just days after Apple announced a major bug bounty program with big incentives for researchers who find bugs in some of the company's products.

"Apple has historically been very expedient in patching vulnerabilities, so I would expect to see an update pretty soon," says Terence Jackson, chief information security officer at Thycotic. "But until then, iPhone users should exercise a little extra discretion when downloading applications and opening links in email, iMessages, or a browser.”

According to Motherboard, the first to report on the issue, security researchers recently discovered that in developing iOS 12.4 Apple had inadvertently reopened a remote code execution bug (CVE-2019-8605) that the company had patched in the previous iOS 12.3 version.  Google Project Zero researcher Ned Williamson reported that issue to Google earlier this year. Apple had described the bug as a "use after free issue [that] was addressed with improved memory management."

Apple's iOS 12.4 among other things contained a fix for another critical vulnerability that allowed attackers to gain access to iPhones via a malicious iMessage.

Muted Risk

Aaron Zander, head of IT at HackerOne, says that the new jailbreak is a "very cool thing" considering how unusual they have become. However, since the vulnerability and the exploit are now public, the associated risks are more manageable. "This is way different than Apple being completely unaware of the vulnerability and allowing exploits to run wild," Zander says.

The bigger issue is how frequently such missteps happen, he says. Typically, companies develop their major software versions separately from their minor releases - for instance, an X.4 version versus an X.4.1 release. In merging minor and major releases, sometimes changes get missed. "This unfortunately happens all the time, which demonstrates why retesting is so important," Zander notes.

Chris Morales, head of security analytics at Vectra, says some people are likely more excited that they can jailbreak their iPhone while still having the latest version of iOS, and aren't worried about the security risks. "The risk here is that a malicious app can get into the Apple store and exploit a vulnerability. While feasible, it is most likely not a regular occurrence or any more of a risk than already existed," Morales says.

Related Content:

Check out The Edge, Dark Reading's new section for features, threat data, and in-depth perspectives. Today's top story: "5 Ways to Improve the Patching Process."

Jai Vijayan is a seasoned technology reporter with over 20 years of experience in IT trade journalism. He was most recently a Senior Editor at Computerworld, where he covered information security and data privacy issues for the publication. Over the course of his 20-year ... View Full Bio

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Data Leak Week: Billions of Sensitive Files Exposed Online
Kelly Jackson Higgins, Executive Editor at Dark Reading,  12/10/2019
Lessons from the NSA: Know Your Assets
Robert Lemos, Contributing Writer,  12/12/2019
4 Tips to Run Fast in the Face of Digital Transformation
Shane Buckley, President & Chief Operating Officer, Gigamon,  12/9/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
The Year in Security: 2019
This Tech Digest provides a wrap up and overview of the year's top cybersecurity news stories. It was a year of new twists on old threats, with fears of another WannaCry-type worm and of a possible botnet army of Wi-Fi routers. But 2019 also underscored the risk of firmware and trusted security tools harboring dangerous holes that cybercriminals and nation-state hackers could readily abuse. Read more.
Flash Poll
Rethinking Enterprise Data Defense
Rethinking Enterprise Data Defense
Frustrated with recurring intrusions and breaches, cybersecurity professionals are questioning some of the industrys conventional wisdom. Heres a look at what theyre thinking about.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-19807
PUBLISHED: 2019-12-15
In the Linux kernel before 5.3.11, sound/core/timer.c has a use-after-free caused by erroneous code refactoring, aka CID-e7af6307a8a5. This is related to snd_timer_open and snd_timer_close_locked. The timeri variable was originally intended to be for a newly created timer instance, but was used for ...
CVE-2014-8650
PUBLISHED: 2019-12-15
python-requests-Kerberos through 0.5 does not handle mutual authentication
CVE-2014-3536
PUBLISHED: 2019-12-15
CFME (CloudForms Management Engine) 5: RHN account information is logged to top_output.log during registration
CVE-2014-3643
PUBLISHED: 2019-12-15
jersey: XXE via parameter entities not disabled by the jersey SAX parser
CVE-2014-3652
PUBLISHED: 2019-12-15
JBoss KeyCloak: Open redirect vulnerability via failure to validate the redirect URL.