How ntfargo/relapse-exploit works
This repository implements a browser-driven PS5 exploit for firmware 7.00–13.60. The user-facing flow runs the WebKit exploit to obtain an arbitrary read/write primitive, prepares a ROP worker, and invokes the kernel exploit; the documented chain uses kernel read/write to enable privilege and sandbox changes and optionally load payloads. Firmware-specific offset tables support the exploit. Several implementation details are unsampled, so uncertain runtime links are omitted rather than inferred.
Main entry points: site.js Browser runner · relapse_exploit.js Kernel exploit · main.js Exploit coordinator · mem.js Memory access
Components 13
Browser entry
- Browser runner
src/site.js - Firmware checks
src/firmware.js - Exploit coordinator
src/main.js
Exploit primitives
- WebKit exploit
src/webkit.js - Memory access
src/utils/mem.js - 64-bit values
src/utils/int64.js - ROP chains
src/rop.js
Kernel stage
- Firmware offsets
offsets - Kernel exploit
src/relapse_exploit.js - Syscall constants
src/utils/syscalls.js
Payload delivery
- Payload loader
src/kexp.js - ELF loader
Other components
- Console user
Connections 12
- Console user → Browser runner: opens exploit
- Browser runner → WebKit exploit: starts exploit
src/site.js - Browser runner → Memory access: installs primitive
src/site.js - Browser runner → Exploit coordinator: runs chain
src/site.js - Browser runner → Firmware checks: checks support
- Exploit coordinator → Kernel exploit: invokes exploit
src/main.js - Exploit coordinator → ROP chains: prepares worker
- Kernel exploit → 64-bit values: uses values
src/relapse_exploit.js - Memory access → 64-bit values: uses values
src/utils/mem.js - Kernel exploit → Firmware offsets: reads offsets
src/relapse_exploit.js - Kernel exploit → Payload loader: loads payloads
src/relapse_exploit.js - Payload loader → ELF loader: starts listener