Displaying test cases 74426 - 74450 of 74755 in total
-
This test case shows an effort is made to avoid OS command injection problem.
-
This test case show there is no double free weakness.
-
Attempt to return a pointer to memory that has been freed.
-
The test case shows a use of a allocated memory after freed.
-
An example to prevent heap overflow.
-
The test cases implements CVE-2002-1869: Don\'t check if you can write a log file allow attackers to avoid logging.
-
The test case exposes an OS Command Injection in scope complexity.
-
The test case exposes an OS Command Injection weakness in a loop.
-
The test case exposes an OS Command Injection weakness in a local control flow.
-
This test case shows a hard coded password in a for loop structure.
-
This test case shows no hard-coded password in a local control flow.
-
The test case exposes a password which is not hard-coded in the source code.
-
The test cases shows hard-coded passwords are not used; these passwords are in a array
-
Test tool ability to identify potential problem of the use of static internal buffer.
-
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.