Buffer Overflows und Format-String-Schwachstellen

Appendix E. flawfinder

Flawfinder version 1.21, (C) 2001–2002 David A. Wheeler. Number of dangerous functions in C/C++ ruleset: 127 Examining fgets.c Examining getchar.c Examining getchar2.c Examining getenv.c Examining getenv2.c Examining gets.c Examining obsd.c Examining off-by-one.c Examining scanf.c Examining scanf2.c Examining snprintf.c Examining sprintf.c Examining strcat.c Examining strcpy.c Examining strncat.c Examining strncpy.c Examining strncpy2.c gets.c:9 [5] (buffer) gets: Does not check for buffer overflows. Use fgets() instead. getenv.c:14 [4] (buffer) strcpy: Does not check for buffer overflows when copying to destination. Consider using strncpy or strlcpy (warning, strncpy is easily misused). scanf.c:10 [4] (buffer) scanf: The ...