Hacking Zelda Buffer overflow

[xvishon]

Found out that there is a glitch in OOT 3DS where the gravedigger will dig up unlimited hearts and even though they do not show up on screen the do give you more health past 20. Just wondering if anyone thinks picking up WAY TOO MANY heart pieces could give a good old crash or buffer overflow. Im still grabbing hearts to try it. anyone else thought of this?

 

[snikerz]

Sounds like a good idea!

As the ARM11 core used in the 3DS is a 32 Bit CPU, you'll need more than 2147483647 hearts to cause an integer overflow. Keep grabbin'!

 

[xvishon]

Sure. lol. That would take forever. Is there anyway to modify save files yet?

 

[urisma]

I doubt this would cause a buffer overflow. Just an integer overflow, which might crash the 3DS, but isn't exploitable since you can't insert your own code since a buffer isn't being overflowed. Even if this did cause a buffer overflow, it would be terribly difficult to even figure out if it's exploitable. To be exploitable then you'd have to overwrite the executable code or redirect IP to somewhere that your own code is. The problem with redirecting the IP to data that is actually code is that you might run into trouble with the noexecute feature, which is present in ARM11. Not sure if the 3DS uses it or not, but it'd be another obstacle to figure out.

 

[xvishon]

I thought it was an idea anyway.

 

[snikerz]

Sure. lol. That would take forever. Is there anyway to modify save files yet?

http://3dbrew.org/wiki/3DSaveTool
http://3dbrew.org/wiki/DSaveManager

 

[dangerboy]

Sounds like a good idea!

As the ARM11 core used in the 3DS is a 32 Bit CPU, you'll need more than 2147483647 hearts to cause an integer overflow. Keep grabbin'!

BEST. POAST. EVAR!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

 

[Crazy-S]

So when this Bug is Exploitable it would be the Twilight Hack NR.2 xD

Does this Bug appear on other Zelda Versions EU US JAP?
Has someone tested that out?

 

[Rydian]

So when this Bug is Exploitable

It's likely not.

 

[Crazy-S]

Don´t be such a killjoy when the Twilight hack was first encountered everyone said it won´t work blah blah and then it was the start of the Wii Homebrew
Why is everyone so friggin pessimistic?!
Give it atleast a try!

 

[enarky]

Don´t be such a killjoy when the Twilight hack was first encountered everyone said it won´t work blah blah and then it was the start of the Wii Homebrew
Why is everyone so friggin pessimistic?!
Give it atleast a try!

At least there was an actual overflow bug. This here is nothing. This is in the line of "Fucking magnets, how do they work".

s/magnets/computers/g

 

[pachura]

n00bz writing about buffer overflow like they understood how does it work...

 

[Rydian]

Don´t be such a killjoy when the Twilight hack was first encountered everyone said it won´t work blah blah and then it was the start of the Wii Homebrew
Why is everyone so friggin pessimistic?!
Give it atleast a try!

You didn't read past the first post, did you?

 

[walk12288]

This is completely useless aside from feeding someone's fantasy. There are two main types of buffer overflows: Heap and Stack overflows. Stack based overflows write more data to a buffer on the stack than has been allocated. This can allow for the overwriting of a function pointer or return address which could be executed to allow the running of your own code. Heap overflows affects the heap data area. Program data can be stored here and overwritten. Heap overflows are much less common, and we probably will not see one for a long time due to their complexity.

IF the system doesn't have buffer overflow protection in it, the most likely soft-mod exploit that we would see is a string buffer overflow. These can occur if an input field pushed onto the stack is not validated. By changing the string, you could possibly jump to another area in the code. If you jump to an area you control, then you have basically hijacked the thread.

For an overflow like this to occur a LOT of things need to line up perfectly. The system first, must not have any overflow protection. If it does, even if you found an exploit, the code execution would be halted. The second is that a developer needs to accidentally on purpose forget to validate user input that is pushed onto the stack. If both of these work, then you would need to be able to point and execute your own code. Which, on the 3DS could be a project in itself (seeing as not much is known about it currently).

*Please note that's for a stack overflow using the stringbuffer.

I hope that clears some things up for people...

 

[doyama]

This is completely useless aside from feeding someone's fantasy. There are two main types of buffer overflows: Heap and Stack overflows

---redacted---

I hope that clears some things up for people...

Regrettably most people stopped reading and understanding after "Heaps and Stacks overflows"

 

[RDilus]

ok this is what i am thinking
i dont own the game yet i will get it tomorrow
if this is really a bug
then it might be a hole to hack it
but it also might brick you're system when you try to hack it or anything else
to make it long story short
you dont know what can happen yet
if it turns out to be a kind of way to hack the 3ds
pls call this hax like this

Zelda heart attack

good name right

 

[Sheimi]

I am more than glad to try this glitch out. I wanna try something with this.

 

[Ron457x2]

If your looking for a possible buffer overflow, here ya go

[youtube]http://www.youtube.com/watch?v=0NvEHxcdWNk[/youtube]

 

[BrightNeko]

now how is that even done ... an I like how that one forces people to play to the end xD want to hack your 3DS finish OoT!!

 

[Ron457x2]

now how is that even done ... an I like how that one forces people to play to the end xD want to hack your 3DS finish OoT!!

Nintendo makes money, we finish the game and may have an exploit,
Its a win-win