Category PS4 Jailbreaking       Thread starter Thread starter PSXHAX       Date / timeStart date Dec 3, 2023 at 7:10 PM       Replies 229      
Status
Not open for further replies.
This weekend PS4 Scene developer @CelesteBlue announced on Twitter news of a PSFree WebKit Exploit for PS4 6.00 to 9.60 crediting Sergei Glazunov and Maddie Stone (Twitter) of Project Zero for discovering the vulnerability, anonymous for writing the PSFree Exploit and himself for testing, porting and improvements alongside a QuickHEN PS4 collection incoming of WebKit exploits for PlayStation 4 System Software versions between 3.15 and 9.60 with Kernel exploits between 3.15 and 9.00 only albeit requiring more work and Laps3c0re which is a port of the Lapse kernel exploit implementation by abc using Mast1c0re by McCaulay as an entry point and Y2JB Userland code execution by Gezine using the PS5 YouTube (USA) app v1.03 PKG crediting Remote_Lua_Loader. 🔥

Download: psfree-1.2.0.zip (39.93 KB) / GIT / PSFree Exploit (Live Demo) via @zecoxao on Twitter / psfree-beta2.7z (16.34 KB) via abc for 8.0x / psfree-beta3.7z (24.60 KB) via abc / PSFree Beta 3 Version (Live Demo) via Kameleonre_ / psfree-1.3.0.7z (30.30 KB) via abc / psfree-beta-140.7z (37.05 KB) via abc / PS5 Kernel Exploit 3.xx-4.xx (PSFree Integrated Live Demo) / PS5 Exploit Host via idlesauce / PSFree900-main.zip / PSFree900 GIT / PSFree 9.00 FW (Live Demo) via Kameleonre_ / 9.00 FW PSFree with GoldHEN (Live Demo) via ps3120 / 6.72 FW PSFree with GoldHEN via ps3120 / psfree-beta3-140.7z (37.92 KB) via abc / psfree-beta4-140.7z (37.93 KB) via abc / psfree700-main.zip (36.1 KB) / PSFree 7.02 FW via Kameleonre_ / psfree-150b.7z (171.98 KB) by abc via master_s9 / PS5-UMTX-Jailbreak-psfree-150b.zip / GIT Fork via idlesauce / psfree-1.5rc1.7z (193.33 KB) via abc / Mirror
This comes proceeding the PS4 NoBD: BD Driveless Updating & No BD Updater Payloads / PS4 NoBD Toolkit, HDD_Script.py to Retrieve Data from Any PS4 Console via SFlash Dump, PS4 CR0.WP Protection Kernel Security Bypass and pOOBs4: PS4 9.00 Jailbreak Exploit via ChendoChap with Updated Payloads previously released.

Here's further details from the included README.txt: PSFree version 1.2.0

PSFree is a WebKit exploit using CVE-2022-22620 to gain arbitrary read/write.

This exploit was initially for the PS4 firmware version 8.03. CelesteBlue has tested and confirmed that the original works on 7.00-8.52 and helped in making the patches for 6.00-6.72, 9.00-9.60, and PS5 1.00-5.50.

CREDITS:
  • CelesteBlue from ps4-dev on discord.com for testing and porting to other firmwares
  • Quentin Meffre (0xdagger) and Mehdi Talbi (abu_y0ussef) for the 6.xx buildBubbleTree() UaF exploit that served as the framework for this exploit
  • Maddie Stone for the CVE writeup
Notes on reimplementing this project and testing on firmwares != 8.03:
  • num_reuse and num_str must be changed if the proof-of-concept is failing
  • 6.xx firmwares need a setTimeout() after a gc() for garbage collection to work. The duration may also need changing.
These values are at exploit.mjs. This implementation was tested on 8.03.

The values are implementation dependent. Even if you are on the same firmware and you test 2 different implementations, you may need to change the values.

For example, if you reimplement the project with setTimeout() callbacks instead of using Promises, even if you are on 8.03, you may need different values.

Changelog:

1.2.0:

  • add support for PS4 6.00-6.20
1.1.0:
  • add support for running ROP chains (PS4 8.03)
  • add support for calling syscalls (PS4 8.03)
1.0.0 changelog:
  • add proof-of-concept code to gain arbitrary read/write (PS4 6.50-9.60/PS5 1.00-5.50)
OLD README:

