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/nbibtex-0.9.18/nbibtex.c Examining data/nbibtex-0.9.18/boyer-moore.c Examining data/nbibtex-0.9.18/nbib.c FINAL RESULTS: data/nbibtex-0.9.18/nbib.c:579:13: [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). FILE *f = fopen(filename, "r"); data/nbibtex-0.9.18/nbib.c:435:12: [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). for (n = strlen((char *)buf); buf[n-1] != '\n'; n = strlen((char *)buf)) { data/nbibtex-0.9.18/nbib.c:435:55: [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). for (n = strlen((char *)buf); buf[n-1] != '\n'; n = strlen((char *)buf)) { data/nbibtex-0.9.18/nbib.c:441: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). n = strlen((char *)buf) + 1; /* -1 below is incorrect without newline */ data/nbibtex-0.9.18/nbib.c:608:3: [1] (buffer) strncpy: Easily used incorrectly; doesn't always \0-terminate or check for invalid pointers [MS-banned] (CWE-120). strncpy((char *)rdr->filename, filename, lua_strlen(L, 1)+1); ANALYSIS SUMMARY: Hits = 5 Lines analyzed = 882 in approximately 0.06 seconds (15883 lines/second) Physical Source Lines of Code (SLOC) = 814 Hits@level = [0] 2 [1] 4 [2] 1 [3] 0 [4] 0 [5] 0 Hits@level+ = [0+] 7 [1+] 5 [2+] 1 [3+] 0 [4+] 0 [5+] 0 Hits/KSLOC@level+ = [0+] 8.59951 [1+] 6.14251 [2+] 1.2285 [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.