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/gdigi-0.4.0/gdigi_xml.h Examining data/gdigi-0.4.0/gtkknob.h Examining data/gdigi-0.4.0/preset.h Examining data/gdigi-0.4.0/gui.h Examining data/gdigi-0.4.0/preset_xml.c Examining data/gdigi-0.4.0/knob.h Examining data/gdigi-0.4.0/effects.h Examining data/gdigi-0.4.0/gui.c Examining data/gdigi-0.4.0/preset.c Examining data/gdigi-0.4.0/gtkknob.c Examining data/gdigi-0.4.0/gdigi.c Examining data/gdigi-0.4.0/effects.c Examining data/gdigi-0.4.0/gdigi.h FINAL RESULTS: data/gdigi-0.4.0/gdigi.c:92:9: [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(buf, 1024, fmt, ap); data/gdigi-0.4.0/gdigi.c:87: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 buf[1024]; data/gdigi-0.4.0/gdigi.c:586:18: [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. unsigned char buf[256]; data/gdigi-0.4.0/gtkknob.c:882:5: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination (CWE-120). Make sure destination can always hold the source data. memcpy (data, knob_png + *offset, length); data/gdigi-0.4.0/preset.c:135:29: [2] (integer) atoi: Unless checked, the resulting number can exceed the expected range (CWE-190). If source untrusted, check both minimum and maximum, even if the input had no minus sign (large numbers can roll over into negative number; consider saving to an unsigned value if that is intended). param->id = atoi(value); data/gdigi-0.4.0/preset.c:138:35: [2] (integer) atoi: Unless checked, the resulting number can exceed the expected range (CWE-190). If source untrusted, check both minimum and maximum, even if the input had no minus sign (large numbers can roll over into negative number; consider saving to an unsigned value if that is intended). param->position = atoi(value); data/gdigi-0.4.0/preset.c:141:32: [2] (integer) atoi: Unless checked, the resulting number can exceed the expected range (CWE-190). If source untrusted, check both minimum and maximum, even if the input had no minus sign (large numbers can roll over into negative number; consider saving to an unsigned value if that is intended). param->value = atoi(value); data/gdigi-0.4.0/gdigi.c:1109:18: [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). x += strlen(str_array[n]); data/gdigi-0.4.0/preset.c:242:32: [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 (XML_Parse(p, contents, strlen(contents), XML_TRUE) != XML_STATUS_OK) { data/gdigi-0.4.0/preset.c:308:56: [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). modified = (unsigned char)data->str[11+strlen(name)]; ANALYSIS SUMMARY: Hits = 10 Lines analyzed = 16199 in approximately 0.85 seconds (19043 lines/second) Physical Source Lines of Code (SLOC) = 13659 Hits@level = [0] 19 [1] 3 [2] 6 [3] 0 [4] 1 [5] 0 Hits@level+ = [0+] 29 [1+] 10 [2+] 7 [3+] 1 [4+] 1 [5+] 0 Hits/KSLOC@level+ = [0+] 2.12314 [1+] 0.732118 [2+] 0.512483 [3+] 0.0732118 [4+] 0.0732118 [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.