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/pd-syslog-0.1/syslog.c FINAL RESULTS: data/pd-syslog-0.1/syslog.c:93:5: [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(result+pos, buf); data/pd-syslog-0.1/syslog.c:105:7: [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(result+pos, ap->a_w.w_symbol->s_name); data/pd-syslog-0.1/syslog.c:110:7: [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(result+pos, buffer); data/pd-syslog-0.1/syslog.c:75:5: [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 buffer[MAXPDSTRING]; data/pd-syslog-0.1/syslog.c:108:7: [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 buffer[MAXPDSTRING]; data/pd-syslog-0.1/syslog.c:68:16: [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(s)length+=strlen(s->s_name); data/pd-syslog-0.1/syslog.c:78:11: [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=strlen(ap->a_w.w_symbol->s_name); data/pd-syslog-0.1/syslog.c:81:11: [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=strlen(buffer); data/pd-syslog-0.1/syslog.c:94: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). pos+=strlen(buf); data/pd-syslog-0.1/syslog.c:96:7: [1] (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 character. strcpy(result+pos, " "); data/pd-syslog-0.1/syslog.c:106:13: [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). pos+= strlen(ap->a_w.w_symbol->s_name); data/pd-syslog-0.1/syslog.c:111: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). pos += strlen(buffer); data/pd-syslog-0.1/syslog.c:115:7: [1] (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 character. strcpy(result+pos, " "); ANALYSIS SUMMARY: Hits = 13 Lines analyzed = 155 in approximately 0.01 seconds (11453 lines/second) Physical Source Lines of Code (SLOC) = 92 Hits@level = [0] 1 [1] 8 [2] 2 [3] 0 [4] 3 [5] 0 Hits@level+ = [0+] 14 [1+] 13 [2+] 5 [3+] 3 [4+] 3 [5+] 0 Hits/KSLOC@level+ = [0+] 152.174 [1+] 141.304 [2+] 54.3478 [3+] 32.6087 [4+] 32.6087 [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.