Developer knowledge network ยท moderated exchange

Onbetrouwbare Code-gemeenschap

Ontwikkelaarsonderzoek, reverse engineering en coderingsgemeenschap

Knowledge indexLive
4Categories
919Threads
2.8KBerichten
Subforums Leiderbord Log in om te posten
Tutorial

Tracking memory heap allocations with Pageheap and WinDbg for UAF bugs

kernel_komrade
Driver Dev
MEMBER
Vertegenwoordiger: 145
Datum van deelname: Feb 2019
Berichten: 26
Bedankt: 45
1 maanden geleden ยท Jul 23, 2026 3:19 PM
#1

To diagnose Use-After-Free (UAF) and heap corruption bugs in complex C++ game codebases:

  1. Enable Pageheap in GFlags (gflags.exe /p /enable target_game.exe /full).
  2. Pageheap places an inaccessible guard page (PAGE_NOACCESS) immediately following every dynamic allocation.
  3. Attach WinDbg.
  4. When a dangling pointer reads freed memory or overflows a buffer by even 1 byte, the CPU triggers an immediate page fault and WinDbg breaks on the exact offending instruction!
ptr_arithmetic
C++ Wizard
MEMBER
Vertegenwoordiger: 162
Datum van deelname: May 2018
Berichten: 73
Bedankt: 42
1 maanden geleden ยท Jul 23, 2026 6:59 PM
#2

Pageheap is an absolute lifesaver for catching memory corruption bugs before shipping code.

vtable_slayer
Senior Reverser
MEMBER
Vertegenwoordiger: 215
Datum van deelname: Mar 2018
Berichten: 86
Bedankt: 61
1 maanden geleden ยท Jul 24, 2026 3:42 PM
#3

Requires significant RAM but pinpointing UAF bugs in 5 seconds is worth it.