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/octave-signal-1.4.1/src/__fwht__.cc Examining data/octave-signal-1.4.1/src/__ultrwin__.cc Examining data/octave-signal-1.4.1/src/cl2bp.cc Examining data/octave-signal-1.4.1/src/cl2bp_lib.cc Examining data/octave-signal-1.4.1/src/cl2bp_lib.h Examining data/octave-signal-1.4.1/src/medfilt1.cc Examining data/octave-signal-1.4.1/src/octave-compat.h Examining data/octave-signal-1.4.1/src/remez.cc Examining data/octave-signal-1.4.1/src/sosfilt.cc Examining data/octave-signal-1.4.1/src/upfirdn.cc FINAL RESULTS: data/octave-signal-1.4.1/src/cl2bp_lib.cc:46:7: [4] (format) vsnprintf: If format strings can be influenced by an attacker, they can be exploited, and note that sprintf variations do not always \0-terminate (CWE-134). Use a constant for the format specification. if (vsnprintf(buf,20*1024-1,format,argptr) == -1) { data/octave-signal-1.4.1/src/cl2bp_lib.cc:45:3: [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 buf[20*1024]; data/octave-signal-1.4.1/src/cl2bp_lib.cc:47:5: [2] (buffer) strcpy: Does not check for buffer overflows when copying to destination [MS-banned] (CWE-120). Consider using snprintf, strcpy_s, or strlcpy (warning: strncpy easily misused). Risk is low because the source is a constant string. strcpy(buf, "#ERROR#"); ANALYSIS SUMMARY: Hits = 3 Lines analyzed = 3132 in approximately 0.13 seconds (25037 lines/second) Physical Source Lines of Code (SLOC) = 1950 Hits@level = [0] 8 [1] 0 [2] 2 [3] 0 [4] 1 [5] 0 Hits@level+ = [0+] 11 [1+] 3 [2+] 3 [3+] 1 [4+] 1 [5+] 0 Hits/KSLOC@level+ = [0+] 5.64103 [1+] 1.53846 [2+] 1.53846 [3+] 0.512821 [4+] 0.512821 [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.