Displaying test cases 4976 - 5000 of 5043 in total
-
CWE: 121 Stack Based Buffer Overflow BadSource: connect_socket Read data using a connect socket (client side) GoodSource: Larger than zero but less than 10 Sinks: GoodSink: Ensure the array index is valid BadSink : Improperly check the array index by not checking the upper bound Flow Varian...
-
CWE: 121 Stack Based Buffer Overflow BadSource: connect_socket Read data using a connect socket (client side) GoodSource: Larger than zero but less than 10 Sinks: GoodSink: Ensure the array index is valid BadSink : Improperly check the array index by not checking the upper bound Flow Varian...
-
CWE: 121 Stack Based Buffer Overflow BadSource: connect_socket Read data using a connect socket (client side) GoodSource: Larger than zero but less than 10 Sinks: GoodSink: Ensure the array index is valid BadSink : Improperly check the array index by not checking the upper bound Flow Varian...
-
CWE: 121 Stack Based Buffer Overflow BadSource: connect_socket Read data using a connect socket (client side) GoodSource: Larger than zero but less than 10 Sinks: GoodSink: Ensure the array index is valid BadSink : Improperly check the array index by not checking the upper bound Flow Varian...
-
CWE: 121 Stack Based Buffer Overflow BadSource: connect_socket Read data using a connect socket (client side) GoodSource: Larger than zero but less than 10 Sinks: GoodSink: Ensure the array index is valid BadSink : Improperly check the array index by not checking the upper bound Flow Varian...
-
CWE: 121 Stack Based Buffer Overflow BadSource: connect_socket Read data using a connect socket (client side) GoodSource: Larger than zero but less than 10 Sinks: GoodSink: Ensure the array index is valid BadSink : Improperly check the array index by not checking the upper bound Flow Varian...
-
CWE: 121 Stack Based Buffer Overflow BadSource: connect_socket Read data using a connect socket (client side) GoodSource: Larger than zero but less than 10 Sinks: GoodSink: Ensure the array index is valid BadSink : Improperly check the array index by not checking the upper bound Flow Varian...
-
CWE: 121 Stack Based Buffer Overflow BadSource: connect_socket Read data using a connect socket (client side) GoodSource: Larger than zero but less than 10 Sinks: GoodSink: Ensure the array index is valid BadSink : Improperly check the array index by not checking the upper bound Flow Varian...
-
CWE: 121 Stack Based Buffer Overflow BadSource: connect_socket Read data using a connect socket (client side) GoodSource: Larger than zero but less than 10 Sinks: GoodSink: Ensure the array index is valid BadSink : Improperly check the array index by not checking the upper bound Flow Varian...
-
CWE: 121 Stack Based Buffer Overflow BadSource: connect_socket Read data using a connect socket (client side) GoodSource: Larger than zero but less than 10 Sinks: GoodSink: Ensure the array index is valid BadSink : Improperly check the array index by not checking the upper bound Flow Varian...
-
CWE: 121 Stack Based Buffer Overflow BadSource: connect_socket Read data using a connect socket (client side) GoodSource: Larger than zero but less than 10 Sinks: GoodSink: Ensure the array index is valid BadSink : Improperly check the array index by not checking the upper bound Flow Varian...
-
CWE: 121 Stack Based Buffer Overflow BadSource: connect_socket Read data using a connect socket (client side) GoodSource: Larger than zero but less than 10 Sinks: GoodSink: Ensure the array index is valid BadSink : Improperly check the array index by not checking the upper bound Flow Varian...
-
Off-by-one error on bounds checking for strcat(). PLOVER: NUM.OBO, BUFF.OVER This replaces case 1320
-
No bounds checking on buffer during strcat(). PLOVER: BUFF.OVER This replaces case 1319
-
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 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.
-
user can input more then the max number of characters causing a stack overflow
-
user can input more then the max number of characters causing a stack overflow
-
The test case shows a Stack Overflow.
-
The test case shows a Stack Overflow.
-
Sprintf is used to copy a string to a stack buffer. A guard in the caller prevents an overflow from occuring
-
Sprintf is used to copy a string to a stack buffer. A guard in the caller is used to prevent an overflow from occuring but the guard is incorrect and an overflow can still occur.
-
Sprintf is used to copy a string to a stack buffer. A guard is used to prevent a buffer overflow condition.
-
Sprintf is used to copy a string to a stack buffer. A guard is used to prevent a buffer overflow condition but the guard is incorrect and a buffer overflow can still occur.
-
Sprintf is used to copy a string to a stack buffer. The length is guarded with a length specifier in the format string preventing a buffer overflow from occuring.