Editing Vulnerabilities
Jump to navigation
Jump to search
The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then publish the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 1: | Line 1: | ||
== | == WebKit/Userland Exploits == | ||
=== Int32 bug === | |||
[[Internet_Browser#Webkit_exploit|WebKit/536.26 exploit]] on [[System Firmware]] [[1.760.000]] and lower '''(patched in [[2.000.000]])''' | |||
<br/>http://wololo.net/2014/10/24/webkit-exploit-confirmed-to-run-on-ps4-firmware-1-76/ | |||
=== | === CVE 2014-1303 === | ||
[[Internet_Browser#Webkit_exploit|WebKit/537.73 exploit]] on [[System Firmware]] [[2.040.000]] and lower '''(patched in [[2.508.000]])''' | |||
<br/>https://github.com/Fire30/PS4-2014-1303-POC | |||
=== FireKaku === | |||
[[Internet_Browser#Webkit_exploit|WebKit/??? exploit]] on [[System Firmware]] [[3.550.000]] + 3.70 (Phat PS4 NOT PRO) and lower '''(patched in [[4.000.000]])''' | |||
<br/>https://github.com/Fire30/PS4-3.55-Code-Execution-PoC | |||
=== heap buffer overflow in butterfly access on uaf_target === | |||
[[Internet_Browser#Webkit_exploit|WebKit/??? exploit]] on [[System Firmware]] [[4.070.000]] and lower '''(patched in [[4.500.000]])''' | |||
<br/>https://rce.party/ps4 (mirror at https://gist.github.com/X41/36acd2a6939e4cebbecba45d35bf0d75) | |||
=== | === Additional Information === | ||
On FW <= 1.76, you could map RWX memory from ROP by abusing the JiT functionality and the sys_jitshm_create and sys_jitshm_alias system calls. This however was fixed after 1.76, as WebKit has been split into two processes. One handles javascript compilation and the other handles other web page elements like image rendering and DOM. The second process will request JiT memory upon hitting JavaScript via IPC (Inter-Process Communication). Since we no longer have access to the process responsible for JiT, we can no longer (at least currently), map RWX memory for proper code execution. | |||
== Kernel Exploits == | |||
=== NamedObj Type Confusion (namedobj) === | |||
==== Analysis ==== | ==== Analysis ==== | ||
[ | [http://cturt.github.io/dlclose-overflow.html Write-up of the < 4.06 kernel exploit] | ||
==== | ==== The Bug ==== | ||
Type confusion in the namedobj system once exploited can lead to an arbitrary free() allowing an attacker to craft a use-after-free situation to obtain code execution in ring0. | |||
Type confusion in the namedobj system once exploited can lead to an arbitrary free() allowing an attacker to craft a use-after-free | |||
==== Patched ==== | ==== Patched ==== | ||
'''Yes''' in 4.06 FW | '''Yes''' in 4.06 FW | ||
=== Dynamic Library Prepare Close (dlclose) === | |||
==== Analysis ==== | ==== Analysis ==== | ||
[http://cturt.github.io/dlclose-overflow.html Analysis of sys_dynlib_prepare_dlclose PS4 kernel heap overflow (by '''CTurt''' with the help of '''qwertyoruiop''')] | |||
==== Bug | ==== The Bug ==== | ||
Integer overflow in the sys_dynlib_prepare_dlclose() system call can lead to a heap overflow causing memory corruption, allowing an attacker to obtain code execution in ring0. | |||
==== Source ==== | |||
[https://github.com/kR105/PS4-dlclose Public release by '''kR105'''] | |||
==== | |||
[https://github.com/kR105/PS4-dlclose Public release by kR105] | |||
==== Patched ==== | ==== Patched ==== | ||
'''Yes''' in 2.00 FW | '''Yes''' in 2.00 FW | ||
=== BadIntegerReturn (badIRET) === | |||
==== Analysis ==== | ==== Analysis ==== | ||
[http://cturt.github.io/ps4-3.html Hacking the PS4, part 3 - Kernel exploitation (by '''CTurt''')] | |||
==== Source ==== | |||
[http://seclists.org/oss-sec/2015/q3/66 CVE-2014-9322] | |||
<br/>[http://www.filedropper.com/ps4-bad-iret-5fs Public binary] | |||
==== The Bug ==== | |||
Allows an attacker to corrupt the GS base address and obtain code execution in ring0 by abusing the IRET instruction. | |||
==== Bug | |||
==== Patched ==== | ==== Patched ==== | ||
'''Yes''' in 2.00 FW | '''Yes''' in 2.00 FW | ||
=== Additional Information === | |||
It seems at some point after the 1.76 FW, ASLR (Address Space Layout Randomization) was enabled in the kernel. This means that to properly exploit the kernel to escalate privileges, an information disclosure vulnerability will most likely be needed to defeat ASLR and locate the kernel in memory. | |||
=== | == First Steps == | ||
==== VidNow ==== | |||
A possible exploit has been found in VidNow App in the Playstation Store App . | |||
PATCHED: Sony has hotfixed this exploit via content hashing the file while in transit. | |||
UPDATE: Some have managed to reverse the hotfix but the method is not known - the PS4 checks the content | |||
hash HTTP header from the HMAC header. | |||
==== SnagFilms ==== | |||
A possible exploit has been found in the SnagFilms App in the Playstation Store App. | |||
Arbitrary code execution in memory has been demonstrated, although so far the system will throw an exception in the programs memory before the payload finishes loading. | |||
If you craft a small enough payload and/or a payload that load's without causing an exception in program memory you can most likely get code execution working. | |||
http://i.imgur.com/5OrSFCa.jpg | |||
{{Reverse Engineering}} | {{Reverse Engineering}} | ||
<noinclude> | <noinclude>[[Category:Main]]</noinclude> | ||
[[Category:Main]] | |||
</noinclude> |