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/bytes-circle-2.6/src/statistics.c Examining data/bytes-circle-2.6/src/circle.c Examining data/bytes-circle-2.6/src/statistics_circle.h FINAL RESULTS: data/bytes-circle-2.6/src/statistics.c:48:19: [3] (buffer) getopt: Some older implementations do not protect against internal buffer overflows (CWE-120, CWE-20). Check implementation on installation, or limit the size of all string inputs. while ((opt = getopt(argc, argv, "z:o:blLZnuBrvh")) != -1) data/bytes-circle-2.6/src/statistics.c:19: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 sigma_char[MAX_SIGMA_CHAR+1] = { data/bytes-circle-2.6/src/statistics.c:68:46: [2] (integer) atoi: Unless checked, the resulting number can exceed the expected range (CWE-190). If source untrusted, check both minimum and maximum, even if the input had no minus sign (large numbers can roll over into negative number; consider saving to an unsigned value if that is intended). if(!(two_circles_value = atoi(optarg))) { data/bytes-circle-2.6/src/statistics.c:167:5: [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 *SIZE_UNITS[6] = { "bytes", "kiB", "MiB", "GiB", "TiB", "PiB"}; data/bytes-circle-2.6/src/statistics.c:171:5: [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 buffer[BUFFER_LENGTH]; data/bytes-circle-2.6/src/statistics.c:200: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). hFile = fopen(szFile, "rb"); data/bytes-circle-2.6/src/statistics.c:196:9: [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). if (strlen(szFile)==0) { data/bytes-circle-2.6/src/statistics.c:347:9: [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). if (strlen(szFile)==0) ANALYSIS SUMMARY: Hits = 8 Lines analyzed = 614 in approximately 0.03 seconds (18798 lines/second) Physical Source Lines of Code (SLOC) = 397 Hits@level = [0] 39 [1] 2 [2] 5 [3] 1 [4] 0 [5] 0 Hits@level+ = [0+] 47 [1+] 8 [2+] 6 [3+] 1 [4+] 0 [5+] 0 Hits/KSLOC@level+ = [0+] 118.388 [1+] 20.1511 [2+] 15.1134 [3+] 2.51889 [4+] 0 [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.