I made an account just to post this.
Mostly I have been a browser of this forum for a long time and like to look at random posts.
I have been developing an idea with a friend and we decided we wanted to share it with the community and see what they could do withit.
Exploit
Notes:
The basic premises state that you would essentially take an image from the switches SD card and edit it in a text editor. You would in theory add many characters to the file so the switch would not know what to do. Basic rules for computers say if a file is too large it would write that overflowing data somewhere else (buffer overflow). That data could be a homebrew launcher, program, game or some other thing that could be written on the switch itself. The reason we use JPEG images is that they are injectable/can be edited. The idea would be to somehow take some code (arm asm) and compile it into a jpeg and use the switch image viewer to access the program.
Mostly I have been a browser of this forum for a long time and like to look at random posts.
I have been developing an idea with a friend and we decided we wanted to share it with the community and see what they could do withit.
Exploit
Notes:
- Involves JPEG images and buffer overflow.
The basic premises state that you would essentially take an image from the switches SD card and edit it in a text editor. You would in theory add many characters to the file so the switch would not know what to do. Basic rules for computers say if a file is too large it would write that overflowing data somewhere else (buffer overflow). That data could be a homebrew launcher, program, game or some other thing that could be written on the switch itself. The reason we use JPEG images is that they are injectable/can be edited. The idea would be to somehow take some code (arm asm) and compile it into a jpeg and use the switch image viewer to access the program.
Or others 
