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/patman-1.2.2+dfsg/prefix_tree.h Examining data/patman-1.2.2+dfsg/fasta.h Examining data/patman-1.2.2+dfsg/main.cpp Examining data/patman-1.2.2+dfsg/global.h Examining data/patman-1.2.2+dfsg/prefix_tree.cpp Examining data/patman-1.2.2+dfsg/fasta.cpp FINAL RESULTS: data/patman-1.2.2+dfsg/prefix_tree.h:32:11: [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. unsigned char drop[5] ; data/patman-1.2.2+dfsg/prefix_tree.cpp:518:30: [1] (buffer) mismatch: Function does not check the second iterator for over-read conditions (CWE-126). This function is often discouraged by most C++ coding standards in favor of its safer alternatives provided since C++14. Consider using a form of this function that checks the second iterator before potentially overflowing it. size_t mm = next_in_queue->mismatch ; data/patman-1.2.2+dfsg/prefix_tree.h:62:16: [1] (buffer) mismatch: Function does not check the second iterator for over-read conditions (CWE-126). This function is often discouraged by most C++ coding standards in favor of its safer alternatives provided since C++14. Consider using a form of this function that checks the second iterator before potentially overflowing it. unsigned char mismatch ; ANALYSIS SUMMARY: Hits = 3 Lines analyzed = 1073 in approximately 0.04 seconds (25627 lines/second) Physical Source Lines of Code (SLOC) = 783 Hits@level = [0] 0 [1] 2 [2] 1 [3] 0 [4] 0 [5] 0 Hits@level+ = [0+] 3 [1+] 3 [2+] 1 [3+] 0 [4+] 0 [5+] 0 Hits/KSLOC@level+ = [0+] 3.83142 [1+] 3.83142 [2+] 1.27714 [3+] 0 [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.