The test case avoids a use of an allocated memory after being freed.

An example to prevent heap overflow.

The test cases implements CVE-2002-1869: Checks if you can write a log file allow attackers to avoid logging.

Initializing a variable to avoid using its unitialized value.

The test case avoids improper null termination with a buffer address type complexity.

No buffer overflow even if the input is not validated. Every operation may write outside the bound of the statically allocated character array.

The variable px now is initialized, avoiding the use of an uninitialized value.

No memory leak, the allocated memory is freed.

The SQL Injection is not possible because the arguments are validated before the MySQL query.

If we check the return of scanf we know how many parameters have been passed.

The test case shows a correct pointer scaling.

The test case prevents a memory leak by releasing memory allocated in a loop.

The test case prevents a memory leak with a pointer which is in a structure.

The test case avoids a Cross-Site Scripting (XSS) in a C/CGI program with scope complexity.

The test case avoids a Cross-Site Scripting (XSS) in a C/CGI program with a string which is in a structure.

The test case avoids a Cross-Site Scripting (XSS) in a C/CGI program with an address alias level code complexity.

The test case avoids a Stack Overflow by fixing a bad loop exit condition (and start index).

The test case avoids a Stack Overflow by fixing a bad array index.

The test case avoids a Stack Overflow by fixing a bad array index.

The test case avoids a resource injection weakness in a scoping context.

The test case avoids a resource injection with a string which is in a structure.

The test case avoids a resource injection.

The test case avoids a resource injection with an address alias level code complexity.

The test case avoids an OS Command Injection in scope complexity.

The test case avoids an OS Command Injection weakness in a loop.