Identificación de vulnerabilidades en binarios

Welcome! In reverse engineering, understanding vulnerabilities is key. These are flaws in software that an attacker can exploit to gain control or cause damage.

We'll explore common types found in compiled binaries, focusing on how they arise and what they look like.

A buffer is a contiguous block of memory allocated to hold data, like an array or a string. Think of it as a fixed-size container.

• Buffer Overflow: Happens when a program tries to write more data into a buffer than it can hold.
• This extra data "overflows" into adjacent memory regions, potentially corrupting other data or even overwriting critical program instructions.

Here's a basic C program using a fixed-size buffer. Notice the char buffer[10]; line, which reserves 10 bytes for our string.

Run this code to see how a string fits into the buffer.

What happens if we try to copy a string longer than 10 characters into our buffer? The strcpy function doesn't check bounds, so it will just keep writing.

This can lead to:

• Program crashes (segmentation faults).
• Corruption of adjacent data.
• Potential execution of malicious code (advanced exploitation).

Modern compilers and OSes have protections, but the core vulnerability remains.

Format string vulnerabilities occur when a program uses user-supplied input as the format string argument in functions like printf() or sprintf().

The format string (e.g., "%s", "%d") tells printf how to interpret and print subsequent arguments. If an attacker controls this string, they can:

• Read data from the stack.
• Write arbitrary data to arbitrary memory locations.

This example shows how an attacker could use format specifiers to peek at stack memory. The printf function expects arguments matching its format string.

If the format string comes from untrusted input, it can be abused.

Computers store numbers using a fixed number of bits. An integer overflow happens when an arithmetic operation tries to create a numeric value that is too large to be represented within the available storage space.

• For unsigned integers, the value "wraps around" to zero.
• For signed integers, it can wrap around to a large negative number.

This can lead to unexpected behavior, buffer overflows (e.g., if a calculated size is too small), or security bypasses.

Watch what happens when we add 1 to the maximum possible value for an unsigned int. It "overflows" and wraps back to zero.

This unexpected behavior can be exploited if the result is used for memory allocation or loop counters.

These vulnerabilities often stem from unsafe programming practices, especially in languages like C/C++ that offer direct memory access.

• Buffer Overflows: Use bounds-checking functions (e.g., strncpy, snprintf) or higher-level languages/libraries.
• Format String Bugs: Always provide a constant format string literal to printf-like functions, never user input.
• Integer Overflows: Validate input, perform range checks, and use larger data types or arbitrary-precision arithmetic when necessary.

Which of the following scenarios describe a common binary vulnerability?

Great job! You've now been introduced to three fundamental binary vulnerabilities:

• Buffer Overflows: Writing past a buffer's allocated memory.
• Format String Bugs: Misusing format specifiers in print functions.
• Integer Overflows: Numbers exceeding their storage capacity and wrapping around.

Understanding these is crucial for analyzing binaries and identifying potential weak points. Next, we'll look at how to find these bugs using automated tools!