# local privilege escalation, remote delivery, emotional damage
help, whoami, sudo make me a sandwich, nmap yourmom, cat /etc/shadow. Or hit the red button.| Affected | yourmom <= latest |
|---|---|
| Fixed in | nothing. Not even in the nightly. |
| Vector | Port 80 (she's very open), port 443 (she's also secured, allegedly) |
| Root cause | Unbounded buffer. Everyone knows. Nobody says anything. |
| Reporter | Some guy on the internet. We forget who. |
| Exploited in the wild | Since before the wild. |
The vulnerability is a classic heap overflow. We tried to allocate a reasonable amount of space and the allocator said "nah, give me the whole heap." After malloc(mom) returned, the kernel's remaining free memory was tracked as a rounding error.
An attacker sends a crafted payload of one sentence. Mom's parser, lacking any bounds checking, begins unwinding the stack for a duration measured in geological epochs. Control of RIP is trivial. Control of RSP is a matter of "how much do you weigh again?"
$ ./yourmom2root --verbose [+] resolving yourmom.local ......... took 3 days (DNS TTL: 1 week) [+] stack too large for ASLR; kernel gave up [+] ret2libc: libc was her fridge [+] got uid=0(root) gid=0(root) groups=0(root),4(adm),69(nice) [+] cleaning up logs ... log file is larger than /var [!] disk full. shutting down.
SELinux. She will disable it by Tuesday.Is this a real exploit?
No. It's a joke. Please don't open a ticket with your vendor.
Is there a bug bounty?
Yes. We pay in exposure, and mom pays in leftovers.
Does this work on my mom?
Only yours.
Why the domain?
Because php2root, nginx2root, and friends gave us the format. We gave it a family.
Will there be a conference talk?
DEF CON has already declined, citing "capacity concerns."