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/adasockets-1.12/examples/rtems_init.c
Examining data/adasockets-1.12/examples/rtems_networkconfig.h
Examining data/adasockets-1.12/rtems/rtems_main.c
Examining data/adasockets-1.12/src/constants.c

FINAL RESULTS:

data/adasockets-1.12/examples/rtems_init.c:42:8:  [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  arg0[20] = "rtems";
data/adasockets-1.12/examples/rtems_init.c:43:8:  [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 *argv[20] = { arg0 };
data/adasockets-1.12/examples/rtems_init.c:68:7:  [2] (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). Risk is low because the source is a constant string.
      strcpy (arg0, "rtems");
data/adasockets-1.12/examples/rtems_init.c:144: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 command_line[ COMMAND_LINE_MAXIMUM ];
data/adasockets-1.12/examples/rtems_networkconfig.h:44: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 ethernet_address[6] = { 0x00, 0x11, 0x22, 0x33, 0x44, 0x55 };
data/adasockets-1.12/examples/rtems_init.c:73:5:  [1] (buffer) strncpy:
  Easily used incorrectly; doesn't always \0-terminate or check for invalid
  pointers [MS-banned] (CWE-120).
    strncpy (linebuf, MAIN_COMMAND_LINE, maximum_length);
data/adasockets-1.12/src/constants.c:131:37:  [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).
  char *result   = (char *) malloc (strlen (name) + 1);

ANALYSIS SUMMARY:

Hits = 7
Lines analyzed = 564 in approximately 0.06 seconds (9769 lines/second)
Physical Source Lines of Code (SLOC) = 360
Hits@level = [0]   7 [1]   2 [2]   5 [3]   0 [4]   0 [5]   0
Hits@level+ = [0+]  14 [1+]   7 [2+]   5 [3+]   0 [4+]   0 [5+]   0
Hits/KSLOC@level+ = [0+] 38.8889 [1+] 19.4444 [2+] 13.8889 [3+]   0 [4+]   0 [5+]   0
Dot directories skipped = 2 (--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.