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/ruby-serialport-1.3.1/ext/native/win_serialport_impl.c Examining data/ruby-serialport-1.3.1/ext/native/serialport.h Examining data/ruby-serialport-1.3.1/ext/native/serialport.c Examining data/ruby-serialport-1.3.1/ext/native/posix_serialport_impl.c FINAL RESULTS: data/ruby-serialport-1.3.1/ext/native/posix_serialport_impl.c:137:9: [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). fd = open(port, O_RDWR | O_NOCTTY | O_NDELAY); data/ruby-serialport-1.3.1/ext/native/win_serialport_impl.c:74:4: [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 port[260]; /* Windows XP MAX_PATH. See http://msdn.microsoft.com/en-us/library/aa365247(VS.85).aspx */ data/ruby-serialport-1.3.1/ext/native/win_serialport_impl.c:115:9: [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). fd = open(port, O_BINARY | O_RDWR); ANALYSIS SUMMARY: Hits = 3 Lines analyzed = 2161 in approximately 0.07 seconds (32266 lines/second) Physical Source Lines of Code (SLOC) = 1524 Hits@level = [0] 3 [1] 0 [2] 3 [3] 0 [4] 0 [5] 0 Hits@level+ = [0+] 6 [1+] 3 [2+] 3 [3+] 0 [4+] 0 [5+] 0 Hits/KSLOC@level+ = [0+] 3.93701 [1+] 1.9685 [2+] 1.9685 [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.