CyberKit

Write-What-Where Condition

Controlling both the value written and the address it lands at.

What it is

A condition in which an attacker controls both the data to write (the what) and the destination address (the where). It is effectively a targeted arbitrary write, often the decisive step toward execution.

Why it matters

Write-what-where is a hallmark of high-severity memory bugs because it directly enables overwriting function pointers or saved state. Identifying it during triage usually escalates a finding to critical.

In practice

A corrupted linked-list unlink operation writes an attacker-chosen value to an attacker-chosen address, overwriting an entry in a function-pointer table.

What to look for

  • Unlinking or pointer writes driven by input.
  • Corrupted function pointers or vtables.
  • Kernel drivers that write to user supplied addresses.

Common mistake

Patching the symptom. Find the input that controls both the address and the value.

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

Sources