| Welcome, Guest |
You have to register before you can post on our site.
|
| Online Users |
There are currently 207 online users. » 0 Member(s) | 206 Guest(s) Bing
|
| Latest Threads |
She's in your city and sh...
by torla 07-26-2026, 04:18 AM
|
The IMPOSSIBLE Happened! ...
by GeoSn0w 06-22-2026, 04:03 AM
|
@pump_upp - best crypto p...
by torla 04-16-2026, 01:23 PM
|
datebest.net - visit webs...
by torla 04-10-2026, 01:11 PM
|
Girls In Your Town - No S...
by torla 04-06-2026, 06:39 PM
|
Girls In Your Town - No V...
by torla 04-04-2026, 11:52 PM
|
New DarkSword Kernel Expl...
by GeoSn0w 03-24-2026, 10:49 PM
|
iPhone 15 - iPhone 11 Cor...
by pliku 03-15-2026, 01:17 PM
|
Great iOS Jailbreak NEWS:...
by pliku 03-15-2026, 12:56 PM
|
Great JAILBREAK News: Mas...
by GeoSn0w 02-04-2026, 05:46 AM
|
|
|
iOS 12.2 / 12.1.4 / 12.1.3 Great JAILBREAK News: New tfp0 Exploit Developed! |
|
Posted by: GeoSn0w - 06-29-2019, 11:28 PM - Forum: Jailbreak News
- Replies (13)
|
 |
In today's video, we have great news to discuss about yet another tfp0 kernel exploit that was just announced a few hours ago by Ned Williamson of Google Project Zero. Ned has announced that he has successfully achieved #tfp0 (Kernel Task Port / Task for Pid 0) on his iPhone 6S Plus running iOS 12.2, by exploiting a vulnerability he has found back in April / May 2019 and was patched in iOS 12.3. As you probably figured out, the vulnerability can only be used on iOS 12.2 and lower which means a release of this exploit could render a Jailbreak for iOS 12.1.3, iOS 12.1.4 and iOS 12.2. Unfortunately, iOS 12.3 and iOS 12.3.1 are not supported.
Apple has included the vulnerability in their Security Content for iOS 12.3 back on May 13, so at this point, the vulnerability is patched. At that time, it was a simple bug that if exploited could cause a kernel panic. Ned has crafted a tfp0 exploit on top of that bug with help from Brandon Azad of Google Project Zero achieving one of the goals he had for over a decade, Ned states. There is currently no info on a future release, but with the bug long patched and reported, Ned might as well release it. As always, staying on iOS 12.2 and lower might pay off more than updating to useless buggy betas or to the latest version.
|
|
|
|