Advanced C Exploit Guidance
Budget: $30 – $250 USD
I’m working through a university-level computer security module and I want to deepen my hands-on understanding of how modern protections can be bypassed. My immediate focus is stack canaries: why they work, how compilers place them, and, most importantly, how to defeat them when crafting buffer-overflow exploits.
Here’s what I’d like from you:
• A step-by-step walkthrough (video or written) that shows how to locate a vulnerability in a C program, confirm the presence of canaries, and design a payload that survives the integrity check.
• Fully commented C exploit code aimed at a complex, realistic target—something more intricate than the typical hello-world overflow, ideally involving multiple functions and non-trivial input parsing.
• Live GDB sessions (commands and screenshots or recordings) so I can replicate every breakpoint, memory inspection, and register modification on my own machine.
• Explanations of each decision you make, covering stack layout, gadget selection, and avoidance of common pitfalls such as bad characters or ASLR interactions.
I already understand the basic theory behind buffer overflows, but I need expert-level guidance on writing reliable exploit code against hardened binaries. If you can deliver clear, reproducible examples that push beyond the simple tutorials, let’s work together.
Here’s what I’d like from you:
• A step-by-step walkthrough (video or written) that shows how to locate a vulnerability in a C program, confirm the presence of canaries, and design a payload that survives the integrity check.
• Fully commented C exploit code aimed at a complex, realistic target—something more intricate than the typical hello-world overflow, ideally involving multiple functions and non-trivial input parsing.
• Live GDB sessions (commands and screenshots or recordings) so I can replicate every breakpoint, memory inspection, and register modification on my own machine.
• Explanations of each decision you make, covering stack layout, gadget selection, and avoidance of common pitfalls such as bad characters or ASLR interactions.
I already understand the basic theory behind buffer overflows, but I need expert-level guidance on writing reliable exploit code against hardened binaries. If you can deliver clear, reproducible examples that push beyond the simple tutorials, let’s work together.