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/harminv-1.4.1/check.h Examining data/harminv-1.4.1/harminv-int.h Examining data/harminv-1.4.1/harminv-main.c Examining data/harminv-1.4.1/harminv.c Examining data/harminv-1.4.1/harminv.h Examining data/harminv-1.4.1/sines.c FINAL RESULTS: data/harminv-1.4.1/harminv-main.c:296:6: [4] (format) printf: If format strings can be influenced by an attacker, they can be exploited (CWE-134). Use a constant for the format specification. printf("harminv " PACKAGE_VERSION " by Steven G. Johnson\n" data/harminv-1.4.1/sines.c:88:6: [4] (format) printf: If format strings can be influenced by an attacker, they can be exploited (CWE-134). Use a constant for the format specification. printf("sines " PACKAGE_VERSION " by Steven G. Johnson.\n" data/harminv-1.4.1/harminv-main.c:290:18: [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 ((c = getopt(argc, argv, "hvVTFwnt:d:f:s:e:E:a:A:Q:")) != -1) data/harminv-1.4.1/sines.c:80:6: [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(time(NULL)); data/harminv-1.4.1/sines.c:82:18: [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 ((c = getopt(argc, argv, "hVvTRrn:t:N:s:")) != -1) data/harminv-1.4.1/sines.c:108:6: [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(atoi(optarg)); data/harminv-1.4.1/harminv-main.c:333:14: [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). nfmin = atoi(optarg); data/harminv-1.4.1/sines.c:108:12: [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). srand(atoi(optarg)); data/harminv-1.4.1/sines.c:111:10: [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). n = atoi(optarg); data/harminv-1.4.1/harminv-main.c:43:13: [1] (buffer) getc: Check buffer boundaries if used in a loop including recursive loops (CWE-120, CWE-20). c = getc(f); data/harminv-1.4.1/harminv-main.c:51:11: [1] (buffer) getc: Check buffer boundaries if used in a loop including recursive loops (CWE-120, CWE-20). c = getc(f); data/harminv-1.4.1/harminv-main.c:69:14: [1] (buffer) getc: Check buffer boundaries if used in a loop including recursive loops (CWE-120, CWE-20). int c = getc(f); data/harminv-1.4.1/harminv-main.c:77:14: [1] (buffer) getc: Check buffer boundaries if used in a loop including recursive loops (CWE-120, CWE-20). int c = getc(f); ANALYSIS SUMMARY: Hits = 13 Lines analyzed = 1764 in approximately 0.10 seconds (16908 lines/second) Physical Source Lines of Code (SLOC) = 1252 Hits@level = [0] 30 [1] 4 [2] 3 [3] 4 [4] 2 [5] 0 Hits@level+ = [0+] 43 [1+] 13 [2+] 9 [3+] 6 [4+] 2 [5+] 0 Hits/KSLOC@level+ = [0+] 34.345 [1+] 10.3834 [2+] 7.1885 [3+] 4.79233 [4+] 1.59744 [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.