From 1126c5bd704901d8ff7a0fadf620b50078396332 Mon Sep 17 00:00:00 2001 From: CTurt Date: Sat, 18 Jul 2020 23:51:32 +0100 Subject: [PATCH] update --- portingnotes.html | 38 +++++++++++++++++++++++++------------- 1 file changed, 25 insertions(+), 13 deletions(-) diff --git a/portingnotes.html b/portingnotes.html index 7107b80..f70270c 100644 --- a/portingnotes.html +++ b/portingnotes.html @@ -107,16 +107,16 @@ tr:nth-child(even) { 0x262360 0x261548 - - + 0x2986a0 + 0x2952f0 pointToIFO 0x2432c8 0x23dfc8 - - + 0x25c880 + 0x258a28 SifIopReboot @@ -131,32 +131,32 @@ tr:nth-child(even) { 0x2082a0 0x208260 - - + 0x84180 + 0x208d80 SifExitRpc 0x208440 0x208400 - - + 0x84310 + 0x208f20 SifIopReset 0x291fb8 0x291358 - - + 0x84fe0 + 0x20e7d8 SifIopSync 0x292138 0x2914d8 - - + 0x85110 + 0x20e958 Controlled memory ranges @@ -248,6 +248,13 @@ tr:nth-child(even) {
+

Testing

+ +

Conflicts

@@ -261,7 +268,7 @@ tr:nth-child(even) {

- We might also be able to force a non-conflict between 2 versions by making use of 2 different buffer overflows. That would need to be experimented with. Until then, here is a table for the versions with conflicting currentDiscBytePointer IFO offsets which we would need to be common controlled memory regions for: + We might also be able to force a non-conflict between 2 versions by making use of 2 different buffer overflows. That would need to be experimented with. Until then, here is a table for the versions with conflicting currentDiscBytePointer IFO offsets which we would need to have common controlled memory regions for:

@@ -351,5 +358,10 @@ tr:nth-child(even) {
+

Hunting for new vulnerabilities

+

+ Those buffer overflows are really easy to find as the IFO parsing is the first thing the DVD player does. We'll probably want to reverse engineer deeper into things like the actual video decoding, etc, in order to see if more easily exploitable bugs are available; for that, I hope others will help collaborate and share notes. +

+