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/asterisk-espeak-5.0~1/app_espeak.c

FINAL RESULTS:

data/asterisk-espeak-5.0~1/app_espeak.c:171:12:  [2] (misc) fopen:
  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 ((fl = fopen(fname, "r")) == NULL) {
data/asterisk-espeak-5.0~1/app_espeak.c:222:12:  [2] (misc) fopen:
  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 ((fl = fopen(fname, "w+")) != NULL) {
data/asterisk-espeak-5.0~1/app_espeak.c:250: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 cachefile[MAXLEN];
data/asterisk-espeak-5.0~1/app_espeak.c:251: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 raw_name[17] = "/tmp/espk_XXXXXX";
data/asterisk-espeak-5.0~1/app_espeak.c:252: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 slin_name[23];
data/asterisk-espeak-5.0~1/app_espeak.c:289: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 MD5_name[33];
data/asterisk-espeak-5.0~1/app_espeak.c:341:16:  [2] (tmpfile) mkstemp:
  Potential for temporary file vulnerability in some circumstances. Some
  older Unix-like systems create temp files with permission to write by all
  by default, so be sure to set the umask to override this. Also, some older
  Unix systems might fail to use O_EXCL when opening the file, so make sure
  that O_EXCL is used by the library (CWE-377).
	if ((raw_fd = mkstemp(raw_name)) == -1) {
data/asterisk-espeak-5.0~1/app_espeak.c:291:7:  [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).
		if (strlen(cachedir) + strlen(MD5_name) + 6 <= MAXLEN) {
data/asterisk-espeak-5.0~1/app_espeak.c:291:26:  [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).
		if (strlen(cachedir) + strlen(MD5_name) + 6 <= MAXLEN) {
data/asterisk-espeak-5.0~1/app_espeak.c:350:39:  [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).
	espk_error = espeak_Synth(args.text, strlen(args.text), 0, POS_CHARACTER,
data/asterisk-espeak-5.0~1/app_espeak.c:351: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).
			(int) strlen(args.text), espeakCHARS_AUTO, NULL, fl);

ANALYSIS SUMMARY:

Hits = 11
Lines analyzed = 422 in approximately 0.03 seconds (14451 lines/second)
Physical Source Lines of Code (SLOC) = 349
Hits@level = [0]   3 [1]   4 [2]   7 [3]   0 [4]   0 [5]   0
Hits@level+ = [0+]  14 [1+]  11 [2+]   7 [3+]   0 [4+]   0 [5+]   0
Hits/KSLOC@level+ = [0+] 40.1146 [1+] 31.5186 [2+] 20.0573 [3+]   0 [4+]   0 [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.