I have another interesting project @DockerENT, @Trashemail take some time to review it as well.
I am quite passionate about exploiting binary files. The first time when I came across Buffer Overflow(a simple technique of exploitation), then I was not able to implement the same with the same copy of code on my system.
The reason for that was there was no consolidated document that would guide me thoroughly to write a perfect exploit payload for the program in case of system changes.
Also, there are very few descriptive blogs/tutorials that had helped me exploiting a given binary.
I have come up with the consolidation of Modern exploitation techniques (in the form of the tutorial) that will allow you to understand exploitation from scratch.
I will be using vagrant file to set up the system on a virtual box. To do the same in your system follow:
- Memory Layout of C program.
- ELF binaries.
- Overview of stack during function call.
- Assembly code for the function call and return.
- Concept of
- Executable memory.
- How Linux finds the binaries utilis?
- Simple exploit using Linux $PATH variable.
- What are stack overflows?
ASLR (basics), avoiding Stack protection.
- Buffer overflow:
- Changing Control of the program to return to some other function
- Shellcode injection in buffer and spawning the shell
Shellcode injection with ASLR enabled.
- Return to Libc attacks.
shell in non executable stack
- Stack organization in case
- This folder contains the set of questions to exploit binaries on the concept that we have learned so far.
- What is format string Vulnerability?
- Seeing the content of stack.
- Writing onto the stack.
- Writing to arbitrary memory location.
- Overriding GOT entry.
- Spawning shell with format string vuln.
- Arena, Bins, Chunks.
- Use after free exploit.
- Double free exploit.