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/gimplensfun-0.2.4/src/LUT.hpp Examining data/gimplensfun-0.2.4/src/gimplensfun.cpp FINAL RESULTS: data/gimplensfun-0.2.4/src/gimplensfun.cpp:1188:5: [4] (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). strcpy( sLensfunParameterStorage.Camera, sLensfunParameters.Camera.c_str() ); data/gimplensfun-0.2.4/src/gimplensfun.cpp:1189:5: [4] (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). strcpy( sLensfunParameterStorage.CamMaker, sLensfunParameters.CamMaker.c_str() ); data/gimplensfun-0.2.4/src/gimplensfun.cpp:1190:5: [4] (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). strcpy( sLensfunParameterStorage.Lens, sLensfunParameters.Lens.c_str() ); data/gimplensfun-0.2.4/src/LUT.hpp:127:15: [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(this->data,rhs.data,rhs.size*sizeof(T)); data/gimplensfun-0.2.4/src/gimplensfun.cpp:146: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 Camera[255]; data/gimplensfun-0.2.4/src/gimplensfun.cpp:147: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 CamMaker[255]; data/gimplensfun-0.2.4/src/gimplensfun.cpp:148: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 Lens[255]; data/gimplensfun-0.2.4/src/gimplensfun.cpp:1052:43: [2] (misc) open: 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). Exiv2image = Exiv2::ImageFactory::open(string(filename)); data/gimplensfun-0.2.4/src/gimplensfun.cpp:1169:9: [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(sLensfunParameterStorage.Camera)>0) data/gimplensfun-0.2.4/src/gimplensfun.cpp:1171:9: [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(sLensfunParameterStorage.CamMaker)>0) data/gimplensfun-0.2.4/src/gimplensfun.cpp:1173:9: [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(sLensfunParameterStorage.Lens)>0) ANALYSIS SUMMARY: Hits = 11 Lines analyzed = 1451 in approximately 0.06 seconds (24442 lines/second) Physical Source Lines of Code (SLOC) = 1032 Hits@level = [0] 0 [1] 3 [2] 5 [3] 0 [4] 3 [5] 0 Hits@level+ = [0+] 11 [1+] 11 [2+] 8 [3+] 3 [4+] 3 [5+] 0 Hits/KSLOC@level+ = [0+] 10.6589 [1+] 10.6589 [2+] 7.75194 [3+] 2.90698 [4+] 2.90698 [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.