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.
- Risk Scoring
Score a vulnerability with CVSS v3.1, or an incident across five dimensions, and see the reasoning behind each number.
- Map and Score
Map real procedures to ATT&CK techniques, then pick the CVSS v3.1 metrics for real vulnerabilities.
Read next
- Address Space Layout Randomization: Randomizing memory layout so attackers can't predict addresses.
- Return-Oriented Programming: Chaining existing code snippets ending in returns to run logic.
- Stack Canary: A guard value checked on return to detect stack overflows.