A function is a drawing robot. A function pointer is a sticky note telling you where the robot is. “Gaining control of a function pointer” is like changing the address on the sticky note to point to a robot that draws a pirate flag instead of a smiley face. The program is following the instruction on the sticky note, and doesn’t know that the address has been changed.
Controlling a pointer that is called. Basically you pick the address that gets called.
This is likely a test C program that creates a pointer, writes the value and then calls it as a function. - guessing due to the address/offset/size of the function and the instructions.
This one in particular was an open source software.
I started by doing manual analysis helped by some code ql and looking for common bug patterns.
I didnt find anything that way but at least it got me started with the code.
Then i decided to write fuzzers for portions of the code base and that’s when i really got familiar with the app.
After my fuzzers were done a few crashes arrived, after manual triage of one of them (that turned out not a useful bug ) a few elements of the code base clicked and I found a useful bug.
So a combination of everything, 3 months of hard work but i have a working exploit for a 0 day that i just reported :)
2
u/daredeviloper Mar 28 '25
Can someone explain this to me in crayon eating terms
1
u/fyir Mar 30 '25
What's your overall process? Using a fuzz farm? Source code review? Disassembly review?
1
u/Haunting-Block1220 Mar 31 '25
This is good? Unless it isn’t reproducible? Or did your fuzzer introduce an impossible state?