This version relies on it the webkit vulnerability as an entry point, meaning it will work on any PS5 (including PS5 Digital Edition) running firmware 4.03. Lower firmwares may work (although the exploit may need tweaking). Higher firmwares currently do not work (they are not vulnerable to the webkit exploit)
PS5 4.03 kernel exploit is here!
SpecterDev warns against this significant limitations this exploit. Above all:
- The exploit is quite unstable and in his experience it works about 30% of the time. If you try to run it, don’t give up, it may take multiple attempts before the exploit gets through
- Possibly more importantly, this exploit gives us read/write access but no execution! This means that at the moment there is no way to load and run binaries, everything is constrained within the framework of the ROP chain. However, the current implementation allows debug settings.
Specifically, from the exploit’s readme:
- Gets arbitrary read/write access and can run a simple RPC server for read/writes (or a dump server for large reads) (must edit your own address/port into the exploit file at lines 673-677 )
- Activates the debug settings menu (note: you have to exit and re-enter the settings completely to see it).
- Gets root privileges
- This exploit achieves read/write access, but no code execution. This is because we are currently unable to emit kernel code for gadgets as kernel .text pages are marked as eXecute Only Memory (XOM). Attempting to read kernel .text pointers causes panic!
- Same as above + the hypervisor (HV) that forces the kernel to be write-protected, this exploit will too cannot install patches or hooks in kernel spacewhich means no homebrew-related code for now.
- Clang-based fine-grain Control Flow Integrity (CFI) is in place and enforced.
- Supervisor Mode Access Prevention/Execution (SMAP/SMEP) cannot be disabled due to HV.
- The write primitive is somewhat restricted since bytes 0x10–0x14 must be zero (or a valid network interface).
- The stability of the exploit is currently poor. More on that below.
- With a successful run Quit the browser with the circle button, the PS button panics for a currently unknown reason.
The stability of this exploit is around 30% and has several potential bugs. In order of observed decreasing probability:
- stage 1 causes more than one UAF due to failing to catch one or more in the reclamation, resulting in a latent corruption that causes a panic some time later.
- Level 4 finds the overlap/victim socket, but the pktopts are the same as those of the master socket, resulting in the “read” primitive just reading back the pointer you’re trying to read, instead of the contents of that pointer. This needs to be improved and fixed if possible as it is really annoying.
- stage 1‘s attempt to reclaim the UAF fails and something else steals the pointer, causing immediate panic.
- The kqueue leak fails and finds no recognized kernel .data pointer.
In other words, this version is only useful for hackers or people curious to break into the inside of the PS5. Note, however, that despite its limitations, this is the first-ever public release of such a powerful hack for the PS5, meaning new discoveries are bound to happen!
PS5 IPV6 exploit showcase video
Scene member Echo Stretch managed to run the exploit and provide us with a video of it in action as seen below. In the video you can see how to unlock the debug menu and package installer on PS5
— Echo Stretch (@StretchEcho) October 3, 2022
Download and run
You can Download the hack here.
you will need python to run SpecterDev’s implementation and you will be running a web server on your local PC that your PS5 can access.
- Configure fakedns via
manuals.playstation.netto the IP address of your PC
- Run Fake DNS:
python fakedns.py -c dns.conf
- Run HTTPS server:
- Go into advanced PS5 network settings and set the primary DNS to your PC’s IP address and leave the secondary as is
- Sometimes the manual still won’t load and requires a reboot, not sure why that’s really weird
- In the settings go to the user guide and accept the prompt for untrusted certificates, run it
- Optional: Run rpc/dump server scripts (Note: address/port must be replaced in binary form in Exploit.js)
This is an evolving story as more people will test and report on this hack in the coming days, so stay tuned!