iPhone 11, 11 Pro, 11 Pro Max iOS 13.3 jailbreak exploit has been at last discharged by Brandon Azad. Here are the subtleties.
Security specialist Brandon Azad has finished on his promise in what appears to be record time. Only a couple of days back, he took to Twitter to affirm that he would discharge a proof-of-idea misuse at the piece level. Today, that PoC has shown up and it passes by the name of OOB Timestamp.
His unique tweet affirmed that he would be discharging a proof-of-idea that would work with iPhone 11 running iOS 13.3. Now, a subsequent tweet has affirmed the discharge and gives a little extra data on what it is that he has been chipping away at:
“oob_timestamp is a proof-of-concept research exploit that exports the kernel task port on iOS 13.3 17C54 on the iPhone12,3. See README and oob_timestamp.c for details. bugs.chromium.org/p/project-zero…“
Azad has by and by referenced the iPhone12,3/17C54 equipment/programming mix in his tweet, however, this is likely because of the way that his PoC depends on that mix and is likely not down to the way that OOB Timestamp just backings the iPhone 11 and iOS 13.3. Tweets and data discharged by Unc0ver developer Pwn20wnd have everything except affirmed that his group can probably do something amazing to update the Unc0ver jailbreak to expand this tfp0-competent endeavor and make it work for them by offering support for extra devices.
If you are keen on this kind of research and might want to investigate the more specialized parts of Azad’s work, then you can locate the full review and clarification of the bug directly here. If you are just keen on whether this can be taken to the following level and used inside an updated jailbreak arrangement, then the present signs all look extremely positive.
If you’re interested in bootstrapping iOS kernel security research on A13, keep an iPhone 11 on iOS 13.3. I will be releasing a proof-of-concept exploit that provides kernel read/write on iPhone12,3 17C54.
— Brandon Azad (@_bazad) February 4, 2020
Developer Pwn20wnd has just shot-his-shot and exhorted that he will be paying attention to OOB Timestamp when it was discharged. Also, now that it is discharged, well we can just expect that the Unc0ver group will commit time and exertion into redesigning the tool to offer extra similarity on the rear of this PoC discharge.
As of now, there is no “estimated time of arrival child,” which implies that we should all simply kick back and retain what data channels into the open space identifying with progress right now.