Digital only in JPN and USA regions only.Is this digital only or is there a physical version of it?
It did work, but you can't see what it did because you didn't offset the layer.
Try these inputs:
That sets the screen up, sets the glitch up, and then shows you an interesting bit. You can try other offsets in the third command if you want to explore.Code:XSCREEN 2 BGSCREEN 0,134217728,16 BGOFS 0,6400*16,0
So... from the information presented from this thread and a ROP being found (which means control is possible), does this pretty much mean that SmileBasic is exploitable. If we were to summarize what's going on?
So... from the information presented from this thread and a ROP being found (which means control is possible), does this pretty much mean that SmileBasic is exploitable. If we were to summarize what's going on?
It's exploitable. "got rop" means they have control.
now lets just hope all this goes unnoticed by the powers that be until something is released
So... from the information presented from this thread and a ROP being found (which means control is possible), does this pretty much mean that SmileBasic is exploitable. If we were to summarize what's going on?
Yep. Those are some of the function names. I also linked an editor on the first page; if you want to use it, inject the file into your extdata.This is what I get. Is that right?
Arm9HaxLoader?A9HL
We already got rop. Sorry manExcuse my language, but shit hell what have you done
I'm the guy who originally discovered that BGSCREEN can open RAM contents (though I didn't originally discover that the command was bugged, it goes further back than me). The bug was really fickle to work with so I never thought it would go anywhere and we decided to keep it a secret.
Until now, apparently.
The SMILEBASIC community is really small and indie, as is the software. I care about it very much, so I absolutely CANNOT risk that the software get pulled. We need to do some damage control, and fast. I don't know exactly WHAT is going on here, I just got here, so if someone could TLDR me that would be nice.
Basically, the RAM Contents are being used to modify the RAM in such a way in order to get out of the full sandbox and into userland. The exploit fully works apparently too...Excuse my language, but shit hell what have you done
I'm the guy who originally discovered that BGSCREEN can open RAM contents (though I didn't originally discover that the command was bugged, it goes further back than me). The bug was really fickle to work with so I never thought it would go anywhere and we decided to keep it a secret.
Until now, apparently.
The SMILEBASIC community is really small and indie, as is the software. I care about it very much, so I absolutely CANNOT risk that the software get pulled. We need to do some damage control, and fast. I don't know exactly WHAT is going on here, I just got here, so if someone could TLDR me that would be nice.
To summarize:
Smile basic let's you run arbitrary interpreted code in a sandbox. A glitch allows breaking out of the sandbox and directly editing ram. Doing this can allow for rop. Rop is the foundation for all userland exploits.
M-muh damage control!!Excuse my language, but shit hell what have you done
I'm the guy who originally discovered that BGSCREEN can open RAM contents (though I didn't originally discover that the command was bugged, it goes further back than me). The bug was really fickle to work with so I never thought it would go anywhere and we decided to keep it a secret.
Until now, apparently.
The SMILEBASIC community is really small and indie, as is the software. I care about it very much, so I absolutely CANNOT risk that the software get pulled. We need to do some damage control, and fast. I don't know exactly WHAT is going on here, I just got here, so if someone could TLDR me that would be nice.
Sorry, it's a forgone conclusion at this time that hbl for smilebasic is going to be released.Excuse my language, but shit hell what have you done
I'm the guy who originally discovered that BGSCREEN can open RAM contents (though I didn't originally discover that the command was bugged, it goes further back than me). The bug was really fickle to work with so I never thought it would go anywhere and we decided to keep it a secret.
Until now, apparently.
The SMILEBASIC community is really small and indie, as is the software. I care about it very much, so I absolutely CANNOT risk that the software get pulled. We need to do some damage control, and fast. I don't know exactly WHAT is going on here, I just got here, so if someone could TLDR me that would be nice.