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/mftrace-1.2.20+git20191022.3b4bc2e/gf2pbm.c

FINAL RESULTS:

data/mftrace-1.2.20+git20191022.3b4bc2e/gf2pbm.c:597:15:  [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, "bsdho:n:")) != -1)
data/mftrace-1.2.20+git20191022.3b4bc2e/gf2pbm.c:636:13:  [2] (misc) fopen:
  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).
  in_file = fopen (filename, "r");
data/mftrace-1.2.20+git20191022.3b4bc2e/gf2pbm.c:693:28:  [2] (misc) fopen:
  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).
  out_file = outfilename ? fopen (outfilename, "w") : NULL;
data/mftrace-1.2.20+git20191022.3b4bc2e/gf2pbm.c:696: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.
      static char s[100];
data/mftrace-1.2.20+git20191022.3b4bc2e/gf2pbm.c:697:7:  [2] (buffer) sprintf:
  Does not check for buffer overflows (CWE-120). Use sprintf_s, snprintf, or
  vsnprintf. Risk is low because the source has a constant maximum length.
      sprintf (s, "%d.pbm", glyph_num);
data/mftrace-1.2.20+git20191022.3b4bc2e/gf2pbm.c:699:18:  [2] (misc) fopen:
  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).
      out_file = fopen (s, "w");
data/mftrace-1.2.20+git20191022.3b4bc2e/gf2pbm.c:49:35:  [1] (buffer) getc:
  Check buffer boundaries if used in a loop including recursive loops
  (CWE-120, CWE-20).
#define one(fp)		((unsigned char) getc(fp))
data/mftrace-1.2.20+git20191022.3b4bc2e/gf2pbm.c:239:20:  [1] (buffer) getc:
  Check buffer boundaries if used in a loop including recursive loops
  (CWE-120, CWE-20).
	x = (signed char) getc(fp);

ANALYSIS SUMMARY:

Hits = 8
Lines analyzed = 712 in approximately 0.03 seconds (25899 lines/second)
Physical Source Lines of Code (SLOC) = 559
Hits@level = [0]  23 [1]   2 [2]   5 [3]   1 [4]   0 [5]   0
Hits@level+ = [0+]  31 [1+]   8 [2+]   6 [3+]   1 [4+]   0 [5+]   0
Hits/KSLOC@level+ = [0+] 55.4562 [1+] 14.3113 [2+] 10.7335 [3+] 1.78891 [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.