CyberKit

Data Execution Prevention

Also called DEP, NX, W^X.

Marking data memory non-executable to block injected code.

What it is

A mitigation that marks writable memory regions, such as the stack and heap, as non-executable. Attempting to run code from those pages triggers a fault, preventing classic inject-and-jump shellcode.

Why it matters

DEP/NX broke the simplest shellcode techniques and pushed attackers toward code-reuse like ROP. Confirming NX status helps responders understand which exploitation strategy an attacker had to use.

In practice

Shellcode written to the stack never runs because the stack pages are non-executable, forcing the attacker to chain existing code instead.

What to look for

  • Processes running with DEP turned off.
  • Memory regions made executable at runtime.
  • Calls to VirtualProtect that add execute rights.

Common mistake

Assuming it blocks every exploit. ROP reuses code that is already executable.

Practice it nearby

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

Read next

Sources