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/dxtool-0.1/dxtool.c

FINAL RESULTS:

data/dxtool-0.1/dxtool.c:16:3:  [4] (format) fprintf:
  If format strings can be influenced by an attacker, they can be exploited
  (CWE-134). Use a constant for the format specification.
  fprintf(stderr, dir == DIR_TO ? ">>" : "<<");
data/dxtool-0.1/dxtool.c:97:14:  [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((c = getopt(argc, argv, "p:s:e:mxhvrd")) != EOF)
data/dxtool-0.1/dxtool.c:95:12:  [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.
  unsigned char pb[8];
data/dxtool-0.1/dxtool.c:162: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).
  if((fd = open(port, O_RDWR)) == -1)
data/dxtool-0.1/dxtool.c:170:14:  [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.
    unsigned char b[10];
data/dxtool-0.1/dxtool.c:171:14:  [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.
    unsigned char c[10];
data/dxtool-0.1/dxtool.c:195:14:  [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.
    unsigned char b[10];
data/dxtool-0.1/dxtool.c:196:14:  [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.
    unsigned char c[10];
data/dxtool-0.1/dxtool.c:174:11:  [1] (buffer) read:
  Check buffer boundaries if used in a loop including recursive loops
  (CWE-120, CWE-20).
    while(read(fd, b, 8) == 8)
data/dxtool-0.1/dxtool.c:210:8:  [1] (buffer) read:
  Check buffer boundaries if used in a loop including recursive loops
  (CWE-120, CWE-20).
    if(read(fd, c, 8) != 8)

ANALYSIS SUMMARY:

Hits = 10
Lines analyzed = 273 in approximately 0.04 seconds (6499 lines/second)
Physical Source Lines of Code (SLOC) = 242
Hits@level = [0]  17 [1]   2 [2]   6 [3]   1 [4]   1 [5]   0
Hits@level+ = [0+]  27 [1+]  10 [2+]   8 [3+]   2 [4+]   1 [5+]   0
Hits/KSLOC@level+ = [0+] 111.57 [1+] 41.3223 [2+] 33.0579 [3+] 8.26446 [4+] 4.13223 [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.