Announcing RocketLauncher! The first exploit with unlocked Arm7!

UPDATE:
Looks like NoCash found an exploit that is even better then RocketLauncher:

https://problemkaputt.de/gba.htm

He titled it Unlaunch. The exploit works by exploiting a flaw in Stage2 and apparently works on all firmware versions. It requires you run the installer from a DSiWare based hax environment as access to SD/NAND is required. (thus you can't run this from Slot-1 based TWL exploit)

The flaw in stage2 is a buffer overflow involving Launcher's TMD file. If you provide a larger then normal TMD file, it will attempt to load the TMD into ram anyways (this occurs before it does the RSA check) This causes it to overwrite some code in arm9 ram causing arm9 to execute the custom payload. The full details are found in the info menus in the installer.

Note however the installer does not appear to work correctly at the moment. I'd advise you not attempt to install it from the installer. Use the manual install method instead. BUT I'd highly recommend you have a hard mod before attempting manual install. If you have had experience modifying your nand you may be ok doing this. But for safety sake I would just advise against that until the installer works properly.

(this is one reason why RL hasn't been released yet. No proper installer tools are available yet and we don't want people bricking consoles trying to install it)

The release of this exploit may impact our plans regarding RocketLauncher. I'll post more about this once StuckPixel has decided to comment on this.


Important Notice:

Do NOT visit Data Management in DSi System Settings or use the 3DS Transfer tool after installing unlaunch. You WILL brick the console. Wait until HiyaCFW is refined/released properly so that SD redirected version of Launcher can be used or when NoCash decides to implement his own version of the SD redirect patch.








Today I can finally announce a new exploit for the Nintendo DSi. I found this flaw back on May 29th. Almost a year after NoCash initially discovered a oversight by Nintendo involving the DS Cart White list which this exploit takes advantage of (Nintendo forgot to reimplement the RSA checks on it lolz). I was fudging with various things in the white list to try and get a crash. I got system menu to crash by using large values in section 3! So I contacted NoCash and a few other devs about this to investigate it and to see if it's exploitable. Well long story short it was!


Summery of the above video:

1. The exploit requires 1.4.0 firmware! Older or newer fw revisions do not work!
2. The exploit requires a flashcart that you are able to modify the internal rom it presents to the system.
3. Details on which cards will be compatible will be revealed at a later time.
4. The exploit involves a buffer overflow flaw involving section 3 of the white list.
5. This overflow occurs on arm7 thus allowing overwriting memory exclusive to arm7.
6. As a result a large enough overflow will hit the IRQ interrupt handler. This is how we gain code execution.
7. Arm9 was relatively easy to take over. Though data caching presented a minor roadblock while testing on hardware. :P
8. I currently use a modified build of nds-bootloader from WinterMute's github. You know, that portion of hbmenu responsible for booting SRLs. :P
9. Because we already gained arm7 we only had to put arm9 in the correct wait state so that nds-bootloader can do it's thing. :D
10. The exploit in theory can work from the menu once it's running. But we currently make use of the auto boot feature to ensure a stable consistant environment. Tests with a second console suggest that is the case. Note that the exception vector for arm7 seems to either be somewhere else once the menu GUI is running or the overflow hits something else causing arm7 to crash early. Currently we plan to only target exploiting the system with an autoboot rom as it's more predictable.
11. The exact machanics of the arm9 take over and how nds-bootloader is loaded may change. Currently the entire payload fits on the cart. But we may allow reading a payload off SD instead.

Credits to NoCash, Gericom, and Normmatt for help testing/figuring this out. Big credit to StuckPixel who put in most of the coding needed to make this happen. My contribution was finding the flaw and help with testing on hardware.


I will release further details as we finalize this exploit and prepare stuff that will make installing it easier.

Note you will either need a nand mod or a DSiWare based exploit to downgrade your console/install the modified white list needed for this to work. Hopefully we'll have a better solution then simply using fwtool to do this so that may be the factor that determines release date so please be patient!

When things are ready I will update this thread!
 
Last edited by Apache Thunder,

igpltv

Active Member
Newcomer
Joined
Dec 13, 2017
Messages
44
Trophies
0
XP
142
Country
United States
Hey, it has been a couple of months now, and I haven’t really heard or been able to find any updates, so what’s going on?
 

huntertron1

dancing to music!
Member
Joined
Oct 28, 2017
Messages
576
Trophies
0
Age
21
XP
625
Country
United States
I'm not by any stretch rushing them. I haven't heard any updates, who knows if they are still working on it ATM, there is a point where you have to ask what is up.
it takes time. i know this. ive been waiting as soon as i heard about it in 2017 in december.
 

huntertron1

dancing to music!
Member
Joined
Oct 28, 2017
Messages
576
Trophies
0
Age
21
XP
625
Country
United States

smf

Well-Known Member
Member
Joined
Feb 23, 2009
Messages
6,647
Trophies
2
XP
5,885
Country
United Kingdom
havent!!!! one moment

--------------------- MERGED ---------------------------

https://gbatemp.net/threads/early-wip-bluelist-a-script-based-whitelist-editor-for-dsi.498274/
there waiting for a white list editor. and well here's one thats really early find Apache Thunder's post

The whitelist editor thread is a good example of why RocketLauncher hasn't been released yet.

"Once it's released that size will be known. I did add 10 or so dummy entries to each section to facilitate adding entries without changing file size. As long as you design your script to accommodate that, this may be useful for when RocketLauncher is released."

They won't tell you what the white list editor needs to do until rocket launcher is released. So we need to wait until rocket launcher is released before writing a white list editor that works, but they won't release rocket launcher because they are waiting for a white list editor that works.

The last I heard they weren't working on producing one themselves as they were busy doing other things.
 
Last edited by smf,

Apache Thunder

I have cameras in your head!
OP
Member
Joined
Oct 7, 2007
Messages
4,434
Trophies
3
Age
36
Location
Levelland, Texas
Website
www.mariopc.co.nr
XP
6,810
Country
United States
The whitelist editor thread is a good example of why RocketLauncher hasn't been released yet.

"Once it's released that size will be known. I did add 10 or so dummy entries to each section to facilitate adding entries without changing file size. As long as you design your script to accommodate that, this may be useful for when RocketLauncher is released."

They won't tell you what the white list editor needs to do until rocket launcher is released. So we need to wait until rocket launcher is released before writing a white list editor that works, but they won't release rocket launcher because they are waiting for a white list editor that works.

The last I heard they weren't working on producing one themselves as they were busy doing other things.


Not true. StuckPixel is the one working on the white list editor. Hence release of RocketLauncher will be tied on when he finishes the tools he wants to include with it. Also you don't need to know what the size of the whitelist needs to be. All you need for a good tool is the ability to replace existing entries in whitelist without changing it's file size. It shouldn't matter if you don't know what size the whitelist will before RocketLauncher. If you coded it right, it would still do the job regardless. Hard-coding what size the white list will be into your application is a bad idea. You'd want it to be flexible and be able work with any white list. Not just the RocketLauncher ones. ;)
 
Last edited by Apache Thunder,

smf

Well-Known Member
Member
Joined
Feb 23, 2009
Messages
6,647
Trophies
2
XP
5,885
Country
United Kingdom
Not true. StuckPixel is the one working on the white list editor. Hence release of RocketLauncher will be tied on when he finishes the tools he wants to include with it. Also you don't need to know what the size of the whitelist needs to be. All you need for a good tool is the ability to replace existing entries in whitelist without changing it's file size. It shouldn't matter if you don't know what size the whitelist will before RocketLauncher. If you coded it right, it would still do the job regardless. Hard-coding what size the white list will be into your application is a bad idea. You'd want it to be flexible and be able work with any white list. Not just the RocketLauncher ones. ;)

Actually that is pretty much the point I was making. None of the white list editors and safe install tools that people are writing will help speed up the release as StuckPixel won't divulge enough information to do it yourself, until he has written his own tools. But the last thing you said about him was that he wasn't doing any DSi development.

Once we have RocketLauncher and CFW then I don't see that any other safe install tools or white list editors will be any use, because you won't be using nand and everything can be patched in ram.
 
Last edited by smf,

huntertron1

dancing to music!
Member
Joined
Oct 28, 2017
Messages
576
Trophies
0
Age
21
XP
625
Country
United States
Actually that is pretty much the point I was making. None of the white list editors and safe install tools that people are writing will help speed up the release as StuckPixel won't divulge enough information to do it yourself, until he has written his own tools. But the last thing you said about him was that he wasn't doing any DSi development.

Once we have RocketLauncher and CFW then I don't see that any other safe install tools or white list editors will be any use, because you won't be using nand and everything can be patched in ram.
i was just saying that progress is being made also that post was in march to explain to someone that progress is being made even tho its not going to make the relase date(soon™) change. id stop talking about something that i already finished.
 

Site & Scene News

Popular threads in this forum

General chit-chat
Help Users
    K3Nv2 @ K3Nv2: Jaws is on a diet