CyberKit

Use-After-Free

Also called UAF, dangling pointer.

Using a pointer after its memory has been freed and possibly reused.

What it is

A memory-corruption bug where a program continues to use a pointer after the underlying allocation has been freed. If the attacker reclaims that memory with controlled data before it is used, they can hijack the dangling reference.

Why it matters

Use-after-free is among the most prevalent exploitable bug classes in modern software, especially browsers and language runtimes. Detecting it usually requires sanitizers or careful heap analysis rather than a simple crash signature.

In practice

An object is freed but a stale pointer to it is later dereferenced, and the attacker has filled the reclaimed chunk with a fake virtual-method table.

What to look for

  • Crashes accessing freed memory, often caught by sanitizers.
  • Objects released in one path and used in another.
  • Browser and kernel advisories naming UAF.

Common mistake

Fixing it by adding a null check in one place. Find every path that still holds the pointer.

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

  • Heap Overflow: Overflowing a heap allocation to corrupt adjacent chunks or metadata.
  • Type Confusion: Treating a memory object as a different type than it actually is.
  • Heap Spray: Filling the heap with repeated payloads to land at a predictable spot.

Sources