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/r-cran-dotcall64-1.0-0/inst/include/dotCall64.h Examining data/r-cran-dotcall64-1.0-0/src/dotCall64helpers.c Examining data/r-cran-dotcall64-1.0-0/src/init.c Examining data/r-cran-dotcall64-1.0-0/src/testfunctions_c.c Examining data/r-cran-dotcall64-1.0-0/src/dotCall64.c FINAL RESULTS: data/r-cran-dotcall64-1.0-0/src/dotCall64.c:112:2: [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(symName, p); data/r-cran-dotcall64-1.0-0/src/dotCall64.c:565: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(packageName, p); data/r-cran-dotcall64-1.0-0/src/dotCall64.c:87: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 symName[MaxSymbolBytes]; data/r-cran-dotcall64-1.0-0/src/dotCall64.c:89: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 packageName[PATH_MAX]; data/r-cran-dotcall64-1.0-0/src/dotCall64.c:63: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). for(int i=0; i<strlen(p); i++) { data/r-cran-dotcall64-1.0-0/src/dotCall64.c:110:5: [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(p) > MaxSymbolBytes - 1) data/r-cran-dotcall64-1.0-0/src/dotCall64.c:138:19: [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). int symlength = strlen(symName); data/r-cran-dotcall64-1.0-0/src/dotCall64.c:552:2: [1] (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 character. strcpy(packageName, ""); data/r-cran-dotcall64-1.0-0/src/dotCall64.c:563:8: [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(p) > PATH_MAX - 1) ANALYSIS SUMMARY: Hits = 9 Lines analyzed = 1461 in approximately 0.20 seconds (7388 lines/second) Physical Source Lines of Code (SLOC) = 1148 Hits@level = [0] 0 [1] 5 [2] 2 [3] 0 [4] 2 [5] 0 Hits@level+ = [0+] 9 [1+] 9 [2+] 4 [3+] 2 [4+] 2 [5+] 0 Hits/KSLOC@level+ = [0+] 7.83972 [1+] 7.83972 [2+] 3.48432 [3+] 1.74216 [4+] 1.74216 [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.