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/pidgin-privacy-please-0.7.1/src/autoreply.c Examining data/pidgin-privacy-please-0.7.1/src/autoreply.h Examining data/pidgin-privacy-please-0.7.1/src/blocklist.h Examining data/pidgin-privacy-please-0.7.1/src/blocklist.c Examining data/pidgin-privacy-please-0.7.1/src/botcheck.h Examining data/pidgin-privacy-please-0.7.1/src/botcheck.c Examining data/pidgin-privacy-please-0.7.1/src/pp-prefs.h Examining data/pidgin-privacy-please-0.7.1/src/pp-prefs.c Examining data/pidgin-privacy-please-0.7.1/src/pidgin-pp.c FINAL RESULTS: data/pidgin-privacy-please-0.7.1/src/pp-prefs.c:43:2: [4] (buffer) sprintf: Does not check for buffer overflows (CWE-120). Use sprintf_s, snprintf, or vsnprintf. sprintf(path, "/plugins/core/pidgin_pp/%s", key); \ data/pidgin-privacy-please-0.7.1/src/pp-prefs.c:51:2: [4] (buffer) sprintf: Does not check for buffer overflows (CWE-120). Use sprintf_s, snprintf, or vsnprintf. sprintf(path, "/plugins/core/pidgin_pp/%s", key); \ data/pidgin-privacy-please-0.7.1/src/pp-prefs.c:42: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 path[128]; \ data/pidgin-privacy-please-0.7.1/src/pp-prefs.c:50: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 path[128]; \ data/pidgin-privacy-please-0.7.1/src/autoreply.c:145:2: [1] (buffer) strncpy: Easily used incorrectly; doesn't always \0-terminate or check for invalid pointers [MS-banned] (CWE-120). strncpy(node->sender, sender, MAX_NAME_LENGTH); data/pidgin-privacy-please-0.7.1/src/botcheck.c:124:2: [1] (buffer) strncpy: Easily used incorrectly; doesn't always \0-terminate or check for invalid pointers [MS-banned] (CWE-120). strncpy(node->sender, sender, MAX_NAME_LENGTH); ANALYSIS SUMMARY: Hits = 6 Lines analyzed = 1527 in approximately 0.05 seconds (31454 lines/second) Physical Source Lines of Code (SLOC) = 1065 Hits@level = [0] 0 [1] 2 [2] 2 [3] 0 [4] 2 [5] 0 Hits@level+ = [0+] 6 [1+] 6 [2+] 4 [3+] 2 [4+] 2 [5+] 0 Hits/KSLOC@level+ = [0+] 5.6338 [1+] 5.6338 [2+] 3.75587 [3+] 1.87793 [4+] 1.87793 [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.