Safe sample input : backticks interpretation, reading the file /tmp/tainted.txt sanitize : use of ternary condition construction : prepared query and no right verification

Safe sample input : backticks interpretation, reading the file /tmp/tainted.txt sanitize : use of ternary condition construction : right verification

Safe sample input : backticks interpretation, reading the file /tmp/tainted.txt sanitize : use of ternary condition construction : fopen

Safe sample input : backticks interpretation, reading the file /tmp/tainted.txt sanitize : use of ternary condition construction : concatenation with simple quote

Safe sample input : backticks interpretation, reading the file /tmp/tainted.txt sanitize : use of ternary condition construction : interpretation with simple quote

Safe sample input : backticks interpretation, reading the file /tmp/tainted.txt sanitize : cast into int construction : concatenation and checks if the user is allowed to see this data

Safe sample input : backticks interpretation, reading the file /tmp/tainted.txt sanitize : cast into int construction : prepared query and right verification

Safe sample input : backticks interpretation, reading the file /tmp/tainted.txt sanitize : cast into int construction : right verification

The test case shows protection against the use of an allocated memory after being freed with an address alias level code complexity.

This test case avoids the problem of NULL pointer dereference.

This test shows a null pointer is not dereferenced, in a local control flow.

This test case shows an effort made to avoid OS command injection problem.

The test case avoids a use of an allocated memory after being freed with an extra allocation and free complexity.

Format string problems occur when a user has the ability to control or write completely the format string used to format data in the printf style family of C/C++ functions (fixed).

The test case avoids a Time-of-Check-Time-of-Use (TOCTOU) race condition between checking file attributes and then opening and writing to the file using random calls to function pointers.

The test case shows a Time-of-Check-Time-of-Use (TOCTOU) race condition between checking file attributes and then opening and writing to the file.

This test case shows no double free weakness.

The test case shows protection against the use of an allocated memory after being freed.

The test case shows protection against the use of an allocated memory after being freed with a string which is in a structure.

The test case shows protection against the use of an allocated memory after being freed with scope complexity.

Attepmts to assign a character to a memory that has been freed.

This test case shows a block of memory freed once.

This is a CGI program which take some parameters values then print it. It avoids Cross-Site Scripting in C within a looping complexity.

This test case avoids the problem of NULL pointer dereference.

Pointer is checked before use.