According to Perforce $($n$.$d$.),$ approximately $90\%$ of security incidents that were reported are attributed to the exploitation of vulnerabilities in software code and design. Chapter five of Howard and LeBlanc $(2003)$ declares the buffer overrun to be $$Public Enemy #$1($p$.153).$ The authors go on to state that C and C$++$ give programmers a myriad of ways to $$shoot themselves in the foot$($p$.153).$ Specific examples of buffer overruns include stack overruns, heap overruns, array indexing errors, format string bugs, and Unicode and ANSI buffer size mismatches. Buffer overflows can be used to crash programs, corrupt data, and access sensitive files $($Perforce$,$ n$.$d$.).$