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/xcalib-0.8.dfsg1/xcalib.c

FINAL RESULTS:

data/xcalib-0.8.dfsg1/xcalib.c:806:9:  [4] (buffer) strcpy:
  Does not check for buffer overflows when copying to destination [MS-banned]
  (CWE-120). Consider using snprintf, strcpy_s, or strlcpy (warning: strncpy
  easily misused).
        strcpy (in_name, argv[i]);
data/xcalib-0.8.dfsg1/xcalib.c:821:9:  [4] (buffer) strcpy:
  Does not check for buffer overflows when copying to destination [MS-banned]
  (CWE-120). Consider using snprintf, strcpy_s, or strlcpy (warning: strncpy
  easily misused).
        strcpy (in_name, win_default_profile);
data/xcalib-0.8.dfsg1/xcalib.c:1119:3:  [4] (format) vfprintf:
  If format strings can be influenced by an attacker, they can be exploited
  (CWE-134). Use a constant for the format specification.
  vfprintf (stderr, fmt, args);
data/xcalib-0.8.dfsg1/xcalib.c:1133:3:  [4] (format) vfprintf:
  If format strings can be influenced by an attacker, they can be exploited
  (CWE-134). Use a constant for the format specification.
  vfprintf (stdout, fmt, args);
data/xcalib-0.8.dfsg1/xcalib.c:1146:3:  [4] (format) vfprintf:
  If format strings can be influenced by an attacker, they can be exploited
  (CWE-134). Use a constant for the format specification.
  vfprintf (stdout, fmt, args);
data/xcalib-0.8.dfsg1/xcalib.c:235: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 cTmp[4];
data/xcalib-0.8.dfsg1/xcalib.c:255:10:  [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).
    fp = fopen(filename, "rb");
data/xcalib-0.8.dfsg1/xcalib.c:508: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 in_name[256] = { '\000' };
data/xcalib-0.8.dfsg1/xcalib.c:509: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_name[40] = { '\000' };
data/xcalib-0.8.dfsg1/xcalib.c:542: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 win_default_profile[MAX_PATH+1];
data/xcalib-0.8.dfsg1/xcalib.c:600:16:  [2] (integer) atoi:
  Unless checked, the resulting number can exceed the expected range
  (CWE-190). If source untrusted, check both minimum and maximum, even if the
  input had no minus sign (large numbers can roll over into negative number;
  consider saving to an unsigned value if that is intended).
      screen = atoi (argv[i]);
data/xcalib-0.8.dfsg1/xcalib.c:608:20:  [2] (integer) atoi:
  Unless checked, the resulting number can exceed the expected range
  (CWE-190). If source untrusted, check both minimum and maximum, even if the
  input had no minus sign (large numbers can roll over into negative number;
  consider saving to an unsigned value if that is intended).
      controller = atoi (argv[i]);
data/xcalib-0.8.dfsg1/xcalib.c:644:19:  [2] (integer) atoi:
  Unless checked, the resulting number can exceed the expected range
  (CWE-190). If source untrusted, check both minimum and maximum, even if the
  input had no minus sign (large numbers can roll over into negative number;
  consider saving to an unsigned value if that is intended).
      ramp_size = atoi(argv[i]);
data/xcalib-0.8.dfsg1/xcalib.c:805:10:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated; if given one it may
  perform an over-read (it could cause a crash if unprotected) (CWE-126).
      if(strlen(argv[i]) < 255)
data/xcalib-0.8.dfsg1/xcalib.c:820:10:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated; if given one it may
  perform an over-read (it could cause a crash if unprotected) (CWE-126).
      if(strlen(win_default_profile) < 255)

ANALYSIS SUMMARY:

Hits = 15
Lines analyzed = 1150 in approximately 0.04 seconds (29692 lines/second)
Physical Source Lines of Code (SLOC) = 952
Hits@level = [0]  70 [1]   2 [2]   8 [3]   0 [4]   5 [5]   0
Hits@level+ = [0+]  85 [1+]  15 [2+]  13 [3+]   5 [4+]   5 [5+]   0
Hits/KSLOC@level+ = [0+] 89.2857 [1+] 15.7563 [2+] 13.6555 [3+] 5.2521 [4+] 5.2521 [5+]   0
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.