This new tool can jailbreak any iPhone running iOS 11 or later

This new tool can jailbreak any iPhone running iOS 11 or later

This new tool can jailbreak any iPhone running iOS 11 or later

Overall, Apple has always showcased its new iOS at the developer conference in June, which this time will be held on the 22nd in an online event. So this time, hackers took advantage of a security hole, which Apple is not yet aware of, and this allowed the release of a jailbreak for all current versions of iOS - from 11 to 13.5. Apparently, hackers managed to get their hands on a pre-release version of the upcoming iOS 14 way ahead of its launch, as Motherboard reported.

IPhone and iPad users reported that ever since the new iOS 13.5 updates rolled out, majority are facing a similar issue.

Apple released iOS 13.5 and iPadOS 13.5 to the public last week, but users have already discovered two bugs that seem to have something to do with the app's certificates.

"Utilizing native system sandbox exceptions, security remains intact while enabling access to jailbreak files", according to unc0ver, meaning installing the new jailbreak will likely not compromise iOS' sandbox protections.

There are obviously things to bear in mind both before and after jailbreaking your iPhone.

If you are an iPhone user and are receiving updates for dozens of apps unexpectedly, you are not the only one experiencing it.

In Wired's report on the latest jailbreak, the publication warned that users should not attempt to use the tool unless they are "absolutely sure" that they know what they are doing.

The iOS 13.5 jailbreak is another knock on what was once considered an impenetrable fortress of security for Apple. Unlike checkra1n, unc0ver uses a zero-day exploit that hasn't been used in iOS jailbreaks since iOS 8. Also, Apple was not informed about this vulnerability before. However, the entire community has yet to fully inspect and assess the jailbreak tool or the team's claims about the security protections as it isn't open-source, making it hard to analyze.

It seems that right now there is no workaround or fix for this, or whether this is a cloud/server-side problem, or whether this is indeed a bug built into iOS 13.5, which would require a patch.

Related news

[an error occurred while processing the directive]