Documentation
README
Exploiting glibc Heap Vulnerabilities
When to Use
- During authorized exploitation of programs that dynamically manage memory with
malloc/calloc/freeand contain use-after-free, double-free, heap overflow, or off-by-one (poison-null-byte) bugs. - When the stack is not the corruption surface but you control freed-chunk contents, chunk size fields, or allocation ordering, and want to convert that into an arbitrary read/write or code-pointer overwrite.
- When selecting a bin-specific primitive: tcache poisoning, fast-bin dup, unsorted-bin attack, large-bin attack, House of Force/Einherjar/Botcake, etc.
- When you must account for the target glibc version's mitigations (tcache
key, safe-linking, removed malloc hooks).
Critical: Concepts/Steps Most Often Missed
This is the opening of the README. Read the full README on GitHub.