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/cfourcc-0.1.2/cfourcc.c

FINAL RESULTS:

data/cfourcc-0.1.2/cfourcc.c:101:21:  [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 ((optchar = getopt (argc, argv, "d:u:ihf::")) != -1) {
data/cfourcc-0.1.2/cfourcc.c:35:9:  [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.
typedef char AVIHDR[AVILEN];
data/cfourcc-0.1.2/cfourcc.c:41: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 (str, &header[0x70], 4);
data/cfourcc-0.1.2/cfourcc.c:49: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 (str, &header[0xbc], 4);
data/cfourcc-0.1.2/cfourcc.c:56: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 (&header[0x70], str, 4);
data/cfourcc-0.1.2/cfourcc.c:65: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 (&header[0xbc], str, 4);
data/cfourcc-0.1.2/cfourcc.c:90:10:  [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 strused[5], strdesc[5];
data/cfourcc-0.1.2/cfourcc.c:151:9:  [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).
  fin = fopen (argv[optind], "rb");
data/cfourcc-0.1.2/cfourcc.c:185:8:  [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).
	fin = fopen (argv[optind], "r+b");

ANALYSIS SUMMARY:

Hits = 9
Lines analyzed = 210 in approximately 0.04 seconds (5850 lines/second)
Physical Source Lines of Code (SLOC) = 135
Hits@level = [0]   6 [1]   0 [2]   8 [3]   1 [4]   0 [5]   0
Hits@level+ = [0+]  15 [1+]   9 [2+]   9 [3+]   1 [4+]   0 [5+]   0
Hits/KSLOC@level+ = [0+] 111.111 [1+] 66.6667 [2+] 66.6667 [3+] 7.40741 [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.