Displaying test cases 74301 - 74325 of 74617 in total
-
Aviod the problem of NULL pointer derefernece
-
Attempt to return a pointer to memory that has been freed.
-
Test of tool ability to identify a NULL pointer dereference.
-
The test case shows a use of a allocated memory after freed.
-
An example to prevent heap overflow.
-
Using the value of an unitialized variable is not safe. (from TCCLASP-5_6_4_10)
-
The test case shows avoiding improper null termination with a buffer address type complexity.
-
The test case shows a weakness of improper null termination with a buffer address type complexity.
-
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.
-
Using the value of an unitialized variable is not safe.
-
This is a test
-
The accidental addition of a data-structure sentinel can cause serious programing logic problems. (from TCCLASP-5_6_7_10)
-
Fixed strcpy to prevent stack overflow.
-
A heap overflow condition is a buffer overflow, where the buffer that can be overwritten is allocated in the heap portion of memory.
-
The test cases shows hard-coded password is not used.
-
Allocated memory is deleted after use.
-
Allocated memory is deleted after use. There will be no memory leak.
-
The test cases shows hard-coded passwords is used.
-
A stack-based buffer overflow condition is a condition where the buffer being overwritten is allocated on the stack. In the case of C++, misusing container vector could also cause stack overflow.
-
A software system that accepts and executes input in the form of operating system commands (e.g. system(), exec(), open()) should examine the input before its use.
-
Assume all input is malicious. Use an appropriate combination of black lists and white lists to ensure only valid and expected input is processed by the system.
-
If too few arguments are sent to a function, the function will still pop the expected number of arguments from the stack. Potentially, a variable number of arguments could be exhausted in a function as well. (from TCCLASP-5_6_2_10) (CWE 234) Note: some compilers that check whether too few argume...
-
The test case shows a use of a allocated memory after freed.
-
Pointer is initialized and checked before use.
-
Uninitialized variable