Skip to main content

Loading the code workspace…

LC

Understand ASLR and Information Leaks

hard4/9

Understand Stack Canaries and How They Detect Overflows Understand NX Bit and Return-Oriented Programming

Language

Compiler

2.0s Limit 256MB

Submit and pass all tests to enable saving to GitHub.

Implementation

Implement a C program that demonstrates ASLR and information leaks.

Requirements:

Print the addresses of stack variables, heap allocations, and libc functions
Show that addresses change between runs when ASLR is enabled
Document how an information leak defeats ASLR
Explain brute-force bypass conceptually
Show how leaked addresses can be used to calculate other addresses

Success Criteria:

Stack and libc addresses are printed
ASLR behavior is documented in output
Information leak concept is explained

Why This Matters

Every mainstream Linux distribution ships with /proc/sys/kernel/randomize_va_space set to 2, and real exploit chains against browsers and daemons routinely pair a format-string or over-read bug with exactly the libc-offset arithmetic you compute here to defeat it. Heartbleed's severity partly came from how efficiently it leaked memory that could be repurposed to break ASLR in adjacent processes.

Hints

0 / 3 revealed

Validation Suite

main.c

Workspace 1.0

← Understand Stack Canaries and How They Detect OverflowsUnderstand NX Bit and Return-Oriented Programming →