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/libtexttools-2.1.0/src/system.c Examining data/libtexttools-2.1.0/src/curses.c FINAL RESULTS: data/libtexttools-2.1.0/src/system.c:48:10: [4] (shell) execlp: This causes a new program to execute and is difficult to use safely (CWE-78). try using a library call that implements the same functionality if available. execlp( path, path, NULL ); data/libtexttools-2.1.0/src/system.c:50:10: [4] (shell) execlp: This causes a new program to execute and is difficult to use safely (CWE-78). try using a library call that implements the same functionality if available. execlp( path, path, param1, NULL ); data/libtexttools-2.1.0/src/system.c:52:10: [4] (shell) execlp: This causes a new program to execute and is difficult to use safely (CWE-78). try using a library call that implements the same functionality if available. execlp( path, path, param1, param2, NULL ); data/libtexttools-2.1.0/src/system.c:54:10: [4] (shell) execlp: This causes a new program to execute and is difficult to use safely (CWE-78). try using a library call that implements the same functionality if available. execlp( path, path, param1, param2, param3, NULL ); data/libtexttools-2.1.0/src/system.c:92:10: [4] (shell) execlp: This causes a new program to execute and is difficult to use safely (CWE-78). try using a library call that implements the same functionality if available. execlp( path, path, NULL ); data/libtexttools-2.1.0/src/system.c:94:10: [4] (shell) execlp: This causes a new program to execute and is difficult to use safely (CWE-78). try using a library call that implements the same functionality if available. execlp( path, path, param1, NULL ); data/libtexttools-2.1.0/src/system.c:96:10: [4] (shell) execlp: This causes a new program to execute and is difficult to use safely (CWE-78). try using a library call that implements the same functionality if available. execlp( path, path, param1, param2, NULL ); data/libtexttools-2.1.0/src/system.c:98:10: [4] (shell) execlp: This causes a new program to execute and is difficult to use safely (CWE-78). try using a library call that implements the same functionality if available. execlp( path, path, param1, param2, param3, NULL ); data/libtexttools-2.1.0/src/curses.c:42:8: [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. extern char Interface_String[255]; data/libtexttools-2.1.0/src/curses.c:49:1: [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 sline[181]; data/libtexttools-2.1.0/src/system.c:42:12: [2] (misc) open: 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). fd0 = open( "/dev/null", O_RDONLY ); data/libtexttools-2.1.0/src/system.c:44:12: [2] (misc) open: 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). fd1 = open( outfile, O_WRONLY | O_CREAT | O_TRUNC, S_IRUSR | S_IWUSR); data/libtexttools-2.1.0/src/system.c:85:12: [2] (misc) open: 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). fd0 = open( "/dev/null", O_RDONLY ); data/libtexttools-2.1.0/src/system.c:87:12: [2] (misc) open: 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). fd1 = open( "/dev/null", O_WRONLY ); data/libtexttools-2.1.0/src/system.c:89:12: [2] (misc) open: 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). fd2 = open( outfile, O_WRONLY | O_CREAT | O_TRUNC, S_IRUSR | S_IWUSR); ANALYSIS SUMMARY: Hits = 15 Lines analyzed = 749 in approximately 0.05 seconds (15831 lines/second) Physical Source Lines of Code (SLOC) = 529 Hits@level = [0] 1 [1] 0 [2] 7 [3] 0 [4] 8 [5] 0 Hits@level+ = [0+] 16 [1+] 15 [2+] 15 [3+] 8 [4+] 8 [5+] 0 Hits/KSLOC@level+ = [0+] 30.2457 [1+] 28.3554 [2+] 28.3554 [3+] 15.1229 [4+] 15.1229 [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.