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/vmemcache-0.8.1/benchmarks/bench_micro.c
Examining data/vmemcache-0.8.1/benchmarks/benchmark_time.c
Examining data/vmemcache-0.8.1/benchmarks/benchmark_time.h
Examining data/vmemcache-0.8.1/benchmarks/rand.c
Examining data/vmemcache-0.8.1/benchmarks/rand.h
Examining data/vmemcache-0.8.1/benchmarks/bench_simul.c
Examining data/vmemcache-0.8.1/src/common.h
Examining data/vmemcache-0.8.1/src/critnib.c
Examining data/vmemcache-0.8.1/src/critnib.h
Examining data/vmemcache-0.8.1/src/fast-hash.c
Examining data/vmemcache-0.8.1/src/fast-hash.h
Examining data/vmemcache-0.8.1/src/file.c
Examining data/vmemcache-0.8.1/src/file_posix.c
Examining data/vmemcache-0.8.1/src/libvmemcache.c
Examining data/vmemcache-0.8.1/src/libvmemcache.h
Examining data/vmemcache-0.8.1/src/mmap.c
Examining data/vmemcache-0.8.1/src/mmap.h
Examining data/vmemcache-0.8.1/src/mmap_posix.c
Examining data/vmemcache-0.8.1/src/os.h
Examining data/vmemcache-0.8.1/src/os_posix.c
Examining data/vmemcache-0.8.1/src/os_thread_posix.c
Examining data/vmemcache-0.8.1/src/out.h
Examining data/vmemcache-0.8.1/src/ringbuf.c
Examining data/vmemcache-0.8.1/src/ringbuf.h
Examining data/vmemcache-0.8.1/src/sys/queue.h
Examining data/vmemcache-0.8.1/src/sys_util.h
Examining data/vmemcache-0.8.1/src/util.c
Examining data/vmemcache-0.8.1/src/util.h
Examining data/vmemcache-0.8.1/src/util_posix.c
Examining data/vmemcache-0.8.1/src/valgrind_internal.h
Examining data/vmemcache-0.8.1/src/vmemcache.c
Examining data/vmemcache-0.8.1/src/vmemcache.h
Examining data/vmemcache-0.8.1/src/vmemcache_heap.c
Examining data/vmemcache-0.8.1/src/vmemcache_heap.h
Examining data/vmemcache-0.8.1/src/vmemcache_index.c
Examining data/vmemcache-0.8.1/src/vmemcache_index.h
Examining data/vmemcache-0.8.1/src/vmemcache_repl.c
Examining data/vmemcache-0.8.1/src/vmemcache_repl.h
Examining data/vmemcache-0.8.1/src/file.h
Examining data/vmemcache-0.8.1/src/os_thread.h
Examining data/vmemcache-0.8.1/src/out.c
Examining data/vmemcache-0.8.1/tests/example.c
Examining data/vmemcache-0.8.1/tests/test_helpers.h
Examining data/vmemcache-0.8.1/tests/twolevel.c
Examining data/vmemcache-0.8.1/tests/vmemcache_test_heap_usage.c
Examining data/vmemcache-0.8.1/tests/vmemcache_test_mt.c
Examining data/vmemcache-0.8.1/tests/vmemcache_test_basic.c
Examining data/vmemcache-0.8.1/tests/vmemcache_test_utilization.c
FINAL RESULTS:
data/vmemcache-0.8.1/src/os_posix.c:132:9: [5] (race) chmod:
This accepts filename arguments; if an attacker can move those files, a
race condition results. (CWE-362). Use fchmod( ) instead.
return chmod(pathname, mode);
data/vmemcache-0.8.1/src/util_posix.c:109:7: [5] (race) readlink:
This accepts filename arguments; if an attacker can move those files or
change the link content, a race condition results. Also, it does not
terminate with ASCII NUL. (CWE-362, CWE-20). Reconsider approach.
cc = readlink("/proc/self/exe", path, pathlen);
data/vmemcache-0.8.1/tests/vmemcache_test_mt.c:362:15: [5] (buffer) gets:
Does not check for buffer overflows (CWE-120, CWE-20). Use fgets() instead.
stat_t puts, gets, misses;
data/vmemcache-0.8.1/tests/vmemcache_test_mt.c:364:19: [5] (buffer) gets:
Does not check for buffer overflows (CWE-120, CWE-20). Use fgets() instead.
get_stat(cache, &gets, VMEMCACHE_STAT_GET);
data/vmemcache-0.8.1/tests/vmemcache_test_mt.c:373:6: [5] (buffer) gets:
Does not check for buffer overflows (CWE-120, CWE-20). Use fgets() instead.
if (gets != nops)
data/vmemcache-0.8.1/tests/vmemcache_test_mt.c:375:5: [5] (buffer) gets:
Does not check for buffer overflows (CWE-120, CWE-20). Use fgets() instead.
gets, nops);
data/vmemcache-0.8.1/benchmarks/bench_micro.c:284:3: [4] (format) fprintf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
fprintf(stderr, USAGE_STRING, argv[0], n_threads, ops_count,
data/vmemcache-0.8.1/benchmarks/bench_simul.c:530:3: [4] (format) fprintf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
fprintf(f, i ? ";%llu" : "%llu", t[i * (n - 1) /
data/vmemcache-0.8.1/src/file_posix.c:45:9: [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).
(void) strcpy(fullname, dir);
data/vmemcache-0.8.1/src/file_posix.c:46:9: [4] (buffer) strcat:
Does not check for buffer overflows when concatenating to destination
[MS-banned] (CWE-120). Consider using strcat_s, strncat, strlcat, or
snprintf (warning: strncat is easily misused).
(void) strcat(fullname, templ);
data/vmemcache-0.8.1/src/mmap_posix.c:63:7: [4] (buffer) sscanf:
The scanf() family's %s operation, without a limit specification, permits
buffer overflows (CWE-120, CWE-20). Specify a limit to %s, or use a
different input function. If the scanf format is influenceable by an
attacker, it's exploitable.
if (sscanf(line, sscanf_os, &lo, &hi) == 2) {
data/vmemcache-0.8.1/src/os_posix.c:104:9: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
return access(pathname, mode);
data/vmemcache-0.8.1/src/os_posix.c:302:9: [4] (shell) execv:
This causes a new program to execute and is difficult to use safely
(CWE-78). try using a library call that implements the same functionality
if available.
return execv(path, argv);
data/vmemcache-0.8.1/src/out.c:290:35: [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.
static Vsnprintf_func Vsnprintf = vsnprintf;
data/vmemcache-0.8.1/src/out.c:313:41: [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 = (vsnprintf_func == NULL) ? vsnprintf : vsnprintf_func;
data/vmemcache-0.8.1/src/util.c:89: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(lib_name, lib);
data/vmemcache-0.8.1/src/util.c:90:2: [4] (buffer) strcat:
Does not check for buffer overflows when concatenating to destination
[MS-banned] (CWE-120). Consider using strcat_s, strncat, strlcat, or
snprintf (warning: strncat is easily misused).
strcat(lib_name, suffix);
data/vmemcache-0.8.1/src/util.c:91: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(func_name, func);
data/vmemcache-0.8.1/src/util.c:92:2: [4] (buffer) strcat:
Does not check for buffer overflows when concatenating to destination
[MS-banned] (CWE-120). Consider using strcat_s, strncat, strlcat, or
snprintf (warning: strncat is easily misused).
strcat(func_name, suffix);
data/vmemcache-0.8.1/src/util.c:323: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(result, s1);
data/vmemcache-0.8.1/src/util.c:324:2: [4] (buffer) strcat:
Does not check for buffer overflows when concatenating to destination
[MS-banned] (CWE-120). Consider using strcat_s, strncat, strlcat, or
snprintf (warning: strncat is easily misused).
strcat(result, s2);
data/vmemcache-0.8.1/src/util.c:432:4: [4] (format) printf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
printf((*s >= ' ' && *s < 0x7f) ? "%c" : "\\x%02x", *s);
data/vmemcache-0.8.1/tests/test_helpers.h:20:2: [4] (format) fprintf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
fprintf(stderr, "ERROR: " __VA_ARGS__);\
data/vmemcache-0.8.1/tests/test_helpers.h:27:2: [4] (format) fprintf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
fprintf(stderr, __VA_ARGS__);\
data/vmemcache-0.8.1/tests/twolevel.c:10:23: [4] (format) fprintf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
#define ERR(...) do { fprintf(stderr, __VA_ARGS__); exit(1); } while (0)
data/vmemcache-0.8.1/tests/vmemcache_test_basic.c:325: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(nonexistent, dir);
data/vmemcache-0.8.1/tests/vmemcache_test_utilization.c:70:3: [4] (format) printf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
printf(usage_str, prog);
data/vmemcache-0.8.1/tests/vmemcache_test_utilization.c:85:3: [4] (format) printf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
printf(usage_str, prog);
data/vmemcache-0.8.1/tests/vmemcache_test_utilization.c:98:2: [4] (format) printf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
printf(usage_str, prog);
data/vmemcache-0.8.1/tests/vmemcache_test_utilization.c:127:4: [4] (format) printf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
printf(usage_str, argv[0]);
data/vmemcache-0.8.1/tests/vmemcache_test_utilization.c:156:4: [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(p.dir, optarg);
data/vmemcache-0.8.1/benchmarks/bench_micro.c:355:2: [3] (random) srand:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
srand(seed);
data/vmemcache-0.8.1/src/file.c:149:16: [3] (buffer) realpath:
This function does not protect against buffer overflows, and some
implementations can overflow internally (CWE-120/CWE-785!). Ensure that the
destination buffer is at least of size MAXPATHLEN, andto protect against
implementation problems, the input argument should also be checked to
ensure it is no larger than MAXPATHLEN.
char *rpath = realpath(spath, npath);
data/vmemcache-0.8.1/src/os_posix.c:276:9: [3] (buffer) getenv:
Environment variables are untrustable input if they can be set by an
attacker. They can have any content and length, and the same variable can
be set more than once (CWE-807, CWE-20). Check environment variables
carefully before using them.
return getenv(name);
data/vmemcache-0.8.1/src/util.c:303:25: [3] (buffer) getenv:
Environment variables are untrustable input if they can be set by an
attacker. They can have any content and length, and the same variable can
be set more than once (CWE-807, CWE-20). Check environment variables
carefully before using them.
char *pmreorder_env = getenv("PMREORDER_EMIT_LOG");
data/vmemcache-0.8.1/src/util.c:444:18: [3] (buffer) getenv:
Environment variables are untrustable input if they can be set by an
attacker. They can have any content and length, and the same variable can
be set more than once (CWE-807, CWE-20). Check environment variables
carefully before using them.
const char *q = getenv(var);
data/vmemcache-0.8.1/src/util_posix.c:34:9: [3] (buffer) realpath:
This function does not protect against buffer overflows, and some
implementations can overflow internally (CWE-120/CWE-785!). Ensure that the
destination buffer is at least of size MAXPATHLEN, andto protect against
implementation problems, the input argument should also be checked to
ensure it is no larger than MAXPATHLEN.
return realpath(path, NULL);
data/vmemcache-0.8.1/tests/vmemcache_test_basic.c:659:2: [3] (random) srand:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
srand(seed);
data/vmemcache-0.8.1/tests/vmemcache_test_basic.c:854:2: [3] (random) srand:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
srand(seed);
data/vmemcache-0.8.1/tests/vmemcache_test_basic.c:1035:2: [3] (random) srand:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
srand(seed);
data/vmemcache-0.8.1/tests/vmemcache_test_mt.c:560:2: [3] (random) srand:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
srand(seed);
data/vmemcache-0.8.1/tests/vmemcache_test_utilization.c:124:16: [3] (buffer) getopt:
Some older implementations do not protect against internal buffer overflows
(CWE-120, CWE-20). Check implementation on installation, or limit the size
of all string inputs.
while ((opt = getopt(argc, argv, optstr)) != -1) {
data/vmemcache-0.8.1/tests/vmemcache_test_utilization.c:178:2: [3] (random) srand:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
srand(p.seed);
data/vmemcache-0.8.1/benchmarks/bench_micro.c:110: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 vbuf[MAX_VALUE_SIZE]; /* user-provided buffer */
data/vmemcache-0.8.1/benchmarks/bench_simul.c:139:14: [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.
static const char *stat_str[VMEMCACHE_STATS_NUM] = {
data/vmemcache-0.8.1/benchmarks/bench_simul.c:301: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(key, &rest, len);
data/vmemcache-0.8.1/benchmarks/bench_simul.c:362: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 key[key_size + 1];
data/vmemcache-0.8.1/benchmarks/bench_simul.c:541:7: [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).
f = fopen(latency_file, "w");
data/vmemcache-0.8.1/benchmarks/bench_simul.c:598: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 junk[256];
data/vmemcache-0.8.1/src/file.c:50: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 spath[PATH_MAX];
data/vmemcache-0.8.1/src/file.c:64: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 sizebuf[MAX_SIZE_LENGTH + 1];
data/vmemcache-0.8.1/src/file.c:142: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 spath[PATH_MAX];
data/vmemcache-0.8.1/src/file.c:148: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 npath[PATH_MAX];
data/vmemcache-0.8.1/src/file.c:398: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(ADDR_SUM(addr, offset), buffer, size);
data/vmemcache-0.8.1/src/file.c:451: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(buffer, ADDR_SUM(addr, offset), size);
data/vmemcache-0.8.1/src/file.h:31: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 filename[NAME_MAX + 1];
data/vmemcache-0.8.1/src/file_posix.c:90:11: [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).
int fd = open(dir, O_TMPFILE | O_RDWR | flags, S_IRUSR | S_IWUSR);
data/vmemcache-0.8.1/src/file_posix.c:196: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 spath[PATH_MAX];
data/vmemcache-0.8.1/src/file_posix.c:210: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 sizebuf[MAX_SIZE_LENGTH + 1];
data/vmemcache-0.8.1/src/file_posix.c:279: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 dax_region_path[PATH_MAX];
data/vmemcache-0.8.1/src/file_posix.c:280: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 reg_id[DAX_REGION_ID_LEN];
data/vmemcache-0.8.1/src/mmap_posix.c:51: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 line[PROCMAXLEN]; /* for fgets() */
data/vmemcache-0.8.1/src/os_posix.c:46:10: [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).
return open(pathname, flags, (mode_t)mode);
data/vmemcache-0.8.1/src/os_posix.c:48:10: [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).
return open(pathname, flags);
data/vmemcache-0.8.1/src/os_posix.c:113: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).
return fopen(pathname, mode);
data/vmemcache-0.8.1/src/os_posix.c:142:9: [2] (tmpfile) mkstemp:
Potential for temporary file vulnerability in some circumstances. Some
older Unix-like systems create temp files with permission to write by all
by default, so be sure to set the umask to override this. Also, some older
Unix systems might fail to use O_EXCL when opening the file, so make sure
that O_EXCL is used by the library (CWE-377).
return mkstemp(temp);
data/vmemcache-0.8.1/src/out.c:43: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 msg[MAXPRINT];
data/vmemcache-0.8.1/src/out.c:45:2: [2] (buffer) wchar_t:
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.
wchar_t wmsg[MAXPRINT];
data/vmemcache-0.8.1/src/out.c:160:15: [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).
Log_level = atoi(log_level);
data/vmemcache-0.8.1/src/out.c:170: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 log_file_pid[PATH_MAX];
data/vmemcache-0.8.1/src/out.c:183:4: [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 buff[UTIL_MAX_ERR_MSG];
data/vmemcache-0.8.1/src/out.c:195:15: [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).
int align = atoi(log_alignment);
data/vmemcache-0.8.1/src/out.c:206:9: [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.
static char namepath[PATH_MAX];
data/vmemcache-0.8.1/src/out.c:342: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 buf[MAXPRINT];
data/vmemcache-0.8.1/src/out.c:346: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 errstr[UTIL_MAX_ERR_MSG] = "";
data/vmemcache-0.8.1/src/out.c:399: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 errstr[UTIL_MAX_ERR_MSG] = "";
data/vmemcache-0.8.1/src/out.c:411:4: [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(errormsg, "Vsnprintf failed");
data/vmemcache-0.8.1/src/out.c:421: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[MAXPRINT];
data/vmemcache-0.8.1/src/util.c:66: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 lib_name[LIB_LOG_LEN];
data/vmemcache-0.8.1/src/util.c:67: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 func_name[FUNC_LOG_LEN];
data/vmemcache-0.8.1/src/util.c:68: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 suffix[SUFFIX_LEN];
data/vmemcache-0.8.1/src/util.c:73:3: [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(suffix, ".BEGIN");
data/vmemcache-0.8.1/src/util.c:75:3: [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(suffix, ".END");
data/vmemcache-0.8.1/src/util.c:252: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 unit[9] = {0};
data/vmemcache-0.8.1/src/util.c:305:22: [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).
_Pmreorder_emit = atoi(pmreorder_env);
data/vmemcache-0.8.1/src/vmemcache.c:294: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(ext.ptr, value, len);
data/vmemcache-0.8.1/src/vmemcache.c:317: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(get_req.vbuf, value, get_req.vbufsize);
data/vmemcache-0.8.1/src/vmemcache.c:352: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(entry->key.key, key, ksize);
data/vmemcache-0.8.1/src/vmemcache.c:439: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(vbuf, ptr, len);
data/vmemcache-0.8.1/src/vmemcache_index.c:156: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(e->key.key, key, ksize);
data/vmemcache-0.8.1/tests/example.c:22: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 buf[128];
data/vmemcache-0.8.1/tests/twolevel.c:136: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[12];
data/vmemcache-0.8.1/tests/vmemcache_test_basic.c:29:14: [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.
static const char *stat_str[VMEMCACHE_STATS_NUM] = {
data/vmemcache-0.8.1/tests/vmemcache_test_basic.c:44: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 vbuf[VSIZE];
data/vmemcache-0.8.1/tests/vmemcache_test_basic.c:64: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 buf[SIZE_1K];
data/vmemcache-0.8.1/tests/vmemcache_test_basic.c:324: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 nonexistent[4096];
data/vmemcache-0.8.1/tests/vmemcache_test_basic.c:326:2: [2] (buffer) strcat:
Does not check for buffer overflows when concatenating to destination
[MS-banned] (CWE-120). Consider using strcat_s, strncat, strlcat, or
snprintf (warning: strncat is easily misused). Risk is low because the
source is a constant string.
strcat(nonexistent, "/nonexistent_dir");
data/vmemcache-0.8.1/tests/vmemcache_test_basic.c:357: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 vbuf[VMEMCACHE_EXTENT]; /* user-provided buffer */
data/vmemcache-0.8.1/tests/vmemcache_test_basic.c:450: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(ctx->vbuf, key, size);
data/vmemcache-0.8.1/tests/vmemcache_test_basic.c:461: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 vbuf[VSIZE];
data/vmemcache-0.8.1/tests/vmemcache_test_basic.c:468: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 key[KSIZE];
data/vmemcache-0.8.1/tests/vmemcache_test_basic.c:469: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 value[VSIZE];
data/vmemcache-0.8.1/tests/vmemcache_test_basic.c:761:8: [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.
const char *key[N_KEYS] = {
data/vmemcache-0.8.1/tests/vmemcache_test_basic.c:904: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 buf[invalid_size];
data/vmemcache-0.8.1/tests/vmemcache_test_basic.c:1076: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(value->buffer,
data/vmemcache-0.8.1/tests/vmemcache_test_basic.c:1130: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 key[KSIZE];
data/vmemcache-0.8.1/tests/vmemcache_test_basic.c:1131: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 value[VSIZE + 1];
data/vmemcache-0.8.1/tests/vmemcache_test_basic.c:1142: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 vbuf[VSIZE + 1]; /* user-provided buffer */
data/vmemcache-0.8.1/tests/vmemcache_test_basic.c:1223: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 vbuf_eq[val_size];
data/vmemcache-0.8.1/tests/vmemcache_test_basic.c:1226: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 vbuf_twice[twice_size];
data/vmemcache-0.8.1/tests/vmemcache_test_basic.c:1229: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 vbuf_half[half_size];
data/vmemcache-0.8.1/tests/vmemcache_test_basic.c:1265: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 val[val_size];
data/vmemcache-0.8.1/tests/vmemcache_test_mt.c:127: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 vbuf[BUF_SIZE]; /* user-provided buffer */
data/vmemcache-0.8.1/tests/vmemcache_test_mt.c:323: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 vbuf[BUF_SIZE]; /* user-provided buffer */
data/vmemcache-0.8.1/tests/vmemcache_test_utilization.c:32: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 dir[4096];
data/vmemcache-0.8.1/tests/vmemcache_test_utilization.c:214: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 key[MAX_KEYSIZE];
data/vmemcache-0.8.1/tests/vmemcache_test_utilization.c:221:9: [2] (buffer) sprintf:
Does not check for buffer overflows (CWE-120). Use sprintf_s, snprintf, or
vsnprintf. Risk is low because the source has a constant maximum length.
len = sprintf(key, "%zu", keynum);
data/vmemcache-0.8.1/src/file.c:66:15: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
if ((nread = read(fd, sizebuf, MAX_SIZE_LENGTH)) < 0) {
data/vmemcache-0.8.1/src/file.h:81:19: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
#define util_read read
data/vmemcache-0.8.1/src/file.h:85:35: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
#define util_read(fd, buf, count) read(fd, buf, (unsigned)(count))
data/vmemcache-0.8.1/src/file_posix.c:43:26: [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).
char *fullname = alloca(strlen(dir) + strlen(templ) + 1);
data/vmemcache-0.8.1/src/file_posix.c:43:40: [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).
char *fullname = alloca(strlen(dir) + strlen(templ) + 1);
data/vmemcache-0.8.1/src/file_posix.c:52:22: [1] (access) umask:
Ensure that umask is given most restrictive possible setting (e.g., 066 or
077) (CWE-732).
mode_t prev_umask = umask(S_IRWXG | S_IRWXO);
data/vmemcache-0.8.1/src/file_posix.c:56:2: [1] (access) umask:
Ensure that umask is given most restrictive possible setting (e.g., 066 or
077) (CWE-732).
umask(prev_umask);
data/vmemcache-0.8.1/src/file_posix.c:153:2: [1] (buffer) strncpy:
Easily used incorrectly; doesn't always \0-terminate or check for invalid
pointers [MS-banned] (CWE-120).
strncpy(info->filename, d->d_name, NAME_MAX + 1);
data/vmemcache-0.8.1/src/file_posix.c:212:15: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
if ((nread = read(fd, sizebuf, MAX_SIZE_LENGTH)) < 0) {
data/vmemcache-0.8.1/src/file_posix.c:310:16: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
ssize_t len = read(dax_reg_id_fd, reg_id, DAX_REGION_ID_LEN);
data/vmemcache-0.8.1/src/out.c:171:16: [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).
size_t len = strlen(log_file);
data/vmemcache-0.8.1/src/util.c:69: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).
size_t lib_len = strlen(lib);
data/vmemcache-0.8.1/src/util.c:70:20: [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).
size_t func_len = strlen(func);
data/vmemcache-0.8.1/src/util.c:77:22: [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).
size_t suffix_len = strlen(suffix);
data/vmemcache-0.8.1/src/util.c:208: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).
int len = (int)strlen(str);
data/vmemcache-0.8.1/src/util.c:254:12: [1] (buffer) sscanf:
It's unclear if the %s limit in the format string is small enough
(CWE-120). Check that the limit is sufficiently small, or use a different
input function.
int ret = sscanf(str, "%zu%8s", &size, unit);
data/vmemcache-0.8.1/src/util.c:319:24: [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).
char *result = malloc(strlen(s1) + strlen(s2) + 1);
data/vmemcache-0.8.1/src/util.c:319:37: [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).
char *result = malloc(strlen(s1) + strlen(s2) + 1);
data/vmemcache-0.8.1/src/util.c:367:2: [1] (buffer) strncpy:
Easily used incorrectly; doesn't always \0-terminate or check for invalid
pointers [MS-banned] (CWE-120).
strncpy(dst, src, max_length);
data/vmemcache-0.8.1/src/util.c:402:14: [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).
position = strlen(buffer);
data/vmemcache-0.8.1/src/util_posix.c:112:3: [1] (buffer) strncpy:
Easily used incorrectly; doesn't always \0-terminate or check for invalid
pointers [MS-banned] (CWE-120). Risk is low because the source is a
constant string.
strncpy(path, "unknown", pathlen);
data/vmemcache-0.8.1/src/vmemcache.c:544:18: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
return (ssize_t)read;
data/vmemcache-0.8.1/tests/example.c:8:29: [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).
#define STR_AND_LEN(x) (x), strlen(x)
data/vmemcache-0.8.1/tests/twolevel.c:84:40: [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).
ssize_t ret = vmemcache_get(cache, x, strlen(x) + 1, NULL, 0, 0, NULL);
data/vmemcache-0.8.1/tests/twolevel.c:118:40: [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).
#define PUT(x) vmemcache_put(dram, x, strlen(x) + 1, lotta_zeroes, ZSIZE)
data/vmemcache-0.8.1/tests/vmemcache_test_basic.c:349:20: [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).
size_t key_size = strlen(key) + 1;
data/vmemcache-0.8.1/tests/vmemcache_test_basic.c:350:20: [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).
size_t val_size = strlen(value) + 1;
data/vmemcache-0.8.1/tests/vmemcache_test_basic.c:603:4: [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).
strlen(non_existent_key));
data/vmemcache-0.8.1/tests/vmemcache_test_basic.c:771:20: [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).
size_t key_size = strlen(key[0]) + 1;
data/vmemcache-0.8.1/tests/vmemcache_test_basic.c:772:20: [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).
size_t val_size = strlen(value) + 1;
data/vmemcache-0.8.1/tests/vmemcache_test_basic.c:1144:10: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
ssize_t read;
data/vmemcache-0.8.1/tests/vmemcache_test_basic.c:1154:6: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
if (read < 0)
data/vmemcache-0.8.1/tests/vmemcache_test_basic.c:1157:14: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
if ((size_t)read != VSIZE - offset)
data/vmemcache-0.8.1/tests/vmemcache_test_basic.c:1160:4: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
read, VSIZE - offset);
data/vmemcache-0.8.1/tests/vmemcache_test_basic.c:1168:7: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
vbuf[read] = 0;
data/vmemcache-0.8.1/tests/vmemcache_test_basic.c:1169:25: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
value[offset + (size_t)read] = 0;
data/vmemcache-0.8.1/tests/vmemcache_test_basic.c:1171:50: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
if (memcmp(vbuf, value + offset, (unsigned long)read))
data/vmemcache-0.8.1/tests/vmemcache_test_basic.c:1263: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).
size_t ksize = strlen(key) + 1;
ANALYSIS SUMMARY:
Hits = 155
Lines analyzed = 13433 in approximately 0.31 seconds (42920 lines/second)
Physical Source Lines of Code (SLOC) = 8950
Hits@level = [0] 108 [1] 38 [2] 74 [3] 12 [4] 25 [5] 6
Hits@level+ = [0+] 263 [1+] 155 [2+] 117 [3+] 43 [4+] 31 [5+] 6
Hits/KSLOC@level+ = [0+] 29.3855 [1+] 17.3184 [2+] 13.0726 [3+] 4.80447 [4+] 3.46369 [5+] 0.670391
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.