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/yder-1.4.12/examples/log_callback.c Examining data/yder-1.4.12/examples/log_combined.c Examining data/yder-1.4.12/examples/log_console.c Examining data/yder-1.4.12/examples/log_file.c Examining data/yder-1.4.12/examples/log_journald.c Examining data/yder-1.4.12/examples/log_syslog.c Examining data/yder-1.4.12/include/yder.h Examining data/yder-1.4.12/src/yder.c Examining data/yder-1.4.12/test/yder_test.c FINAL RESULTS: data/yder-1.4.12/src/yder.c:370:13: [4] (format) vsnprintf: If format strings can be influenced by an attacker, they can be exploited, and note that sprintf variations do not always \0-terminate (CWE-134). Use a constant for the format specification. out_len = vsnprintf(NULL, 0, message, args); data/yder-1.4.12/src/yder.c:373:5: [4] (format) vsnprintf: If format strings can be influenced by an attacker, they can be exploited, and note that sprintf variations do not always \0-terminate (CWE-134). Use a constant for the format specification. vsnprintf(out, (out_len + 1), message, args_cpy); data/yder-1.4.12/test/yder_test.c:17: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(app_name, log_app_name); data/yder-1.4.12/test/yder_test.c:18: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(cls, log_message); data/yder-1.4.12/examples/log_callback.c:21: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 *level_name, date_stamp[20]; data/yder-1.4.12/src/yder.c:260:25: [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 ((cur_log_file = fopen(cur_log_file_path, "a+")) == NULL) { data/yder-1.4.12/test/yder_test.c:12:1: [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 message[1024]; data/yder-1.4.12/test/yder_test.c:13:1: [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 app_name[128]; ANALYSIS SUMMARY: Hits = 8 Lines analyzed = 1129 in approximately 0.07 seconds (17077 lines/second) Physical Source Lines of Code (SLOC) = 755 Hits@level = [0] 8 [1] 0 [2] 4 [3] 0 [4] 4 [5] 0 Hits@level+ = [0+] 16 [1+] 8 [2+] 8 [3+] 4 [4+] 4 [5+] 0 Hits/KSLOC@level+ = [0+] 21.1921 [1+] 10.596 [2+] 10.596 [3+] 5.29801 [4+] 5.29801 [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.