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/i8kutils-1.43/i8k.h Examining data/i8kutils-1.43/i8kctl.c Examining data/i8kutils-1.43/i8kctl.h Examining data/i8kutils-1.43/probe_i8k_calls_time.c Examining data/i8kutils-1.43/smm.c FINAL RESULTS: data/i8kutils-1.43/i8kctl.c:57:21: [4] (buffer) sscanf: The scanf() family's %s operation, without a limit specification, permits buffer overflows (CWE-120, CWE-20). Specify a limit to %s, or use a different input function. ret_nargs = sscanf(proc_i8k_str, "%s %s %s %d %d %d %d %d %d %d\n", data/i8kutils-1.43/i8kctl.c:37: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 i8k_ioctl_bios_version[4]; data/i8kutils-1.43/i8kctl.c:39: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 i8k_proc_format[16]; data/i8kutils-1.43/i8kctl.c:40: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 i8k_proc_bios_version[4]; data/i8kutils-1.43/i8kctl.c:41: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 i8k_proc_serial_version[16]; data/i8kutils-1.43/i8kctl.c:50: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 proc_i8k_str[64]; data/i8kutils-1.43/i8kctl.c:99: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 args[16]; data/i8kutils-1.43/i8kctl.c:197:35: [2] (integer) atoi: Unless checked, the resulting number can exceed the expected range (CWE-190). If source untrusted, check both minimum and maximum, even if the input had no minus sign (large numbers can roll over into negative number; consider saving to an unsigned value if that is intended). left = i8k_set_fan(I8K_FAN_LEFT, atoi(argv[1])); data/i8kutils-1.43/i8kctl.c:203:37: [2] (integer) atoi: Unless checked, the resulting number can exceed the expected range (CWE-190). If source untrusted, check both minimum and maximum, even if the input had no minus sign (large numbers can roll over into negative number; consider saving to an unsigned value if that is intended). right = i8k_set_fan(I8K_FAN_RIGHT, atoi(argv[2])); data/i8kutils-1.43/i8kctl.c:328:14: [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). i8k_fd = open(I8K_PROC, O_RDONLY); data/i8kutils-1.43/i8kctl.c:350:14: [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). i8k_fd = open(I8K_PROC, O_RDONLY); data/i8kutils-1.43/probe_i8k_calls_time.c:27:11: [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). i8k_fd = open(I8K_PROC, O_RDONLY); data/i8kutils-1.43/smm.c:55:11: [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). int fp = open("/proc/i8k", O_WRONLY); data/i8kutils-1.43/i8kctl.c:55:18: [1] (buffer) read: Check buffer boundaries if used in a loop including recursive loops (CWE-120, CWE-20). if ((rc_read=read(i8k_fd, proc_i8k_str, 64*sizeof(char))) != -1) { ANALYSIS SUMMARY: Hits = 14 Lines analyzed = 629 in approximately 0.05 seconds (13267 lines/second) Physical Source Lines of Code (SLOC) = 452 Hits@level = [0] 30 [1] 1 [2] 12 [3] 0 [4] 1 [5] 0 Hits@level+ = [0+] 44 [1+] 14 [2+] 13 [3+] 1 [4+] 1 [5+] 0 Hits/KSLOC@level+ = [0+] 97.3451 [1+] 30.9735 [2+] 28.7611 [3+] 2.21239 [4+] 2.21239 [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.