CyberKit

Heap Overflow

Also called heap buffer overflow.

Overflowing a heap allocation to corrupt adjacent chunks or metadata.

What it is

A buffer overflow in dynamically allocated (heap) memory, where excess data overwrites neighboring allocations or the allocator's bookkeeping metadata. Exploitation typically manipulates heap layout to control what gets corrupted.

Why it matters

Heap overflows are harder to exploit than stack ones but remain a common path to code execution in browsers and services. Understanding allocator behavior is essential for triaging heap-corruption crashes during analysis.

In practice

An image decoder under-allocates a buffer for pixel data and the overflow overwrites a function pointer stored in an adjacent heap object.

What to look for

  • Heap corruption messages from the allocator.
  • Crashes in free or malloc after input handling.
  • Length fields that are trusted from input.

Common mistake

Thinking the heap is safer than the stack. Heap bugs are a common path to code execution.

Practice it nearby

CyberKit has no tool for this term itself. These are the closest places to practice it.

In the field

Well-known tools where this shows up on the job. They are listed to show the landscape, not as a recommendation.

  • Nessus Commercial

    A vulnerability scanner that checks hosts for known flaws and missing patches.

  • Qualys VMDR Commercial

    A cloud platform that scans assets and ranks vulnerabilities for patching.

  • OpenVAS Open source

    An open source vulnerability scanner with a large set of checks.

  • Nuclei Open source

    Runs community templates that test for specific, newly published flaws.

Read next

  • Buffer Overflow: Writing past the end of a buffer to corrupt adjacent memory.
  • Heap Spray: Filling the heap with repeated payloads to land at a predictable spot.
  • Use-After-Free: Using a pointer after its memory has been freed and possibly reused.

Sources