It appears there is a new release but it can be considered as an "old release" coming to the PS4 Soon, UPDATE: the exploit has been released . A couple months ago we seen Team FailOverflow release the breadcrumbs to exploit v4.05 firmware with the details reveled on there blog ": The First PS4 Kernel Exploit: Adieu" Since that time developer SpecterDev has been on a mission to put the pieces together for a workable jailbreak (not an easy task by any means) on the PS4 (4.05 firmware)., Over the course of the past several months SpecterDev has spent many hours of work to get this exploit stable state usable state for anyone interested. He has done amazing work for the PS4 development community is a vital step forward for the PS4. Now 1.76 is not the only window for the PS4 but also 4.05 provides a new window that is now easier to obtain, but will this be enough to launch the PS4 Homebrew Scene to a new level?
In my personal opinion i think we have another step or two before the PS4 Scene breaksout Personally I am not as excited about this exploit as some are from an end-user perspective, i do not think this will be a "golden firmware" just as i did not believe 1.76 ever was, both exploits have came to late in the PS3 life-cycle. Just as Team Fail0verflow themselves suggested in closing when they first detailed this 4.05 window and i quote "And so we say goodbye to a nice exploit." . As we can be extremely thankful for the contributions from Team fail0verflow we can also gather through comments and actions that they will not be the ones to release an exploit themselves or be the ones to give the fuel to something current, i could be wrong here but this is what I have gathered. So this exploit originating from them i would say does show there is a bit of steam knock off the exploit potential impact for launching a community, I think this is a great step forward but i do not think a 2nd PS4 is needed quite yet, i think there will be more to come as times passes, but that is your choice and i can only offer a different perspective then what others have been given, i would just point to my track record on being correct in many of these situation ;p . This is exciting on many levels but not sure its worth buying a 2nd PS4..?..?..
In my personal opinion i think we have another step or two before the PS4 Scene breaksout Personally I am not as excited about this exploit as some are from an end-user perspective, i do not think this will be a "golden firmware" just as i did not believe 1.76 ever was, both exploits have came to late in the PS3 life-cycle. Just as Team Fail0verflow themselves suggested in closing when they first detailed this 4.05 window and i quote "And so we say goodbye to a nice exploit." . As we can be extremely thankful for the contributions from Team fail0verflow we can also gather through comments and actions that they will not be the ones to release an exploit themselves or be the ones to give the fuel to something current, i could be wrong here but this is what I have gathered. So this exploit originating from them i would say does show there is a bit of steam knock off the exploit potential impact for launching a community, I think this is a great step forward but i do not think a 2nd PS4 is needed quite yet, i think there will be more to come as times passes, but that is your choice and i can only offer a different perspective then what others have been given, i would just point to my track record on being correct in many of these situation ;p . This is exciting on many levels but not sure its worth buying a 2nd PS4..?..?..
-
Summary
PS4 4.05 Kernel Exploit
In this project you will find a full implementation of the "namedobj" kernel exploit for the PlayStation 4 on 4.05. It will allow you to run arbitrary code as kernel, to allow jailbreaking and kernel-level modifications to the system. . This exploit does include a loader that listens for payloads on port 9020 and will execute them upon receival.
You can find fail0verflow's original write-up on the bug here, you can find my technical write-up which dives more into implementation specificshere(this is still in progress and will be published within the next few days).
Patches Included
The following patches are made by default in the kernel ROP chain:
- Disable kernel write protection
- Allow RWX (read-write-execute) memory mapping
- Dynamic Resolving (sys_dynlib_dlsym) allowed from any process
- Custom system call #11 (kexec()) to execute arbitrary code in kernel mode
- Allow unprivileged users to call setuid(0) successfully. Works as a status check, doubles as a privilege escalation.
Notes
- This exploit is actually incredibly stable at around 95% in my tests. WebKit very rarely crashes and the same is true with kernel.
- I've built in a patch so the kernel exploit will only run once on the system. You can still make additional patches via payloads.
- A custom syscall is added (#11) to execute any RWX memory in kernel mode, this can be used to execute payloads that want to do fun things like jailbreaking and patching the kernel.
- An SDK is not provided in this release, however a barebones one to get started with may be released at a later date.
- I've released a sample payload here that will make the necessary patches to access the debug menu of the system via settings, jailbreaks, and escapes the sandbox.
Contributors
I was not alone in this exploit's development, and would like to thank those who helped me along the way below.
- qwertyoruiopz
- Flatz
- CTurt
- Anonymous
Great news for the PS4,this is a great step forward for development but i caution people getting too excited about this and running out to buy a new PS4.
Personally I will get excited when we see a CURRENT FIRMWARE exploited, That will be the start to the Explosion of PS4 Homebrew IMO.
Update: via @Red: Much like ps3xploit I have hosted this files for others to use, in case anyone would like to mess around with this but doesnt feel like hosting the files themselves. http://redthetrainer.com/ps4/
Source(s): github.com/Cryptogenic
twitter.com/SpecterDev / Reddit.com
Last edited:
on the vita, you can manipulate the xml file. it's how I updated mine\ without signing in and updating past 3.60. 
I'm blocking several urls with the wii u, but it also blocks the eshop, you can get around that with nnu patcher. btw, on the ;ps4, blocking updates tutorial - you can still connect to the internet to run the exploit. I've tested it with the 4.07 web exploit. 
