Displaying test cases 248176 - 248200 of 248586 in total
-
The test cases shows hard-coded password is not used.
-
The test case shows a Heap Overflow will not occur when assigning a character \'a\' to a heap buffer. The code has array address complexity.
-
The test case shows a Heap Overflow will not occur when assigning a character \'a\' to a heap buffer. The code has scope complexity.
-
The test case shows a Heap Overflow will not occur when assigning a character \'a\' to a heap buffer.
-
Pointer is initialized before use.
-
Allocated memory is deleted after use.
-
Allocated memory is deleted after use. There will be no memory leak.
-
The test cases shows passwords are stored in the system and not hard coded.
-
The test cases shows passwords are stored in the system and not hard coded.
-
The test cases shows passwords are stored in the system and not hard-coded.
-
The test cases shows passwords are stored in a vector and not hard-coded.
-
The test cases shows hard-coded passwords is not used.
-
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.
-
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.
-
A software system that accepts and executes input in the form of operating system commands (e.g. system()) could allow an attacker with lesser privileges than the target software to execute commands with the elevated privileges of the executing process.
-
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.
-
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.
-
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.
-
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.
-
Null Dereference in a Index Alias complexity
-
The pointer p is dereferenced even though the value is null.
-
The pointer is dereferenced even though the value is null in the \'function\' call.
-
The pointer p is dereferenced even though the value is null.