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/mialmpick-0.2.15/src/callbacks.h Examining data/mialmpick-0.2.15/src/load_vista.c Examining data/mialmpick-0.2.15/src/trackball.c Examining data/mialmpick-0.2.15/src/landmarkinput.c Examining data/mialmpick-0.2.15/src/globals.h Examining data/mialmpick-0.2.15/src/landmarktable.h Examining data/mialmpick-0.2.15/src/landmarkinput.h Examining data/mialmpick-0.2.15/src/landmarktable.c Examining data/mialmpick-0.2.15/src/callbacks.c Examining data/mialmpick-0.2.15/src/png_save.h Examining data/mialmpick-0.2.15/src/gldrawable.c Examining data/mialmpick-0.2.15/src/glview.h Examining data/mialmpick-0.2.15/src/main.c Examining data/mialmpick-0.2.15/src/png_save.c Examining data/mialmpick-0.2.15/src/globals.c Examining data/mialmpick-0.2.15/src/image3d.c Examining data/mialmpick-0.2.15/src/gllandmark.h Examining data/mialmpick-0.2.15/src/glview.c Examining data/mialmpick-0.2.15/src/image3d.h Examining data/mialmpick-0.2.15/src/trackball.h Examining data/mialmpick-0.2.15/src/glvolume.c Examining data/mialmpick-0.2.15/src/gldrawable.h Examining data/mialmpick-0.2.15/src/gllandmark.c Examining data/mialmpick-0.2.15/src/glvolume.h FINAL RESULTS: data/mialmpick-0.2.15/src/callbacks.c:334: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 name[1024]; data/mialmpick-0.2.15/src/callbacks.c:579:2: [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(old_color, color_ptr, 4 * sizeof(gdouble)); data/mialmpick-0.2.15/src/callbacks.c:588:9: [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(color_ptr, old_color, 4 * sizeof(gdouble)); data/mialmpick-0.2.15/src/glvolume.c:423: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 info[3000]; data/mialmpick-0.2.15/src/image3d.c:211:4: [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(trgt_data, src_data, src->nx * sizeof(gfloat)); data/mialmpick-0.2.15/src/load_vista.c:36:14: [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 ((file = fopen(file_name, "r")) == 0) { data/mialmpick-0.2.15/src/png_save.c:35:9: [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). outf = fopen(name,"wb"); data/mialmpick-0.2.15/src/landmarktable.c:601:17: [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 (picfile && strlen(picfile)) { ANALYSIS SUMMARY: Hits = 8 Lines analyzed = 7287 in approximately 0.15 seconds (48050 lines/second) Physical Source Lines of Code (SLOC) = 5064 Hits@level = [0] 6 [1] 1 [2] 7 [3] 0 [4] 0 [5] 0 Hits@level+ = [0+] 14 [1+] 8 [2+] 7 [3+] 0 [4+] 0 [5+] 0 Hits/KSLOC@level+ = [0+] 2.76461 [1+] 1.57978 [2+] 1.38231 [3+] 0 [4+] 0 [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.