``` Information leak Out-of-bounds Read Use After Free Integer Overflow or Wraparound Out-of-bounds Write Heap overflow ``` |
> The only way to reliably bypass DEP and ASLR is through an pointer > leak. This is a situation where a value on the stack, at a reliable > location, might be used to locate a usable function pointer or ROP > gadget. Once this is done, it is sometimes possible to create a > payload that reliably bypasses both protection mechanisms. |
|
|
POC: Proof of Concept CWE: Common Weakness Enumeration Top 25 list: https://cwe.mitre.org/top25/archive/2019/2019_cwe_top25.html ASLR: Address Space Layout Randomization https://en.wikipedia.org/wiki/Address_space_layout_randomization DEP: Data Execution Prevention https://en.wikipedia.org/wiki/Executable_space_protection ROP: Return-Oriented Programming https://en.wikipedia.org/wiki/Return-oriented_programming |