9 ms·
In this case it's the same. The max stack depth is known, and the overflow easily triggerable and controllable from outside. It cannot get much easier. Wikiped
by rurban 7y ago
In this case it's the same. The max stack depth is known, and the overflow easily triggerable and controllable from outside. It cannot get much easier.
Wikipedia is a bit confused.
- NobodyNada 7y agoIt’s trivial to cause a stack overflow (as in allocating too much memory and running out of stack space), but how would you overwrite the return address? From what I can tell, the attacker can only cause the application to allocate lots of memory, not to overwrite memory.
- rurban 7y agoMemory DOS will not happen with normal recursion, only a tradional stackoverflow. And by adding some content after the fixed number of [ or {, this will by on the stack as argument to the recursive function. There are so many possible exploits. See eg. https://jon.oberheide.org/files/infiltrate12-thestackisback.pdf https://jon.oberheide.org/files/infiltrate12-thestackisback.... or search for "stack overflow recursion exploit"