Address Space Layout Randomization
Also called ASLR.
Randomizing memory layout so attackers can't predict addresses.
What it is
A mitigation that randomizes the base addresses of the stack, heap, libraries, and executable each time a program runs. Without known addresses, attackers cannot reliably hardcode where their payload or gadgets live.
Why it matters
ASLR raises the cost of exploitation by forcing attackers to find an information leak first. In IR, knowing whether ASLR was enabled and effective helps assess how plausible a claimed exploit really was.
In practice
An exploit fails on a reboot because the target library loaded at a new random base, breaking its hardcoded gadget addresses.
What to look for
- Modules loaded at the same address every boot.
- Binaries built without relocation support.
- Leaks that reveal base addresses.
Common mistake
Treating it as a fix. One information leak defeats it.
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
- Data Execution Prevention: Marking data memory non-executable to block injected code.
- Information Leak: Disclosing memory contents to defeat randomization or steal secrets.
- Position-Independent Executable: A binary built to load at a random base, enabling full ASLR.