[New Update below] - Dec 13: In the PlayStation 4 hacking scene there has been some developments over the past weeks. Recently cturt announced a Kernel Exploit in the PS4 firmware, this kernel exploit is actually patched in latest firmwares and will only run up to Ps4 firmware v1.76. However this kernel exploit, while patched in later firmware's is still a huge discovery and will prove to be very useful for the PS4 community. As developers will now have a closer look at the security and workings on the firmware with an angle they previously never had access to. Which has already produced some progress on a rumored PS4 Jailbreak from valid sources in PS4 hacker Cturt & Others ( but beware there are many FAKE ps4 jailbreaks out there connected to alot of scams to land a quick buck or to infect your system with malware and viruses.).
Then today Cturt makes the groundbreaking announcement as the developer states "Just broke WebKit process out of a FreeBSD jail (cred->cr_prison = &prison0). Guess you could say the PS4 is now officially "jailbroken" :P" in a recent tweet, followed by another tweet that reads " Can successfully dump RAM from other processes (like SceShellUI) using ptrace! Next step: patching RAM...". While this "jailbreak" is only working upto v1.76 firmware at the moment it does not do many user's much good, but it does give hackers and developer more access to the system that is starting to show its holes in security. One can only hope developers and hackers can produce a jailbreak for later firmwares. These things happen in steps and these steps take some time, but it seems that the PS4 may not be as secure as one may imagine. Does this mean CFW and Homebrew on the PlayStation 4 (PS4)? Time will only tell and hopefully we see some more exciting news on the PS4 front in the coming weeks/months. Best advice for a PS4 owner awaiting, is to exercise patients as this will take some time if it even happens on later firmwares, but that possiablity is stronger today that it was several days ago. So there is progress and that is exciting to see in the PlayStation 4 Community.
Recent Tweets from Cturt
UPDATE
(Dec 14) Developer Cturt shows off some additional details as he shows the file system (root) and proceeses running that the hacker was able to capture the processes running in RAM. I
Stay tuned for all the latest developments regarding this breakthrough on the PS4.
Then today Cturt makes the groundbreaking announcement as the developer states "Just broke WebKit process out of a FreeBSD jail (cred->cr_prison = &prison0). Guess you could say the PS4 is now officially "jailbroken" :P" in a recent tweet, followed by another tweet that reads " Can successfully dump RAM from other processes (like SceShellUI) using ptrace! Next step: patching RAM...". While this "jailbreak" is only working upto v1.76 firmware at the moment it does not do many user's much good, but it does give hackers and developer more access to the system that is starting to show its holes in security. One can only hope developers and hackers can produce a jailbreak for later firmwares. These things happen in steps and these steps take some time, but it seems that the PS4 may not be as secure as one may imagine. Does this mean CFW and Homebrew on the PlayStation 4 (PS4)? Time will only tell and hopefully we see some more exciting news on the PS4 front in the coming weeks/months. Best advice for a PS4 owner awaiting, is to exercise patients as this will take some time if it even happens on later firmwares, but that possiablity is stronger today that it was several days ago. So there is progress and that is exciting to see in the PlayStation 4 Community.
Recent Tweets from Cturt
UPDATE
(Dec 14) Developer Cturt shows off some additional details as he shows the file system (root) and proceeses running that the hacker was able to capture the processes running in RAM. I
Code:
[+] Entered shellcode
[+] UID: 0, GID: 0
[DIR]: .
[DIR]: ..
[DIR]: adm
[DIR]: app_tmp
[DIR]: data
[DIR]: dev
[DIR]: eap_user
[DIR]: eap_vsh
[DIR]: hdd
[DIR]: host
[DIR]: hostapp
[FILE]: mini-syscore.elf
[DIR]: mnt
[DIR]: preinst
[DIR]: preinst2
[FILE]: safemode.elf
[FILE]: SceBootSplash.elf
[FILE]: SceSysAvControl.elf
[DIR]: system
[DIR]: system_data
[DIR]: system_ex
[DIR]: system_tmp
[DIR]: update
[DIR]: usb
[DIR]: user
[+] PID 0, name: kernel, thread: mca taskq
[+] PID 1, name: mini-syscore.elf, thread: SceRegSyncer
[+] PID 2, name: SceHidAuth, thread: SceHidAuth
[+] PID 3, name: hidMain, thread: hidMain
[+] PID 4, name: SceCameraDriverMain, thread: SceCameraDriverM
[+] PID 5, name: SceCameraSdma, thread: SceCameraSdma
[+] PID 6, name: hdmiEvent, thread: hdmiEvent
[+] PID 8, name: xpt_thrd, thread: xpt_thrd
[+] PID 9, name: iccnvs, thread: iccnvs
[+] PID 10, name: audit, thread: audit
[+] PID 11, name: idle, thread: idle: cpu0
[+] PID 12, name: intr, thread: irq273: xhci2
[+] PID 13, name: geom, thread: g_notification
[+] PID 14, name: yarrow, thread: yarrow
[+] PID 15, name: usb, thread: usbus2
[+] PID 16, name: md0, thread: md0
[+] PID 17, name: icc_thermal, thread: icc_thermal
[+] PID 18, name: sflash, thread: sflash
[+] PID 19, name: sbram, thread: sbram
[+] PID 20, name: trsw intr, thread: trsw intr
[+] PID 21, name: trsw ctrl, thread: trsw ctrl
[+] PID 22, name: SceBtDriver, thread: SceBtDriver
[+] PID 23, name: pagedaemon0, thread: pagedaemon0
[+] PID 24, name: pagedaemon1, thread: pagedaemon1
[+] PID 25, name: vmdaemon, thread: vmdaemon
[+] PID 26, name: bufdaemon, thread: bufdaemon
[+] PID 27, name: syncer, thread: syncer
[+] PID 28, name: vnlru, thread: vnlru
[+] PID 29, name: softdepflush, thread: softdepflush
[+] PID 31, name: SceSysAvControl.elf, thread: SceAvSettingPoll
[+] PID 33, name: SceSysCore.elf, thread: SysCoreAppmgrWat
[+] PID 34, name: orbis_audiod.elf, thread: AoutMonitorPid40
[+] PID 35, name: GnmCompositor.elf, thread: CameraThread
[+] PID 36, name: SceShellCore, thread: SceMsgMwSendMana
[+] PID 38, name: SceShellUI, thread: SceWebReceiveQue
[+] PID 39, name: MonoCompiler.elf, thread: MonoCompiler.elf
[+] PID 40, name: SceAvCapture, thread: SceAvCaptureIpc
[+] PID 41, name: SceGameLiveStreamin, thread: SceGlsStrmJobQue
[+] PID 42, name: ScePartyDaemon, thread: SceMbusEventPoll
[+] PID 43, name: SceVideoCoreServer, thread: SceVideoCoreServ
[+] PID 44, name: SceRemotePlay, thread: SceRp-Httpd
[+] PID 45, name: SceCloudClientDaemo, thread: SceCloudClientDa
[+] PID 46, name: SceVdecProxy.elf, thread: proxy_ipmi_serve
[+] PID 47, name: SceVencProxy.elf, thread: SceVencProxyIpmi
[+] PID 48, name: fs_cleaner.elf, thread: fs_cleaner.elf
[+] PID 49, name: SceSpkService, thread: SceSpkService
[+] PID 50, name: WebProcess.self, thread: selectThread
[+] PID 51, name: orbis-jsc-compiler., thread: SceFastMalloc
[+] Triggering second kernel payload
[+] Entered main payloadStay tuned for all the latest developments regarding this breakthrough on the PS4.