Hello Everyone !
I’d like to present a new series this week. In this series, we will practice applications with Buffer overflow Vulnerability detected. In the first article, there will also be knowledge of theory in addition to practice. It’s going to be a long-term article. I don’t think you’re going to get bored because I had so much fun preparing it.
First of all, I have to say that I didn’t know much about Buffer Overflow before I wrote this article. Actually, there was, but it was like memorization. Therefore, I have researched all the details that should have been learned from the beginning and prepared this article. If I’m missing, if it’s my fault, I apologize in advance.
If I’m going to list the topics;
- Anatomy of Memory
- Anatomy of The Stack
- Anatomy of Buffer Overflow
- Steps to conduct a Buffer Overflow on PCMan FTP Server 2.0.7
- Meet Immunity Debugger
- Finding the Offset
- Overwriting the EIP
- Finding Bad Characters
- Finding the Right Module
- Generating Shell code.
The complete of hexadecimal characters we could possibly use in an exploit is shown below:
Due to “\x00” being the hex representation of a null byte, which will immediately terminate the remainder of the shellcode
Now, as a final action, we can add our sheLL32.dll. I’m adding padding so Shellcode.
Let’s use the msfvenom to create our She