3 ms·
Writable exclusive OR eXecutable policy, applied to memory pages it makes memory safety bugs a lot harder to exploit, as an attacker can't simply load an execut
by brohee 11y ago
Writable exclusive OR eXecutable policy, applied to memory pages it makes memory safety bugs a lot harder to exploit, as an attacker can't simply load an executable payload (typically, shellcode) in the address space of the exploited program and jump to it...
- JoachimS 11y agoJust to emphasize (be picky): Logically it is exclusive or (XOR), not inclusive (OR). That is either write or execute, but not both.
- Avernar 11y agoToo be really picky, logically it's NAND. Not writable and not executable is valid. :)
- bentcorner 11y ago> as an attacker can't simply load an executable payload (typically, shellcode) in the address space of the exploited program and jump to it... Very interesting read on how this works in practice: https://www.corelan.be/index.php/2010/06/16/exploit-writing-tutorial-part-10-chaining-dep-with-rop-the-rubikstm-cube/ https://www.corelan.be/index.php/2010/06/16/exploit-writing-...