PSXHAX.COM website and domain for sale. Contact Us with your offer!
PS4 Dlclose Exploit for Firmware 1.01 Now Fully Implemented!
Following their work-in-progress, PlayStation 4 developer zecoxao with help from droogie1xp, psxdev, VVildCard777, fx0code, CTurt for the exploit and kr105 for the payload have achieved kernel and code execution despite the Grey Screen of Death (GSoD) and fully implemented the Dlclose Exploit for PS4 Firmware 1.01 now! :lovexf2:

Download: PS4-dlclose-master.zip / GIT / PS4 Playground 1.01 Demo

From the README.md file, to quote: PS4-dlclose 1.01 Version

Fully implemented dlclose exploit for PS4 fw 1.01. Compile it with CTurt's.

This is the bare working exploit, you must add your own payload code to make it do anything useful. Enjoy!

Here's to hoping this PlayStation 4 kernel exploit port leads PS4 homebrew developers to uncovering more vulnerabilities and even some unknown goodies perhaps! <3

Code:
*(uint16_t *)0xFFFFFFFF827E31EE = 0x9090;
*(uint16_t *)0xFFFFFFFF827E31FD = 0x9090;
*(uint16_t *)0xFFFFFFFF827E3202 = 0x9090...
PS4 4.55 Kernel Port Updates by Flatz to Fail0verflow Kexec Github
Last fall we saw several additions to Fail0verflow's PS4 Kexec GIT including Kaslr Support, PS4 Offsets and Marcan's Updates, and following his recent Decrypted sl-config.xml.env today PlayStation 4 developer Flat_z lit up the PS4 once again adding 4.55 Kernel Port updates to Fail0verflow's Kexec Github for homebrew developers! :bananaman1:

Here's a summary of the updates from @flatz on Github.com, as follows: 4.55 kernel port and a few slight changes
magic.h (Added 4.55 offsets)
Code:
#ifdef PS4_3_55

#define kern_off_printf 0x1df550
#define kern_off_copyin 0x3b96e0
#define kern_off_copyout 0x3b9660
#define kern_off_copyinstr 0x3b9a50
#define kern_off_kmem_alloc_contig 0x337ea0
#define kern_off_kmem_free 0x33bca0
#define kern_off_pmap_extract 0x3afd70
#define kern_off_pmap_protect 0x3b1f50
#define kern_off_sched_pin 0x1ced60...
PS4 Playground / Dlclose for Firmware 1.01 (WIP) Port by Zecoxao
Since the initial 1.76 PS4 Playground and 3.55 PS4 Playground for Firmware (WIP) PlayStation 4 developer zecoxao has been working with the help of bigboss, wildcard and droogie on porting the Dlclose Exploit to PS4 Firmware 1.01 in hopes of finding undiscovered bugs and vulnerabilities that may be exploitable! :winkxf2:

Download: PS4 Playground 1.01 (GIT) / SceShellCore.elf (8.97 MB)

According to @zecoxao, to quote: "Most offsets SHOULD be fine and most stuff is working BUT we do NOT have code exec working yet. if anyone knows why, please contact us :smilexf2:"

From the README.md file: PS4-playground

A collection of PS4 tools and experiments using the WebKit exploit. This is for firmware 1.76/1.01 only at the moment.

Although initially just a framework to help write and execute ROP chains, the playground now allows for running unsigned binaries compiled, and booting Linux from USB.

Setup

A live demo can be tried here.

You should clone the repo and upload it your own server if you wish to make changes:
Code:
git clone git://github.com/CTurt/PS4-playground.git
You can also download a zip of the latest source here.

Usage

After executing a test, you should either refresh the page, or close and reopen the browser entirely; running multiple experiments sequentially is not reliable. If you are using a web browser view in an app which isn't the Internet Browser, you can use the Refresh button under Misc to refresh the page.

Code Execution

Click "Go", and wait for the text "Stage: Waiting for payload..." to appear.

Send the desired binary over TCP to your PS4 on port 9023...
Sony Removes Qwertyoruiopz Primitive, Decrypted sl-config.xml.env
Yesterday Sony released PS4 Firmware 4.70, and today PlayStation 4 developer qwertyoruiopz confirmed that Sony removed the primitive used to exploit his bug with bombob explaining this means Sony patched the way to access the bug, but the exploit is still present so those on OFW 4.55 continue to have an entry point. :sneaky:

That is great news for PlayStation 4 developers including @theorywrong who tweeted reminding everyone it's ultimately qwertyoruiopz's decision whether to release it or wait, but noted that if it was released PS4 Devs could begin work on jailbreak-related projects.

So how did Sony patch the primitive if the exploit has yet to be released? Both qwertyoruiopz and flat_z shed some light on this with a transcript from Twitter as follows:
  • qwertyoruiop‏: lol great sony removed the primitive I used to exploit my bug
  • qwertyoruiop‏: my bet? i accidentally let some crash logs go early on. sucks because it was a good exploit primitive, but it's cool since my bug is OK
  • qwertyoruiop‏: I keep mine off the network now. Not initially however
  • Kazoo Kid‏: they haven't a primitive is dead, but the exploit itself is ok
  • Chara~Chan~~‏: Let the library expanding While we have bug we'll have more games in time. More late more better
  • qwertyoruiop‏: that's the strategy :)
  • TheoryWrong‏: It is not for us to choose, but if I can give my opinion, many developer could start things with a jailbreak
  • Newgunnerr‏: So will this mean a release from you?
  • Thibobo: His bug is OK so probably Not
  • Reminon‏: Lol why would he burn the whole exploit over a part of it being fixed?
And some words of wisdom from flat_z on preventing this from happening again:
  • eh, so for future hacks, be sure you have...
PS4 Jailbreak Exploit by Chaitin Tech Echoes via SpecterDev
Many may recall the PS4 Firmware 4.01 Jailbreak by Chaitin Tech, their ROP Tool and the addition of Kaslr Support last year.

Following his PS4 4.0x WebKit Userland Exploit Documentation, JailbreakMe PS4 3.5x / 3.70 / 4.0x Exploit Ports and continuing research PlayStation 4 developer SpecterDev shared a tweet earlier today echoing Chaitin Tech's PS4 kernel exploit on 4.05 that was disclosed to Sony and patched in 4.06 official Firmware this past November.

The news comes after qwertyoruiopz's PS4 4.50 Kernel R/W Access announcement, PS4 4.5x Pwnage and confirmation of PS4 4.55 Dumped.

While @SpecterDev already stated he can't release it and as a result decided to remove the tweet, at least PS4 Developers who have been collaborating and examining it can rest assured that Chaitin Tech and Sony aren't the only ones privy now... here's to hoping someone else will also run across it and decide to share it with the scene. :angel:

From the...
Back
Top