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/jigzo-0.6.1/src/Texture.cxx Examining data/jigzo-0.6.1/src/Screen.cxx Examining data/jigzo-0.6.1/src/Loader.cxx Examining data/jigzo-0.6.1/src/main.cxx FINAL RESULTS: data/jigzo-0.6.1/src/main.cxx:1153:3: [4] (buffer) sprintf: Does not check for buffer overflows (CWE-120). Use sprintf_s, snprintf, or vsnprintf. sprintf(tmp,"Rotating pieces: %s",rotateEnabled ? " ON" : "OFF"); data/jigzo-0.6.1/src/main.cxx:1163:4: [4] (buffer) sprintf: Does not check for buffer overflows (CWE-120). Use sprintf_s, snprintf, or vsnprintf. sprintf(tmp,"Sound: %s",soundEnabled ? " ON" : "OFF"); data/jigzo-0.6.1/src/main.cxx:1169:3: [4] (buffer) sprintf: Does not check for buffer overflows (CWE-120). Use sprintf_s, snprintf, or vsnprintf. sprintf(tmp,"Connection tolerance: %s", data/jigzo-0.6.1/src/main.cxx:1511:2: [3] (random) srand: This function is not sufficiently random for security-related functions such as key and nonce creation (CWE-327). Use a more secure technique for acquiring random values. srand(t); data/jigzo-0.6.1/src/Loader.cxx:32:17: [2] (misc) fopen: Check when opening files - can an attacker redirect it (via symlinks), force the opening of special file type (e.g., device files), move things around to create a race condition, control its ancestors, or change its contents? (CWE-362). FILE *infile = fopen(filename.c_str(), "rb"); data/jigzo-0.6.1/src/Loader.cxx:71:17: [2] (misc) fopen: Check when opening files - can an attacker redirect it (via symlinks), force the opening of special file type (e.g., device files), move things around to create a race condition, control its ancestors, or change its contents? (CWE-362). FILE *infile = fopen(filename.c_str(), "rb"); data/jigzo-0.6.1/src/Loader.cxx:111:17: [2] (misc) fopen: Check when opening files - can an attacker redirect it (via symlinks), force the opening of special file type (e.g., device files), move things around to create a race condition, control its ancestors, or change its contents? (CWE-362). FILE* infile = fopen(filename.c_str(), "rb"); data/jigzo-0.6.1/src/Loader.cxx:156:13: [2] (misc) fopen: Check when opening files - can an attacker redirect it (via symlinks), force the opening of special file type (e.g., device files), move things around to create a race condition, control its ancestors, or change its contents? (CWE-362). FILE *fp = fopen(filename.c_str(), "rb"); data/jigzo-0.6.1/src/main.cxx:505:3: [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 tmp[4096]; data/jigzo-0.6.1/src/main.cxx:627:2: [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 tmp[256]; data/jigzo-0.6.1/src/main.cxx:791:2: [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 tmp[256]; data/jigzo-0.6.1/src/main.cxx:872:2: [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 tmp[256]; data/jigzo-0.6.1/src/main.cxx:1132:10: [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. static char str[256]; data/jigzo-0.6.1/src/main.cxx:1135:19: [2] (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). Risk is low because the source is a constant string. strinited =1 ; strcpy(str,"----"); data/jigzo-0.6.1/src/main.cxx:1140:4: [2] (buffer) sprintf: Does not check for buffer overflows (CWE-120). Use sprintf_s, snprintf, or vsnprintf. Risk is low because the source has a constant maximum length. sprintf(str,"%f",float(frames)/(float(SDL_GetTicks()-mark)/1000.)); data/jigzo-0.6.1/src/main.cxx:1151:3: [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 tmp[256]; data/jigzo-0.6.1/src/main.cxx:1161:4: [2] (buffer) sprintf: Does not check for buffer overflows (CWE-120). Use sprintf_s, snprintf, or vsnprintf. Risk is low because the source has a constant maximum length. sprintf(tmp,"Sound support failed"); data/jigzo-0.6.1/src/main.cxx:1166:3: [2] (buffer) sprintf: Does not check for buffer overflows (CWE-120). Use sprintf_s, snprintf, or vsnprintf. Risk is low because the source has a constant maximum length. sprintf(tmp,"Sound support not available"); data/jigzo-0.6.1/src/main.cxx:548:8: [1] (buffer) read: Check buffer boundaries if used in a loop including recursive loops (CWE-120, CWE-20). f.read(tmp,m); ANALYSIS SUMMARY: Hits = 19 Lines analyzed = 2082 in approximately 0.09 seconds (24277 lines/second) Physical Source Lines of Code (SLOC) = 1745 Hits@level = [0] 22 [1] 1 [2] 14 [3] 1 [4] 3 [5] 0 Hits@level+ = [0+] 41 [1+] 19 [2+] 18 [3+] 4 [4+] 3 [5+] 0 Hits/KSLOC@level+ = [0+] 23.4957 [1+] 10.8883 [2+] 10.3152 [3+] 2.29226 [4+] 1.7192 [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.