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/ocaml-sqlite3-5.0.2/src/sqlite3_stubs.c FINAL RESULTS: data/ocaml-sqlite3-5.0.2/src/sqlite3_stubs.c:238:3: [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, sizeof buf, fmt, args); data/ocaml-sqlite3-5.0.2/src/sqlite3_stubs.c:252:3: [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, sizeof buf, fmt, args); data/ocaml-sqlite3-5.0.2/src/sqlite3_stubs.c:277:3: [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, sizeof buf, fmt, args); data/ocaml-sqlite3-5.0.2/src/sqlite3_stubs.c:234: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 buf[1024]; data/ocaml-sqlite3-5.0.2/src/sqlite3_stubs.c:246: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 buf[1024]; data/ocaml-sqlite3-5.0.2/src/sqlite3_stubs.c:273: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 buf[1024]; data/ocaml-sqlite3-5.0.2/src/sqlite3_stubs.c:491: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(vfs, String_val(v_vfs), vfs_len); data/ocaml-sqlite3-5.0.2/src/sqlite3_stubs.c:507:3: [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(file, String_val(v_file), file_len); data/ocaml-sqlite3-5.0.2/src/sqlite3_stubs.c:520: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 msg[1024]; data/ocaml-sqlite3-5.0.2/src/sqlite3_stubs.c:527:7: [2] (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 string. strcpy(msg, "<unknown_error>"); data/ocaml-sqlite3-5.0.2/src/sqlite3_stubs.c:664:3: [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(sql, String_val(v_sql), len); data/ocaml-sqlite3-5.0.2/src/sqlite3_stubs.c:718:3: [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(sql, String_val(v_sql), len); data/ocaml-sqlite3-5.0.2/src/sqlite3_stubs.c:779:3: [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(sql, String_val(v_sql), len); data/ocaml-sqlite3-5.0.2/src/sqlite3_stubs.c:839:3: [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(sql, String_val(v_sql), len); data/ocaml-sqlite3-5.0.2/src/sqlite3_stubs.c:893:3: [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(stmtw->sql, sql, sql_len); data/ocaml-sqlite3-5.0.2/src/sqlite3_stubs.c:1672:3: [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(dst_name, String_val(v_dst_name), dst_len); data/ocaml-sqlite3-5.0.2/src/sqlite3_stubs.c:1676:3: [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(src_name, String_val(v_src_name), src_len); ANALYSIS SUMMARY: Hits = 17 Lines analyzed = 1736 in approximately 0.05 seconds (33383 lines/second) Physical Source Lines of Code (SLOC) = 1398 Hits@level = [0] 1 [1] 0 [2] 14 [3] 0 [4] 3 [5] 0 Hits@level+ = [0+] 18 [1+] 17 [2+] 17 [3+] 3 [4+] 3 [5+] 0 Hits/KSLOC@level+ = [0+] 12.8755 [1+] 12.1602 [2+] 12.1602 [3+] 2.14592 [4+] 2.14592 [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.