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/shhmsg-1.4.2/errno.c
Examining data/shhmsg-1.4.2/error.c
Examining data/shhmsg-1.4.2/fatal.c
Examining data/shhmsg-1.4.2/internal.h
Examining data/shhmsg-1.4.2/message.c
Examining data/shhmsg-1.4.2/progname.c
Examining data/shhmsg-1.4.2/shhmsg.h
Examining data/shhmsg-1.4.2/streams.c
Examining data/shhmsg-1.4.2/vars.c
Examining data/shhmsg-1.4.2/verbose.c
Examining data/shhmsg-1.4.2/debian/hello.c

FINAL RESULTS:

data/shhmsg-1.4.2/errno.c:62:2:  [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(GET_ERROR_STREAM, format, ap);
data/shhmsg-1.4.2/errno.c:105:2:  [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(GET_ERROR_STREAM, format, ap);
data/shhmsg-1.4.2/error.c:44:5:  [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(GET_ERROR_STREAM, format, ap);
data/shhmsg-1.4.2/fatal.c:49:5:  [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(GET_ERROR_STREAM, format, ap);
data/shhmsg-1.4.2/message.c:76:5:  [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(GET_MESSAGE_STREAM, format, ap);
data/shhmsg-1.4.2/progname.c:87:5:  [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(name, ret);
data/shhmsg-1.4.2/shhmsg.h:13:46:  [4] (format) printf:
  If format strings can be influenced by an attacker, they can be exploited
  (CWE-134). Use a constant for the format specification.
#define MSG_FORMAT_1 __attribute__ ((format (printf, 1, 2)))
data/shhmsg-1.4.2/shhmsg.h:14:46:  [4] (format) printf:
  If format strings can be influenced by an attacker, they can be exploited
  (CWE-134). Use a constant for the format specification.
#define MSG_FORMAT_2 __attribute__ ((format (printf, 2, 3)))
data/shhmsg-1.4.2/verbose.c:130:5:  [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(GET_VERBOSE_STREAM, format, ap);
data/shhmsg-1.4.2/verbose.c:61:14:  [3] (buffer) getenv:
  Environment variables are untrustable input if they can be set by an
  attacker. They can have any content and length, and the same variable can
  be set more than once (CWE-807, CWE-20). Check environment variables
  carefully before using them.
    envVal = getenv(envName);
data/shhmsg-1.4.2/progname.c:73: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.
    static char name[15];
data/shhmsg-1.4.2/verbose.c:49: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 envName[20];
data/shhmsg-1.4.2/verbose.c:60:5:  [2] (buffer) strcat:
  Does not check for buffer overflows when concatenating to destination
  [MS-banned] (CWE-120). Consider using strcat_s, strncat, strlcat, or
  snprintf (warning: strncat is easily misused). Risk is low because the
  source is a constant string.
    strcat(envName, "_LEVEL");
data/shhmsg-1.4.2/verbose.c:64:12:  [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).
    return atoi(envVal);
data/shhmsg-1.4.2/verbose.c:52:5:  [1] (buffer) strncpy:
  Easily used incorrectly; doesn't always \0-terminate or check for invalid
  pointers [MS-banned] (CWE-120).
    strncpy(envName, msgGetName(), 10);

ANALYSIS SUMMARY:

Hits = 15
Lines analyzed = 843 in approximately 0.04 seconds (21576 lines/second)
Physical Source Lines of Code (SLOC) = 319
Hits@level = [0]   8 [1]   1 [2]   4 [3]   1 [4]   9 [5]   0
Hits@level+ = [0+]  23 [1+]  15 [2+]  14 [3+]  10 [4+]   9 [5+]   0
Hits/KSLOC@level+ = [0+] 72.1003 [1+] 47.0219 [2+] 43.8871 [3+] 31.348 [4+] 28.2132 [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.