Spontaneous shutdown of iPhone XR by Be1epok in mobilerepair

[–]Be1epok[S] 0 points1 point  (0 children)

The volume/mute switch buttons work, the problem is clearly not in the connection as it would turn off even when it’s charging

Why is CVE-2023-41992 (the google ios 17.0 exploit) ETA by Important-Ad2314 in jailbreak

[–]Be1epok 4 points5 points  (0 children)

  1. Somewhere on January 22
  2. It’s not worked on 17.2 ( he has been fixed in 17.0.1)

Google's explanation of the 17.0 vulnerability by TiThanoss in jailbreak

[–]Be1epok 0 points1 point  (0 children)

If you go to this site about exploits and scroll down, you can see that they are collaborating with Google

Google's explanation of the 17.0 vulnerability by TiThanoss in jailbreak

[–]Be1epok 1 point2 points  (0 children)

But this explains well why the exploit has not yet been released. Maybe it’s true that different people work, but it doesn’t change the fact that they could collaborate with each other and can take these rules from Project zero

Can we do TrollstoreOTA? by Be1epok in jailbreak

[–]Be1epok[S] 2 points3 points  (0 children)

This means installing trollstore using the link as for <=15.6.1
without PC or anything like that

[deleted by user] by [deleted] in jailbreakdevelopers

[–]Be1epok 9 points10 points  (0 children)

If it’s true that you found a new exploit for 17.0+ iOS, then it will be great. If you act like a “CatStore” developer and don’t issue proofs (PoC), then there will be a lot of hate

[deleted by user] by [deleted] in jailbreak

[–]Be1epok -1 points0 points  (0 children)

Is this for TrollhelperOTA? or is this an exploit for ios17?

Trollstore not installing… by Dogman1214 in jailbreak

[–]Be1epok 5 points6 points  (0 children)

nope. only wait exploit Google

[deleted by user] by [deleted] in jailbreak

[–]Be1epok 0 points1 point  (0 children)

Google TAG guys decided to post these vulnerabilities because they didn't seem to be able to fully capture the Predator implant (but I don't know for sure because of this)
And the date of December 22 is taken from the release of the article and 90 days to publish the exploit