C Test Suite for Source Code Analyzer - weakness Test suite #45

The test case exposes a resource injection.

The test case shows a resource injection.

The test cases shows a resource injection.

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

The test case shows a Stack Overflow.

The test case shows a Stack Overflow.

The test case shows a Stack Overflow.

The test case exposes a Cross-Site Scripting (XSS) in C/CGI programming.

The test case exposes a Cross-Site Scripting (XSS) in C/CGI programming.

The test case shows a Cross Site scripting weakness in a C/CGI application.

Unchecked error condition; if we don\'t check the return of [em]scanf[/em] we don\'t know how many parameters have been passed.

Using the value of an unitialized variable is not safe.

Buffer overflow if the input is not validated. Every operation may write outside the bound of the statically allocated character array. From \"Secure Coding in C and C++\" by Robert C. Seacord. Page 28, Figure 2-2.

The test case shows a weakness of improper null termination with a buffer address type complexity.

Using the value of an unitialized variable is not safe. (from TCCLASP-5_6_4_10)

The test cases implements CVE-2002-1869: Don\'t check if you can write a log file allow attackers to avoid logging.

This test case shows a null pointer is dereferenced.

This is a CGI program which take some parameters values then print it. It shows Cross-Site Scripting in C. This test case replace Test case 1792.

This test case shows a block of memory is freed twice. This test case replaces 1446

Attempted "double free" of allocated memory.

Attempt to return a pointer to memory that has been freed. This replaces test case 2108

Attempt to return a pointer to memory that has been freed.

The test case shows a use of a allocated memory after freed.

The test case shows a use of a allocated memory after freed. This test case replaces test case 1915.

The test case shows a use of a allocated memory after freed.