Big news on the DS scene today as Team Twizzers releases their DSiWare Sudokuhax, a new exploit that lets user run unsigned codes from the DSi's SD slot by exploiting a flaw in the DSiWare game, Sudoku.
According to the team, the project started in early December when they managed to get the "DSi mode code execution by exploiting the DSiWare application ‘Sudoku’ by EA. Sudoku is only available for regions USA and EUR/AU (Nintendo has now apparently removed the game from the EUR/AU and USA DSi Shop). Exploiting DSiWare is interesting because in DSi mode the DSi SD card slot is accessible, the whole 16MB RAM is available, and the CPU is clocked 2x higher than DS-mode. The max size of the embedded code that can be loaded directly via this exploit is limited so a small payload was needed to chain load to another application. Initially a wifi loader was used, but this was switched to load from the DSi SD card slot. The SD card loader boots /boot.nds from the SD card directly from Sudokuhax."
The team notes that "DSiWare exploits can’t access gamecard slot1, it’s likely that only launcher/sysmenu can access slot1. The main advantage of DSiWare exploits over hybrid card EEPROM savedata exploits is SD card access, *and* the exploit supports SDHC."
Developer's note:
Usage of the exploit is described below:
1. Export Sudoku to SD card via the data management menu.
2. Sudokuhax will then be injected into the Sudoku application via client software. The client software uploads DSi-specific data from the Sudoku application to a web server, then injects the retrieved data into the Sudoku application.
3. Copy the output binary to SD card with the same filename as the original.
4. Copy Sudokuhax from SD card to “internal memory” via the data management menu.
5. Launch Sudoku, then press button A or touch screen at the Sudoku title screen.
6. Now boot.nds on SD card will be run.
The data uploaded by the client software includes the anonymous DSi-unique console ID, and other data required for modifying the Sudoku binary on SD card. This data is used for logging unique web server requests.
