Usage of GDB and Objdump in Exploit Development — A hands on exercise for Reverse Engineering.
Today I’m gonna Discuss about usage of GDB aka Gnome Debugger and as well as Objdump in Exploit Development. This is the most important part in the part of Hacking, where you will get to know how exploits are developed and how the attackers make use of it.




The first 3 snaps describe how the exploit will be developed with the help of GDB and the last snap is showing that you are grabbing the shellcode with the help of OBJDUMP.
The First snap is showing the disassembly of the program, which was discovered with a common vulnerability found in software i.e. Buffer Overflow. This vulnerability will occurs, when you send too many requests for a program whose buffer size is low than the request sent for a program.
The Second Snap is showing that 0x41414141 code, which shows that program operations was hampered which caused segmentation fault due to the highest request given to the program.
The third snap shows that the Overflowed Program Disassembly code has been compiled, to check the vulnerability something like this:
I had got 0x08048414 now to make confirmation of the program vulnerability I had typed the command run $(perl -e ‘print “A” x 40 . “\x08\x04\x84\x14”’) and pressed enter, so that it had triggered the vulnerability and the code “\x08\x04\x84\x14” can be used to write exploit in Metasploit Module.
And finally the last snap is nothing but grabbing shellcode, Objdump in Linux is one of the greatest tool for a Professional Hacker, where you can grab the Shellcode and can make penetration testing on the software, which gets triggered by vulnerability.