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/libapache2-mod-defensible-1.4/mod_defensible.c FINAL RESULTS: data/libapache2-mod-defensible-1.4/mod_defensible.c:262:11: [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). len = strlen(ip); data/libapache2-mod-defensible-1.4/mod_defensible.c:312:21: [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). len_dnsbl = strlen(srv_elts[i]); data/libapache2-mod-defensible-1.4/mod_defensible.c:316:9: [1] (buffer) strncpy: Easily used incorrectly; doesn't always \0-terminate or check for invalid pointers [MS-banned] (CWE-120). strncpy(hostdnsbl, revip, len); data/libapache2-mod-defensible-1.4/mod_defensible.c:317:9: [1] (buffer) strncat: Easily used incorrectly (e.g., incorrectly computing the correct maximum size to add) [MS-banned] (CWE-120). Consider strcat_s, strlcat, snprintf, or automatically resizing strings. Risk is low because the source is a constant character. strncat(hostdnsbl, ".", 1); data/libapache2-mod-defensible-1.4/mod_defensible.c:318:9: [1] (buffer) strncat: Easily used incorrectly (e.g., incorrectly computing the correct maximum size to add) [MS-banned] (CWE-120). Consider strcat_s, strlcat, snprintf, or automatically resizing strings. strncat(hostdnsbl, srv_elts[i], len_dnsbl); ANALYSIS SUMMARY: Hits = 5 Lines analyzed = 415 in approximately 0.03 seconds (14149 lines/second) Physical Source Lines of Code (SLOC) = 288 Hits@level = [0] 0 [1] 5 [2] 0 [3] 0 [4] 0 [5] 0 Hits@level+ = [0+] 5 [1+] 5 [2+] 0 [3+] 0 [4+] 0 [5+] 0 Hits/KSLOC@level+ = [0+] 17.3611 [1+] 17.3611 [2+] 0 [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.