CyberKit

Out-of-Bounds Write

Also called OOB write.

Writing to memory outside the bounds of an intended buffer.

What it is

A defect where code writes data at an index or offset outside a buffer's valid range. Depending on what sits at the target address, the write can corrupt data, pointers, or control structures.

Why it matters

Out-of-bounds writes generalize buffer overflows and are frequently the root cause behind code-execution bugs. The location and attacker control of the write determine how directly it becomes a write-what-where primitive.

In practice

A negative array index lets an attacker place a controlled value at a location of their choosing, overwriting a saved function pointer.

What to look for

  • Writes past an array end in sanitizer output.
  • Index values taken from input without checks.
  • CWE-787 in vendor advisories.

Common mistake

Checking only the upper bound. Negative indexes write out of bounds too.

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