Hacking Official Kernel Exploit released for up to 4.05 by Fail0verflow

  • Thread starter Thread starter aos10
  • Start date Start date
  • Views Views 35,646
  • Replies Replies 148
  • Likes Likes 16
For end-user, nope. But if you got some RE background, combining the 4.0x webkit exploit and the kexploit you would be able to do things that used to be exclusively for 1.76.

A "nope", that I understand! The rest of your post, I have no idea. My skill level basically is: Downloading stuff to an SD card, shoving it into a Wii, you've successfully hacked a console.
 
Releasing a Kexploit doesn't instantly mean everyone can use it right off the bat. Why is this an issue for some people? The title really is fine, the exploit was released..
NO, it really wasn't. Someone wrote about it. Where is the release? Where is the entire code base or file to download? There is none. This isn't a release.
 
What are the chances of buying the PS4 pro standard edition (no games included) brand new being on a low firmware i.e 4.05 or lower? Im from the uk and Argos have them in stock. Thanks
 
Do all PS4 Pros come on under 4.06?

The Destiny 2 bundle comes with 4.70, while the regulars are 4.07+. Only the ones at launch came with 3.70 (for whatever reason). Think of it this way, the "Pro" came out in November 2016, and OFW 4.06 also came out in November 2016. After ~12 months on the shelves, all launch units are long gone.
 
The Destiny 2 bundle comes with 4.70, while the regulars are 4.07+. Only the ones at launch came with 3.70 (for whatever reason). Think of it this way, the "Pro" came out in November 2016, and OFW 4.06 also came out in November 2016. After ~12 months on the shelves, all launch units are long gone.

Thanks for the info. What would I have to lookout for on the box to know if its on 4.05 or less firmware? Pro and reg consoles.
 
The Destiny 2 bundle comes with 4.70, while the regulars are 4.07+. Only the ones at launch came with 3.70 (for whatever reason). Think of it this way, the "Pro" came out in November 2016, and OFW 4.06 also came out in November 2016. After ~12 months on the shelves, all launch units are long gone.
Ah darn that sucks, not at all interested for Destiny 2 on console but not even base model is that low. RIP
 
I think my PS4 Pro was like 4.13 or something at those lines. It wasn't 3.X atleast.
 
I hear SpecterDev is messing around with this. Check his twitter. It's cool, my PS4 is still on 3.55. Not sure if it was worth the wait for me...
 
i have a 2nd pro, unopened, waiting for almost a year on 3.70, it might be time for it to be awakened soon
Ehh that's a bit scary, are spam bots getting more advanced? Copying posts to raise their post count, to seem legit?

i have a 2nd pro, unopened, waiting for almost a year on 3.70, it might be time for it to be awakened soon :D
 
Fuck Square. The last game I played on my PS4 was FFXV so I updated to 4.06 before updating that stupid game. Hopefully there will be something for later FWs as I haven't had much of a reason to touch the console. I do want to play Horizon eventually.
 
I can't believe this.
bought a PS4 PRO 3 weeks ago to have a LOW FW. It's 4.07 out of box

I was using my up to date PS4 FAT and waiting for news about hacking.

didn't want to play with my PS4 PRo becouse everything i gaming on need last FW. and becouse i have no 4k TV to make me try my PS4 PRO.

i'm so sad,!
 
I'm on 4.06 firmware and read this on the blog post:

The namedobj exploit was present and exploitable (albeit using a slightly different method than described here) until it was fixed in firmware version 4.06. This vulnerability was also found and exploited by (at least) Chaitin Tech, so props to them! Taking a quick look at the 4.07 kernel, we can see a straightforward fix (4.06 is assumed to be identical - only had 4.07 on hand while writing this post):

Whats this straightforward fix they are talking about? Will the exploit come to 4.06 in the future? Thanks
 
I'm on 4.06 firmware and read this on the blog post:

The namedobj exploit was present and exploitable (albeit using a slightly different method than described here) until it was fixed in firmware version 4.06. This vulnerability was also found and exploited by (at least) Chaitin Tech, so props to them! Taking a quick look at the 4.07 kernel, we can see a straightforward fix (4.06 is assumed to be identical - only had 4.07 on hand while writing this post):

Whats this straightforward fix they are talking about? Will the exploit come to 4.06 in the future? Thanks

Nope, the method was fixed with an extra line of code to check if the type id is 0x4000, which was the value the exploit depended upon. In short, if you are not equal or lower than 4.05, you have to wait for another time.
 
I'm on 4.06 firmware and read this on the blog post:

The namedobj exploit was present and exploitable (albeit using a slightly different method than described here) until it was fixed in firmware version 4.06. This vulnerability was also found and exploited by (at least) Chaitin Tech, so props to them! Taking a quick look at the 4.07 kernel, we can see a straightforward fix (4.06 is assumed to be identical - only had 4.07 on hand while writing this post):

Whats this straightforward fix they are talking about? Will the exploit come to 4.06 in the future? Thanks

There is a good one for 4.50 - 4.55 that hasnt been released yet.
 
  • Like
Reactions: peteruk

Site & Scene News

Popular threads in this forum