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/unrardll-0.1.4/src/unrardll/wrapper.cpp FINAL RESULTS: data/unrardll-0.1.4/src/unrardll/wrapper.cpp:28:5: [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. char callback_error[CALLBACK_ERROR_SZ + 1]; data/unrardll-0.1.4/src/unrardll/wrapper.cpp:246:5: [2] (buffer) wchar_t: 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. wchar_t pathbuf[4096] = {0}; data/unrardll-0.1.4/src/unrardll/wrapper.cpp:247:5: [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. char comment_buf[MAX_COMMENT_LENGTH]; data/unrardll-0.1.4/src/unrardll/wrapper.cpp:316:48: [1] (buffer) wcslen: 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). filename = wchar_to_unicode(fh->FileNameW, wcslen(fh->FileNameW)); ANALYSIS SUMMARY: Hits = 4 Lines analyzed = 492 in approximately 0.04 seconds (11656 lines/second) Physical Source Lines of Code (SLOC) = 421 Hits@level = [0] 10 [1] 1 [2] 3 [3] 0 [4] 0 [5] 0 Hits@level+ = [0+] 14 [1+] 4 [2+] 3 [3+] 0 [4+] 0 [5+] 0 Hits/KSLOC@level+ = [0+] 33.2542 [1+] 9.50119 [2+] 7.12589 [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.