The test case avoids a Stack Overflow by fixing a bad array index.

The test case shows a Stack Overflow with a bad array index.

The test case avoids a Stack-based Buffer Overflow.

The test case shows a Stack-based Buffer Overflow.

A strcpy does not overflow a stack buffer because a check is made to avoid an overflow condition.

A strcpy overflows a stack buffer. A check was made to avoid an overflow condition but the check is off by one.

An fgets is called with a correct bound.

An fgets is called with an incorrect bound allowing a stack buffer to be overrun.

An fgets is used in place of gets with a proper bounds check.

A gets is never safe for untrusted input due to lack of buffer length checks.

An ad-hoc string copy with bounds check does not overflows a stack buffer.

An ad-hoc string copy without bounds check overflows a stack buffer.

An ad hoc gets with bounds check does not allow a stack buffer to be overrun.

An ad hoc gets without bounds check allows a stack buffer to be overrun.

A string decode function properly checks for termination and no buffer overflow occurs.

A string decode function misses a termination check which allows the decode to proceed past the end of the buffer.

CVE-2012-4296

CVE-2013-2480

CWE: 121 Stack Based Buffer Overflow BadSource: Initialize data as a large string GoodSource: Initialize data as a small string Sinks: cpy BadSink : Copy data to string using wcscpy Flow Variant: 84 Data flow: data passed to class constructor and destructor by declaring the class object on ...

CWE: 121 Stack Based Buffer Overflow BadSource: Initialize data as a large string GoodSource: Initialize data as a small string Sinks: cpy BadSink : Copy data to string using wcscpy Flow Variant: 83 Data flow: data passed to class constructor and destructor by declaring the class object on ...

CWE: 121 Stack Based Buffer Overflow BadSource: Initialize data as a large string GoodSource: Initialize data as a small string BadSink : Copy data to string using wcscpy Flow Variant: 82 Data flow: data passed in a parameter to an virtual method called via a pointer

CWE: 121 Stack Based Buffer Overflow BadSource: Initialize data as a large string GoodSource: Initialize data as a small string Sinks: cpy BadSink : Copy data to string using wcscpy Flow Variant: 81 Data flow: data passed in a parameter to an virtual method called via a reference

CWE: 121 Stack Based Buffer Overflow BadSource: Initialize data as a large string GoodSource: Initialize data as a small string Sinks: cpy BadSink : Copy data to string using wcscpy Flow Variant: 74 Data flow: data passed in a map from one function to another in different source files

CWE: 121 Stack Based Buffer Overflow BadSource: Initialize data as a large string GoodSource: Initialize data as a small string Sinks: cpy BadSink : Copy data to string using wcscpy Flow Variant: 73 Data flow: data passed in a list from one function to another in different source files

CWE: 121 Stack Based Buffer Overflow BadSource: Initialize data as a large string GoodSource: Initialize data as a small string Sinks: cpy BadSink : Copy data to string using wcscpy Flow Variant: 72 Data flow: data passed in a vector from one function to another in different source files