Flawfinder version 2.0.10, (C) 2001-2019 David A. Wheeler. Number of rules (primarily dangerous function names) in C/C++ ruleset: 223 Examining data/gmotionlive-1.0/gmotionlive.c FINAL RESULTS: data/gmotionlive-1.0/gmotionlive.c:111:7: [4] (buffer) strcpy: Does not check for buffer overflows when copying to destination [MS-banned] (CWE-120). Consider using snprintf, strcpy_s, or strlcpy (warning: strncpy easily misused). strcpy(boundary, netcam_line); data/gmotionlive-1.0/gmotionlive.c:279:2: [4] (buffer) sprintf: Does not check for buffer overflows (CWE-120). Use sprintf_s, snprintf, or vsnprintf. sprintf(message, "%sNow viewing: %s\nURL: %s\nFrames viewed: %ld (%ld KBytes)\nFPS: %.1f (%.1f KBps)\n", data/gmotionlive-1.0/gmotionlive.c:31:1: [2] (buffer) char: Statically-sized arrays can be improperly restricted, leading to potential overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length. char netcam_line[NETCAM_LINELENGTH]; data/gmotionlive-1.0/gmotionlive.c:36:1: [2] (buffer) char: Statically-sized arrays can be improperly restricted, leading to potential overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length. char databuf[8192]; data/gmotionlive-1.0/gmotionlive.c:37:1: [2] (buffer) char: Statically-sized arrays can be improperly restricted, leading to potential overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length. char boundary[4096]; data/gmotionlive-1.0/gmotionlive.c:203:4: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination (CWE-120). Make sure destination can always hold the source data. memcpy(boundarystart + boundoff, start + checklen, netcam_boundarylen); data/gmotionlive-1.0/gmotionlive.c:109:28: [1] (buffer) strlen: Does not handle strings that are not \0-terminated; if given one it may perform an over-read (it could cause a crash if unprotected) (CWE-126). netcam_boundarylen = strlen(netcam_line); data/gmotionlive-1.0/gmotionlive.c:276:17: [1] (buffer) strlen: Does not handle strings that are not \0-terminated; if given one it may perform an over-read (it could cause a crash if unprotected) (CWE-126). message=malloc(strlen(about)+strlen(url_desc)+strlen(url)+80); data/gmotionlive-1.0/gmotionlive.c:276:31: [1] (buffer) strlen: Does not handle strings that are not \0-terminated; if given one it may perform an over-read (it could cause a crash if unprotected) (CWE-126). message=malloc(strlen(about)+strlen(url_desc)+strlen(url)+80); data/gmotionlive-1.0/gmotionlive.c:276:48: [1] (buffer) strlen: Does not handle strings that are not \0-terminated; if given one it may perform an over-read (it could cause a crash if unprotected) (CWE-126). message=malloc(strlen(about)+strlen(url_desc)+strlen(url)+80); ANALYSIS SUMMARY: Hits = 10 Lines analyzed = 334 in approximately 0.02 seconds (13810 lines/second) Physical Source Lines of Code (SLOC) = 288 Hits@level = [0] 0 [1] 4 [2] 4 [3] 0 [4] 2 [5] 0 Hits@level+ = [0+] 10 [1+] 10 [2+] 6 [3+] 2 [4+] 2 [5+] 0 Hits/KSLOC@level+ = [0+] 34.7222 [1+] 34.7222 [2+] 20.8333 [3+] 6.94444 [4+] 6.94444 [5+] 0 Dot directories skipped = 1 (--followdotdir overrides) Minimum risk level = 1 Not every hit is necessarily a security vulnerability. There may be other security vulnerabilities; review your code! See 'Secure Programming HOWTO' (https://dwheeler.com/secure-programs) for more information.