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 109: | Line 109: | ||
'''No''' in PS5 FW 4.51. | '''No''' in PS5 FW 4.51. | ||
---- | ---- | ||
Line 139: | Line 130: | ||
== FW <= 4.03 - exFAT driver heap-based buffer overflow == | == FW <= 4.03 - exFAT driver heap-based buffer overflow == | ||
=== Credits === | === Credits === | ||
Line 149: | Line 138: | ||
Not yet because even though there is ChendoChap's method to execute usermode code in WebKit, there is no PS5 kernel dump to build a kernel ROP chain. Exploiting this kernel vulnerability blind is almost impossible because once the USB device is inserted it corrupts the kernel heap memory and if the offsets in the kernel ROP chain are bad it creates a kernel panic. | Not yet because even though there is ChendoChap's method to execute usermode code in WebKit, there is no PS5 kernel dump to build a kernel ROP chain. Exploiting this kernel vulnerability blind is almost impossible because once the USB device is inserted it corrupts the kernel heap memory and if the offsets in the kernel ROP chain are bad it creates a kernel panic. | ||
See the [https://www.psdevwiki.com/ps4/Vulnerabilities#FW_.3C.3D_9.00_-_exFAT_driver_heap-based_buffer_overflow PS4 wiki]. | |||
=== Patched === | === Patched === |