This course will try to explain to you the most common vulnerabilities identified in binary applications, i.e. buffer overflow, use-after-free, format string and integer under/overflow.


What will this course teach you?

  • Understanding the structure and purpose of the CPU and the memory

  • Basics of C programming

  • Basics of assembly

  • Understanding and exploiting basic buffer overflow

  • Understanding and exploiting basic use-after-free vulnerability

  • Understanding and exploiting basic format string vulnerability

  • Understanding and exploiting basic integer overflow and underflow vulnerabilities

What this course won’t teach you?

  • Reverse engineering

  • Coding in C or Assembly (although we will briefly cover both)

  • Explain, use and create fuzzers

  • Create your own shellcode

Minimum requirements:

  • Being familiar with computer

  • Being familiar with Linux

  • Being able to read C code (or similar language)

Before we start with the course, we will need to clarify and set the limit of what is a binary application and what are security vulnerabilities in the context of this course.

A binary application, also known as software, is a collection of instructions and data that tells a computer how to work. Instructions are machine language supported by an individual processor – typically a C​entral P​rocessor U​nit. Machine language consists of groups of binary values which are read and understood by the processor and correspond to an operation. After each instruction (i.e. operation) executed by the processor, the state of the computer change from its preceding state. For example, an instruction may change the value stored in a particular memory location in the computer. Softwares are usually written in high-level programming languages, such as C, C++ or .NET. Those languages are easier and more efficient for programmers because they are closer to natural languages than machine languages. High-level languages are translated into machine language using a compiler [1].

A security vulnerability is a weakness which allows an attacker to reduce a system’s information assurance [2]. Typically, a vulnerability will allow an attacker to compromise the C​onfidentiality and/or the I​ntegrity and/or the A​vailability of a system, hence the CIA concept in IT security.

For the sake of simplicity, this course will only cover applications running on Linux i386 (32-bit architecture). The high-level language used for demonstrations will be C since it is a widely known language that produces binary application relatively easy to understand. As for the lab, we will exercise on an Ubuntu virtual environment.


This course is licensed under the Apache Licence, Version 2.0.


About the author

My name is Antonin Beaujeant (@beaujeant), I’m a security professional doing mostly penetration tests. I don’t have extensive knowledge of binary security. Most of my experience in that area is coming from CTF and security challenges.

There is already tons of information available for free on the internet, but I decided to create my own course nonetheless. The topic can be complex and overwhelming, so I wanted to create a course the way I wish I would have learned it.

Everybody has its own preference for learning, e.g. reading, listening, visualizing, etc. This means the structure of this course might be odd and the way I explain things might not make sense to you. This is why I tried to add references as much as possible when suited so that you can get more information or read the same content with a different approach and style.

How to contribute

I’d be more than happy to hear your feedback for improvement in both substance and form. If you see any, feel free to report it via the GitHub issue page or via pull requests. I’m not a native English speaker, so this means there are probably lots of typos, repetitions and weird turns of phrase. Furthermore, as mentioned previously, I’m not an expert in binary security, so the content of this course might be inaccurate or maybe even incorrect. While sometimes, I’m inaccurate on purpose for the sake of simplicity, I did my best to avoid any incorrect statement and/or explanation. I created that course for educational purpose and would feel terrible if it actually misinformed its audience instead. So I would really appreciate if you could help me identifying erroneous content and improve this course.


  • [1]

  • [2]

  • CIA:

  • i386:

  • @beaujeant:

  • issue page:

  • pull requests: