We will start by looking at the protections of the binary and we realize that NX is enabled so it will not let us execute code in memory. First we see that our attack vector are two inputs but we do not know the iteration that the program returns to us. So we will have to open gdb and analyze the code in search of how to exploit it and perform the important task of reverse engineering. After see..
Pwning in Linux
2019. 3. 27. 05:02
Notice
Recent Posts
Recent Comments
- Total
- Today
- Yesterday
Link
TAG
- arithmetic overflow/underflow
- leak libc
- buffer overflow
- write primitive
- cracking
- Windows
- XSS
- pwnable.xyz
- one gadget
- leak stack memory address
- dnspy
- Call oriented programming
- Pwnable.kr
- ASM
- GOT Dereferencing/Overwriting
- hijacking redirection flow
- stack pivot
- format string
- canary
- shellcode
- fake stack frame
- Backdoors
- theFaunia course
- 32Bit
- open-redirect
- return oriented programming
- x64dbg
- use after free
- html injection
- pwnable.tw
| 일 | 월 | 화 | 수 | 목 | 금 | 토 |
|---|---|---|---|---|---|---|
| 1 | 2 | 3 | 4 | 5 | 6 | 7 |
| 8 | 9 | 10 | 11 | 12 | 13 | 14 |
| 15 | 16 | 17 | 18 | 19 | 20 | 21 |
| 22 | 23 | 24 | 25 | 26 | 27 | 28 |
Archives