fail0verflow Profile
fail0verflow

@fail0verflow

Followers
52K
Following
6
Media
16
Statuses
227

Joined November 2010
Don't wanna be here? Send us removal request.
@fail0verflow
fail0verflow
11 months
want to play with the fbsd umtx exploit? check out
Tweet card summary image
github.com
Contribute to fail0verflow/ps5-umtxdbg development by creating an account on GitHub.
20
128
617
@fail0verflow
fail0verflow
2 years
@flat_z
Aleksei Kulaev
2 years
finally. hello, PS5 PSP :)
Tweet media one
9
45
269
@fail0verflow
fail0verflow
3 years
New blog post about hacking PS VR! We managed to find some major flaws - breaking secure boot and extracting all key material:
14
185
591
@fail0verflow
fail0verflow
4 years
Translation: We got all (symmetric) ps5 root keys. They can all be obtained from software - including per-console root key, if you look hard enough!.
@fail0verflow
fail0verflow
4 years
Another one bites the dust 😎
Tweet media one
139
1K
4K
@fail0verflow
fail0verflow
4 years
Another one bites the dust 😎
Tweet media one
73
359
2K
@fail0verflow
fail0verflow
5 years
Here is our implementation of the Renesas RL78 debug protocol (as requested in a comment on the blog):
Tweet card summary image
github.com
Implementation of Renesas debug protocol(s) for RL78 and perhaps other archs - fail0verflow/rl78-debug
8
33
185
@fail0verflow
fail0verflow
7 years
Took a peek at latest PS4 Pro (CUH-72xx, board NVG-001): same southbridge (CXD90046GG), newly marked syscon (A06-C0L2 but still RL78/G13) - so nothing changes in terms of "Aux Hax" stuff :).
31
54
300
@fail0verflow
fail0verflow
7 years
Another "PS4 Aux Hax" blog! Using HDMI-CEC to get code exec on all PS4 southbridge versions (including PS4 Pro, etc.), without requiring other parts of the system to be pwned:.
35
392
976
@fail0verflow
fail0verflow
7 years
Small update to Aux Hax:.Nearly same methods are working against devices on recent PS4 Pro board NVB-003:.Syscon A05-C0L2 (R5F101LL).Belize southbridge (CXD90046GG). Belize has ROM readout protection and clears stack. they're learning ;).
11
48
253
@fail0verflow
fail0verflow
7 years
A trio of new blog posts! Checkout "PS4 Aux Hax": hacking Aeolia, Syscon, and DS4.
14
163
445
@fail0verflow
fail0verflow
7 years
Note the CVE creation date, in case anyone doubted our disclosure timeline. And don't even *think* about trying to give the bug itself a cutesy name. We have enough of those already ;-).
8
7
131
@fail0verflow
fail0verflow
7 years
The Tegra X1 flaw that both ShofEL2 and Fusée Gelée exploit now has a name: CVE-2018-6242.
11
100
302
@fail0verflow
fail0verflow
7 years
Fun fact: we started upstreaming some patches months ago (working with the linux-tegra community on Tegra X1 support in mainline Linux), so if you've seen anyone else running Linux on the Switch recently. chances are they were running some of our code unknowingly ;-).
13
31
272
@fail0verflow
fail0verflow
7 years
Reminder: ShofEL2 cannot be patched in existing units (it will work on *any* firmware, past or future), it allows full access (all keys and secrets), and it is completely undetectable by normal software. You can dual boot Linux and Switch OS with impunity.
@fail0verflow
fail0verflow
8 years
In case it wasn't obvious, our Switch coldboot exploit:.* Is a bootrom bug.* Can't be patched (in currently released Switches).* Doesn't require a modchip to pull off.
28
163
486
@fail0verflow
fail0verflow
7 years
ShofEL2 also supports running Switch homebrew. Technically.
Tweet media one
24
136
604
@fail0verflow
fail0verflow
7 years
Extra derp points because that China-only port was *Twilight Princess*, not *Wind Waker*.
2
2
109
@fail0verflow
fail0verflow
7 years
Protip for @arstechnica: this is Dolphin on Linux, not some dodgy China-only port for the Shield.
2
21
223
@fail0verflow
fail0verflow
7 years
In utterly, completely unrelated news, here's a sneak peak at a totally brand new Zelda game coming soon to Nintendo Switch.
Tweet media one
38
222
865
@fail0verflow
fail0verflow
7 years
Jokes aside, we have a 90-day responsible disclosure window for ShofEL2 ending on April 25th. Since another person published the bug so close to our declared deadline, we're going to wait things out. Stay tuned.
9
42
233