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..
Brainfuck Date: 08/01/2019-09/01/2019 @naivenom 4.1 Reconocimiento gef➤ checksec [+] checksec for '/home/binary/pwnable.kr/brainfuck/bf' Canary : Yes NX : Yes PIE : No Fortify : No RelRO : Partial Canary and NX (No shellcode) 4.2 Deep Reversing Analysis Como no puede ser de otra manera vamos solo a centrarnos en realizar reversing instrucción por instrucción y tomar notas de que es lo que esta s..
- Total
- Today
- Yesterday
- html injection
- Windows
- stack pivot
- Call oriented programming
- Pwnable.kr
- canary
- hijacking redirection flow
- write primitive
- dnspy
- Backdoors
- 32Bit
- open-redirect
- leak stack memory address
- format string
- shellcode
- use after free
- one gadget
- return oriented programming
- buffer overflow
- XSS
- fake stack frame
- cracking
- ASM
- theFaunia course
- pwnable.tw
- x64dbg
- pwnable.xyz
- GOT Dereferencing/Overwriting
- leak libc
- arithmetic overflow/underflow
일 | 월 | 화 | 수 | 목 | 금 | 토 |
---|---|---|---|---|---|---|
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 | 29 | 30 |