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/stdsyslog-0.03.3/flexarr.h
Examining data/stdsyslog-0.03.3/stdsyslog.c

FINAL RESULTS:

data/stdsyslog-0.03.3/stdsyslog.c:396:3:  [4] (shell) execvp:
  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.
		execvp(argv[0], argv);
data/stdsyslog-0.03.3/stdsyslog.c:233:15:  [3] (buffer) getopt:
  Some older implementations do not protect against internal buffer overflows
  (CWE-120, CWE-20). Check implementation on installation, or limit the size
  of all string inputs.
	while ((ch = getopt(argc, argv, "d:f:hlp:V-:")) != -1) {
data/stdsyslog-0.03.3/stdsyslog.c:204: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 readbuf[2048];
data/stdsyslog-0.03.3/stdsyslog.c:353:21:  [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).
		const int pidfd = open(pidfile, O_CREAT | O_EXCL | O_RDWR,
data/stdsyslog-0.03.3/stdsyslog.c:546:2:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination (CWE-120).
  Make sure destination can always hold the source data.
	memcpy(fd->rbuf + cpos, rdbuf, sz);
data/stdsyslog-0.03.3/stdsyslog.c:636:2:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination (CWE-120).
  Make sure destination can always hold the source data.
	memcpy(spec, &sp, sizeof(*spec));
data/stdsyslog-0.03.3/stdsyslog.c:454:9:  [1] (buffer) read:
  Check buffer boundaries if used in a loop including recursive loops
  (CWE-120, CWE-20).
				    read(fd, readbuf, sizeof(readbuf));

ANALYSIS SUMMARY:

Hits = 7
Lines analyzed = 705 in approximately 0.03 seconds (25776 lines/second)
Physical Source Lines of Code (SLOC) = 554
Hits@level = [0]   4 [1]   1 [2]   4 [3]   1 [4]   1 [5]   0
Hits@level+ = [0+]  11 [1+]   7 [2+]   6 [3+]   2 [4+]   1 [5+]   0
Hits/KSLOC@level+ = [0+] 19.8556 [1+] 12.6354 [2+] 10.8303 [3+] 3.61011 [4+] 1.80505 [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.