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/aeskeyfind-1.0/aes.c Examining data/aeskeyfind-1.0/util.c Examining data/aeskeyfind-1.0/util.h Examining data/aeskeyfind-1.0/aes.h Examining data/aeskeyfind-1.0/aeskeyfind.c FINAL RESULTS: data/aeskeyfind-1.0/aeskeyfind.c:237: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 ((ch = getopt(argc, argv, "hvqt:")) != -1) { data/aeskeyfind-1.0/aeskeyfind.c:212:12: [2] (misc) open: 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). int fd = open(filename, O_RDONLY); ANALYSIS SUMMARY: Hits = 2 Lines analyzed = 404 in approximately 0.03 seconds (13057 lines/second) Physical Source Lines of Code (SLOC) = 317 Hits@level = [0] 16 [1] 0 [2] 1 [3] 1 [4] 0 [5] 0 Hits@level+ = [0+] 18 [1+] 2 [2+] 2 [3+] 1 [4+] 0 [5+] 0 Hits/KSLOC@level+ = [0+] 56.7823 [1+] 6.30915 [2+] 6.30915 [3+] 3.15457 [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.