![]() The ASCII player name or the game data aren't exploitable. ( No crash, just nice very high scores, and very long words displayed. Has ASCII null-terminated high-score list names and null-terminated word list strings. Has some profile names but they're all in one tiny savfile. Has ASCII strings for high-scores, game didn't crash with modified high-scores. Has ASCII high-scores with null terminated strings, no string bugs. string bugs only corrupted the display, making the game unplayable. Has ASCII high-scores with null terminated strings. ![]() Game didn't crash with a long profile string. Uses ASCII strings, the value of each char is - 0x20 of the actual ASCII value. ![]() Uses ASCII for player name and other text input, but the checksum is unknown. Has ASCII player name checksum is unknown. Uses ASCII player name for time scores It's unlikely this can be exploited, seems to crash /w out-of-bounds array-index. Has ASCII string but the checksum is unknown. Has ASCII strings but the checksum is unknown. Not sure if this can be exploited somehow, it crashes /w array-index out-of-bounds fail. It's unlikely this can be exploited, seems to crash /w out-of-bounds array-index. ![]() Has ASCII player names, checksum is unknown. Has some ASCII strings in savedata, but they seem to be from the game binary not user input?Ĭhecksum is unknown, save has ASCII strings. The checksum seemed to be identical to arcade hoops, but when save modification was attempted the game appeared to reset the high-scores? Save slots are obfuscated, the algorithm is understood for all but the first save slot. 5 DSiWare that were already obtained for analysisÄSiWare which probably aren't exploitable.4 DSiWare that probably don't have vulnerabilities. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |