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/gbase-0.5/gbase.c FINAL RESULTS: data/gbase-0.5/gbase.c:51: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 buffer[33]; data/gbase-0.5/gbase.c:232:65: [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. accumulator = strtol(gtk_entry_get_text(GTK_ENTRY(entry)), (char **)NULL, bases[id]); data/gbase-0.5/gbase.c:234:66: [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. accumulator = strtoul(gtk_entry_get_text(GTK_ENTRY(entry)), (char **)NULL, bases[id]); data/gbase-0.5/gbase.c:269:5: [2] (buffer) sprintf: Does not check for buffer overflows (CWE-120). Use sprintf_s, snprintf, or vsnprintf. Risk is low because the source has a constant maximum length. sprintf(buffer, "%ld", accumulator); data/gbase-0.5/gbase.c:273:7: [2] (buffer) sprintf: Does not check for buffer overflows (CWE-120). Use sprintf_s, snprintf, or vsnprintf. Risk is low because the source has a constant maximum length. sprintf(buffer, "%lu", accumulator); data/gbase-0.5/gbase.c:276:7: [2] (buffer) sprintf: Does not check for buffer overflows (CWE-120). Use sprintf_s, snprintf, or vsnprintf. Risk is low because the source has a constant maximum length. sprintf(buffer, "%lX", accumulator); data/gbase-0.5/gbase.c:279:7: [2] (buffer) sprintf: Does not check for buffer overflows (CWE-120). Use sprintf_s, snprintf, or vsnprintf. Risk is low because the source has a constant maximum length. sprintf(buffer, "%lo", accumulator); data/gbase-0.5/gbase.c:224:6: [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(gtk_entry_get_text(GTK_ENTRY(entry))) == 0) { data/gbase-0.5/gbase.c:384:30: [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(bad_string(argv[i+1], strlen(argv[i+1]), type, 0)) { ANALYSIS SUMMARY: Hits = 9 Lines analyzed = 420 in approximately 0.03 seconds (12532 lines/second) Physical Source Lines of Code (SLOC) = 322 Hits@level = [0] 0 [1] 2 [2] 7 [3] 0 [4] 0 [5] 0 Hits@level+ = [0+] 9 [1+] 9 [2+] 7 [3+] 0 [4+] 0 [5+] 0 Hits/KSLOC@level+ = [0+] 27.9503 [1+] 27.9503 [2+] 21.7391 [3+] 0 [4+] 0 [5+] 0 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.