3 ms·
> The executable stack bit doesn't bother me since I'm on an ARM Cortex. I'm not familiar enough with ARM - what does ARM Cortex give you here?
by geofft 7y ago
> The executable stack bit doesn't bother me since I'm on an ARM Cortex.
I'm not familiar enough with ARM - what does ARM Cortex give you here?
- Gibbon1 7y agoIt's what it doesn't give me. Doesn't have a memory management unit, so no stack execution protection. So no protection against classic stack smashing attacks. I saw a talk about weird machines. The upshot of it is if you can clobber the return address on the stack you can usually create a weird machine that you can then program[1]. Leads me to believe that if you are putting entrusted data and return addresses on the same stack you're in a state of sin security wise. https://en.wikipedia.org/wiki/Weird_machine https://en.wikipedia.org/wiki/Weird_machine [1] Also saw an exploit on an embedded system where they leveraged that even though the memory was locked you could set the program counter and read/write registers via jtag. Using that they were able in short order to recover the devices security keys and re-flash it with their own code.