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/t50-5.8.7/src/cidr.c
Examining data/t50-5.8.7/src/memalloc.c
Examining data/t50-5.8.7/src/include/t50_cidr.h
Examining data/t50-5.8.7/src/include/t50_randomizer.h
Examining data/t50-5.8.7/src/include/protocol/t50_rip.h
Examining data/t50-5.8.7/src/include/protocol/t50_gre.h
Examining data/t50-5.8.7/src/include/protocol/t50_ip.h
Examining data/t50-5.8.7/src/include/protocol/t50_rsvp.h
Examining data/t50-5.8.7/src/include/protocol/t50_ospf.h
Examining data/t50-5.8.7/src/include/protocol/t50_tcp_options.h
Examining data/t50-5.8.7/src/include/protocol/t50_egp.h
Examining data/t50-5.8.7/src/include/protocol/t50_igmp.h
Examining data/t50-5.8.7/src/include/protocol/t50_eigrp.h
Examining data/t50-5.8.7/src/include/t50_shuffle.h
Examining data/t50-5.8.7/src/include/t50_help.h
Examining data/t50-5.8.7/src/include/t50_errors.h
Examining data/t50-5.8.7/src/include/t50_cksum.h
Examining data/t50-5.8.7/src/include/t50_modules.h
Examining data/t50-5.8.7/src/include/t50_typedefs.h
Examining data/t50-5.8.7/src/include/configuration.h
Examining data/t50-5.8.7/src/include/t50_memalloc.h
Examining data/t50-5.8.7/src/include/t50_config.h
Examining data/t50-5.8.7/src/include/t50_netio.h
Examining data/t50-5.8.7/src/include/t50_defines.h
Examining data/t50-5.8.7/src/shuffle.c
Examining data/t50-5.8.7/src/randomizer.c
Examining data/t50-5.8.7/src/config.c
Examining data/t50-5.8.7/src/modules.c
Examining data/t50-5.8.7/src/netio.c
Examining data/t50-5.8.7/src/modules/eigrp.c
Examining data/t50-5.8.7/src/modules/igmpv1.c
Examining data/t50-5.8.7/src/modules/icmp.c
Examining data/t50-5.8.7/src/modules/ipsec.c
Examining data/t50-5.8.7/src/modules/ripv1.c
Examining data/t50-5.8.7/src/modules/tcp.c
Examining data/t50-5.8.7/src/modules/gre.c
Examining data/t50-5.8.7/src/modules/ripv2.c
Examining data/t50-5.8.7/src/modules/ip.c
Examining data/t50-5.8.7/src/modules/dccp.c
Examining data/t50-5.8.7/src/modules/egp.c
Examining data/t50-5.8.7/src/modules/igmpv3.c
Examining data/t50-5.8.7/src/modules/ospf.c
Examining data/t50-5.8.7/src/modules/udp.c
Examining data/t50-5.8.7/src/modules/rsvp.c
Examining data/t50-5.8.7/src/help/egp_help.c
Examining data/t50-5.8.7/src/help/tcp_udp_dccp_help.c
Examining data/t50-5.8.7/src/help/rip_help.c
Examining data/t50-5.8.7/src/help/ospf_help.c
Examining data/t50-5.8.7/src/help/eigrp_help.c
Examining data/t50-5.8.7/src/help/icmp_help.c
Examining data/t50-5.8.7/src/help/ip_help.c
Examining data/t50-5.8.7/src/help/gre_help.c
Examining data/t50-5.8.7/src/help/ipsec_help.c
Examining data/t50-5.8.7/src/help/igmp_help.c
Examining data/t50-5.8.7/src/help/rsvp_help.c
Examining data/t50-5.8.7/src/help/general_help.c
Examining data/t50-5.8.7/src/main.c
Examining data/t50-5.8.7/src/usage.c
Examining data/t50-5.8.7/src/cksum.c
Examining data/t50-5.8.7/src/errors.c

FINAL RESULTS:

data/t50-5.8.7/src/errors.c:42: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, str, args);
data/t50-5.8.7/src/main.c:111:3:  [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.
  printf ( INFO "PID=%u\n", getpid() );
data/t50-5.8.7/src/main.c:123:5:  [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.
    printf ( INFO "" PACKAGE_NAME " successfully launched at %s\n",
data/t50-5.8.7/src/main.c:224:7:  [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.
      printf ( INFO "" PACKAGE_NAME " successfully finished at %s\n",
data/t50-5.8.7/src/main.c:307:7:  [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.
      printf ( INFO "Sending %u packets...\n", co->threshold );
data/t50-5.8.7/src/main.c:357:5:  [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.
    printf ( INFO "(PID:%1$u) packets:    %2$" PRIu64 " (%3$" PRIu64 " bytes sent).\n"
data/t50-5.8.7/src/config.c:750:18:  [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).
      co->bits = atoi ( p ); /* NOTE: Range will be checked later. */
data/t50-5.8.7/src/config.c:1907: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).
  matches[0] = atoi ( t );
data/t50-5.8.7/src/config.c:1918:24:  [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).
      matches[i - 1] = atoi ( t );
data/t50-5.8.7/src/config.c:1936:25:  [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).
    if ( ( matches[4] = atoi ( t ) ) == 0 )
data/t50-5.8.7/src/config.c:2008: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 sep[2] = " ";
data/t50-5.8.7/src/randomizer.c:75: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).
  if ( ( _fd = open ( "/dev/urandom", O_RDONLY ) ) == -1 )
data/t50-5.8.7/src/config.c:1873:5:  [1] (buffer) strncpy:
  Easily used incorrectly; doesn't always \0-terminate or check for invalid
  pointers [MS-banned] (CWE-120).
    strncpy((d), (s), (len)); \
data/t50-5.8.7/src/randomizer.c:84:16:  [1] (buffer) read:
  Check buffer boundaries if used in a loop including recursive loops
  (CWE-120, CWE-20).
    if ( ( r = read ( _fd, p, endp - p ) ) == -1 )

ANALYSIS SUMMARY:

Hits = 14
Lines analyzed = 10669 in approximately 0.33 seconds (32331 lines/second)
Physical Source Lines of Code (SLOC) = 5542
Hits@level = [0]  10 [1]   2 [2]   6 [3]   0 [4]   6 [5]   0
Hits@level+ = [0+]  24 [1+]  14 [2+]  12 [3+]   6 [4+]   6 [5+]   0
Hits/KSLOC@level+ = [0+] 4.33057 [1+] 2.52616 [2+] 2.16528 [3+] 1.08264 [4+] 1.08264 [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.