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/wrapsrv-1.0.0/list.h
Examining data/wrapsrv-1.0.0/wrapsrv.c

FINAL RESULTS:

data/wrapsrv-1.0.0/wrapsrv.c:295:4:  [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(q, se->tname);
data/wrapsrv-1.0.0/wrapsrv.c:324:3:  [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(p, argv[i]);
data/wrapsrv-1.0.0/wrapsrv.c:338:7:  [4] (shell) system:
  This causes a new program to execute and is difficult to use safely
  (CWE-78). try using a library call that implements the same functionality
  if available.
	rc = system(scmd);
data/wrapsrv-1.0.0/wrapsrv.c:100:8:  [3] (random) random:
  This function is not sufficiently random for security-related functions
  such as key and nonce creation (CWE-327). Use a more secure technique for
  acquiring random values.
	rnd = random() % (wsum + 1);
data/wrapsrv-1.0.0/wrapsrv.c:380:2:  [3] (random) srandom:
  This function is not sufficiently random for security-related functions
  such as key and nonce creation (CWE-327). Use a more secure technique for
  acquiring random values.
	srandom(seed);
data/wrapsrv-1.0.0/wrapsrv.c:226:2:  [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 buf[NS_MAXDNAME];
data/wrapsrv-1.0.0/wrapsrv.c:299:9:  [2] (buffer) sprintf:
  Does not check for buffer overflows (CWE-120). Use sprintf_s, snprintf, or
  vsnprintf. Risk is low because the source has a constant maximum length.
			q += sprintf(q, "%hu", se->port);
data/wrapsrv-1.0.0/wrapsrv.c:364:11:  [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 answer[NS_MAXMSG];
data/wrapsrv-1.0.0/wrapsrv.c:274:14:  [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).
	len_tname = strlen(se->tname);
data/wrapsrv-1.0.0/wrapsrv.c:283: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).
	bufsz = strlen(cmd) + 1;
data/wrapsrv-1.0.0/wrapsrv.c:286:12:  [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).
	bufsz += (strlen(se->tname) + 1) * n_host;
data/wrapsrv-1.0.0/wrapsrv.c:317:12:  [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).
		bufsz += strlen(argv[i]);
data/wrapsrv-1.0.0/wrapsrv.c:325:8:  [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).
		p += strlen(argv[i]);

ANALYSIS SUMMARY:

Hits = 13
Lines analyzed = 604 in approximately 0.03 seconds (18580 lines/second)
Physical Source Lines of Code (SLOC) = 468
Hits@level = [0]  11 [1]   5 [2]   3 [3]   2 [4]   3 [5]   0
Hits@level+ = [0+]  24 [1+]  13 [2+]   8 [3+]   5 [4+]   3 [5+]   0
Hits/KSLOC@level+ = [0+] 51.2821 [1+] 27.7778 [2+] 17.094 [3+] 10.6838 [4+] 6.41026 [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.