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/libeot-0.01/inc/libeot/EOT.h
Examining data/libeot-0.01/inc/libeot/EOTError.h
Examining data/libeot-0.01/inc/libeot/libeot.h
Examining data/libeot-0.01/src/ctf/parseCTF.c
Examining data/libeot-0.01/src/ctf/parseCTF.h
Examining data/libeot-0.01/src/ctf/parseTTF.c
Examining data/libeot-0.01/src/ctf/parseTTF.h
Examining data/libeot-0.01/src/ctf/SFNTContainer.c
Examining data/libeot-0.01/src/ctf/SFNTContainer.h
Examining data/libeot-0.01/src/lzcomp/ahuff.c
Examining data/libeot-0.01/src/lzcomp/AHUFF.H
Examining data/libeot-0.01/src/lzcomp/bitio.c
Examining data/libeot-0.01/src/lzcomp/BITIO.H
Examining data/libeot-0.01/src/lzcomp/ERRCODES.H
Examining data/libeot-0.01/src/lzcomp/liblzcomp.c
Examining data/libeot-0.01/src/lzcomp/liblzcomp.h
Examining data/libeot-0.01/src/lzcomp/lzcomp.c
Examining data/libeot-0.01/src/lzcomp/LZCOMP.H
Examining data/libeot-0.01/src/lzcomp/mtxmem.c
Examining data/libeot-0.01/src/lzcomp/MTXMEM.H
Examining data/libeot-0.01/src/util/logging.h
Examining data/libeot-0.01/src/util/max.h
Examining data/libeot-0.01/src/util/stream.h
Examining data/libeot-0.01/src/util/stream.c
Examining data/libeot-0.01/src/libeot.c
Examining data/libeot-0.01/src/EOT.c
Examining data/libeot-0.01/src/writeFontFile.c
Examining data/libeot-0.01/src/flags.h
Examining data/libeot-0.01/src/triplet_encodings.c
Examining data/libeot-0.01/src/triplet_encodings.h
Examining data/libeot-0.01/src/writeFontFile.h
Examining data/libeot-0.01/src/eot2ttf.c

FINAL RESULTS:

data/libeot-0.01/src/EOT.c:153:3:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination (CWE-120).
  Make sure destination can always hold the source data.
  memcpy(&(out->panose), scanner, 10);
data/libeot-0.01/src/ctf/SFNTContainer.h:17:3:  [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 tag[4];
data/libeot-0.01/src/ctf/parseCTF.c:751: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 tag[4];
data/libeot-0.01/src/eot2ttf.c:38:16:  [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 fildes = open(argv[1], O_RDONLY);
data/libeot-0.01/src/eot2ttf.c:46:19:  [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).
  FILE *outFile = fopen(outFileName, "wb");
data/libeot-0.01/src/lzcomp/ahuff.c:428: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 stackArr[50]; /* use this to reverse the bits */
data/libeot-0.01/src/lzcomp/liblzcomp.c:90: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).
	FILE *in = fopen(argv[1], "rb");
data/libeot-0.01/src/lzcomp/liblzcomp.c:118:3:  [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 fnBuf[10];
data/libeot-0.01/src/lzcomp/liblzcomp.c:119:3:  [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(fnBuf, "%d.ctf", i + 1);
data/libeot-0.01/src/lzcomp/liblzcomp.c:120:15:  [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).
		FILE *out = fopen(fnBuf, "wb");
data/libeot-0.01/src/util/stream.c:304:3:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination (CWE-120).
  Make sure destination can always hold the source data.
  memcpy(sOut->buf + sOut->pos, sIn->buf + sIn->pos, length);

ANALYSIS SUMMARY:

Hits = 11
Lines analyzed = 5094 in approximately 0.16 seconds (31475 lines/second)
Physical Source Lines of Code (SLOC) = 4126
Hits@level = [0]  16 [1]   0 [2]  11 [3]   0 [4]   0 [5]   0
Hits@level+ = [0+]  27 [1+]  11 [2+]  11 [3+]   0 [4+]   0 [5+]   0
Hits/KSLOC@level+ = [0+] 6.54387 [1+] 2.66602 [2+] 2.66602 [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.