Position-Independent Executable
Also called PIE, RELRO.
A binary built to load at a random base, enabling full ASLR.
What it is
An executable compiled so its code and data references are relative rather than fixed, allowing the whole program image to load at a randomized address. It extends ASLR to the main binary itself, not just shared libraries.
Why it matters
Without PIE, the main executable loads at a known address and provides a stable source of gadgets even when libraries are randomized. PIE plus RELRO hardening removes those reliable anchors from an attacker.
In practice
Because the binary was built as a PIE, its functions land at a new random base each run and can no longer be used as fixed ROP gadgets.
What to look for
- Binaries built without PIE, loading at fixed addresses.
- Checksec output on deployed software.
- Old builds that never got rebuilt.
Common mistake
Building the main binary with PIE but not its libraries. Every fixed module gives attackers a known address.
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.
- Information Leak: Disclosing memory contents to defeat randomization or steal secrets.