PSFree is a WebKit exploit using CVE-2022-22620 to gain arbitrary read/write.

This exploit is for the PS4 firmware version 8.03

Porting to other firmware versions:

The only non-portable parts of the exploit (assuming the firmware is vulnerable) are:

1. the size of SerializedScriptValue and the offsets of its fields
2. how to achieve an arbitrary decrement primitive

There also other objects used by this exploit such as StringImpl. They too are also subject to change between different firmware versions but are very stable hence why we did not list them.

Number 2 is used to corrupt the length of the JSArrayBufferView. This exploit manipulated the destructor ~SerializedScriptValue() to achieve the wanted result.

There is possibly a restricted free primitive via repeatedly corrupting any object that gets allocated at a JSArrayBufferView and changing its contents so that is frees another object.

For example you could modify a StringImpl to have its data pointer point to a target address and set its BufferOwnership to BufferOwned and have it destroyed.

The primitive is restricted as you can only fastFree() addresses known by the fastMalloc allocator. This means an address on the fastMalloc heap, regardless of whether it is free or not.

This means you can recreate any previous fastMalloc use-after-free exploit.

Spoiler: Related Tweets
PSFree WebKit Exploit for PS4 6.00 to 9.60 & QuickHEN PS4 Incoming.png
 

Comments

Hey guys,
I currently have a ps4 on v5.0.5 , and a ps4pro on i believe 6.something. I never bothered to hack them, and they've just been in storage for years at this point.

Seeing the new auto JB via the BluRay exploit, I ordered a disc and figured it's about time i get around to it.

My question is.. is the new BluRay exploit hack the best way to go at this point? Or are there better, more pertistant hacks on lower versions than 9.x (ie - that i dont have to run manually every time i have to shut down), on another version, since i have pretty low firmwares now?

Or do i just suck it up, and upgrade them to at least 9.x and use the Bluray hack?

Any suggestions would be much appreciated!

Thanks!!
 
I have an og ps4 on 11.02, just got the payload running via ethernet. im still trying to figure out pkgs, but am super excited to eventually get some, i guess its just a waiting game at this point.

Just wanted to thank all the contributors and coders that make this possible, so thank you and looking foward to future updates.
 
Just to update on my last post (2 posts ago), I dug out both PS4's...

PS4 is on v5.03
PS4 Pro is on v8.00

After doing more reading... I'm guessing there is no point in keeping the PS4 at v5, since there is no easy hack like the BD-JB? And i'd also have to use backported versions of all games i'd need?

Assuming with the Pro, there's not much point keeping it at 8, as v9 works just fine, and is compatible with the BD-JB?

Again, any input would be appreciated!
Thanks again!
 
I’d recommend using firmware 9.0 instead, since most tools are usually tested on that version. I think it’s now the most commonly used one, and therefore the safest.
 
@jwentzell
Good morning. I hope you are well. In my humble opinion... I would keep the PS4 on 5.05 and the Pro on 9.00. Because, if I'm not mistaken, 9.00 allows you to unlock it without needing a USB drive (I may be wrong).

There's a golden rule I learned from the community: Never update the console and always stay on the lowest firmware possible.

I hope this has been helpful.
 
@ZeHKarLuZ @Recman27
Both good points, thanks for the feedback! After thinking it over, I think i'll bump the Pro up to 9.0 for sure.

For the PS4, maybe bring it up to 5.05 for the time being, just in case later down the road if things open up more on 5.x, (say, a permanent hack\cfw) atleast i'll have an option to do that still.

Thanks again, i appreciate the input!
 
Yes, stay on 5.05 for the regular and 9.0 for the Pro
I bought a brand new slim a month or so ago and was on 6.2 out the box, so I went to the 2nd best jailbreak (after 5.05) to 6.72.
 
@stu07940
Yeah, for sure. Ive had every consolse hacked ever since the psx. (still have them all besides that one), except for a switch and gamecube, a xb1.

While it sucks it's not persistant, this is by far the easiest hack i've ever seen. haha. I dont even play games that much anymore, its just fun to mess around with and learn.
 
@stu07940
I’m on firmware 9.00 on a PS4 Fat, and everything works perfectly. The jailbreak runs smoothly, no crashes or instability so far. I’ve tested several payloads and homebrew apps, and everything seems stable and responsive. Definitely happy with how it performs.
 
Status
Not open for further replies.
Back
Top