heap0
http://exploit.education/phoenix/heap-zero/
Source
Luckily it gives us the source:
Analysis
So let's analyse what it does:
Allocates two chunks on the heap
Sets the
fp
variable of chunkf
to the address ofnowinner
Copies the first command-line argument to the
name
variable of the chunkd
Runs whatever the
fp
variable off
points at
The weakness here is clear - it runs a random address on the heap. Our input is copied there after the value is set and there's no bound checking whatsoever, so we can overrun it easily.
Regular Execution
Let's check out the heap in normal conditions.
We'll break right after the strcpy and see how it looks.
If we want, we can check the contents.
So, we can see that the function address is there, after our input in memory. Let's work out the offset.
Working out the Offset
Since we want to work out how many characters we need until the pointer, I'll just use a De Bruijn Sequence.
Let's break on and after the strcpy
. That way we can check the location of the pointer then immediately read it and calculate the offset.
So, the chunk with the pointer is located at 0x2493060
. Let's continue until the next breakpoint.
radare2 is nice enough to tell us we corrupted the data. Let's analyse the chunk again.
Notice we overwrote the size
field, so the chunk is much bigger. But now we can easily use the first value to work out the offset (we could also, knowing the location, have done pxq @ 0x02493060
).
So, fairly simple - 80 characters, then the address of winner
.
Exploit
We need to remove the null bytes because argv
doesn't allow them
Last updated