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/matroxset-0.4/fb.h Examining data/matroxset-0.4/videodev2.h Examining data/matroxset-0.4/matroxfb.h Examining data/matroxset-0.4/matroxset.c FINAL RESULTS: data/matroxset-0.4/matroxset.c:221:16: [3] (buffer) getopt: Some older implementations do not protect against internal buffer overflows (CWE-120, CWE-20). Check implementation on installation, or limit the size of all string inputs. while ((rtn = getopt(argc, argv, "o:f:mhdplc:e")) != -1) { data/matroxset-0.4/fb.h:120:2: [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 id[16]; /* identification string eg "TT Builtin" */ data/matroxset-0.4/fb.h:321: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 modename[40]; /* default video mode */ data/matroxset-0.4/fb.h:324:8: [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 open; /* Has this been open already ? */ data/matroxset-0.4/fb.h:334: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 fontname[40]; /* default font name */ data/matroxset-0.4/matroxset.c:287:7: [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(fb, O_RDWR); data/matroxset-0.4/videodev2.h:333:2: [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 APP_data[60]; /* Data in the JPEG APPn segment. */ data/matroxset-0.4/videodev2.h:336:2: [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 COM_data[60]; /* Data in JPEG COM segment */ ANALYSIS SUMMARY: Hits = 8 Lines analyzed = 1945 in approximately 0.07 seconds (29070 lines/second) Physical Source Lines of Code (SLOC) = 1446 Hits@level = [0] 26 [1] 0 [2] 7 [3] 1 [4] 0 [5] 0 Hits@level+ = [0+] 34 [1+] 8 [2+] 8 [3+] 1 [4+] 0 [5+] 0 Hits/KSLOC@level+ = [0+] 23.5131 [1+] 5.5325 [2+] 5.5325 [3+] 0.691563 [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.