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/pthreadpool-0.0~git20200615.029c886/bench/latency.cc Examining data/pthreadpool-0.0~git20200615.029c886/bench/throughput.cc Examining data/pthreadpool-0.0~git20200615.029c886/examples/addition.c Examining data/pthreadpool-0.0~git20200615.029c886/include/pthreadpool.h Examining data/pthreadpool-0.0~git20200615.029c886/src/fastpath.c Examining data/pthreadpool-0.0~git20200615.029c886/src/gcd.c Examining data/pthreadpool-0.0~git20200615.029c886/src/legacy-api.c Examining data/pthreadpool-0.0~git20200615.029c886/src/memory.c Examining data/pthreadpool-0.0~git20200615.029c886/src/portable-api.c Examining data/pthreadpool-0.0~git20200615.029c886/src/pthreads.c Examining data/pthreadpool-0.0~git20200615.029c886/src/shim.c Examining data/pthreadpool-0.0~git20200615.029c886/src/threadpool-atomics.h Examining data/pthreadpool-0.0~git20200615.029c886/src/threadpool-common.h Examining data/pthreadpool-0.0~git20200615.029c886/src/threadpool-object.h Examining data/pthreadpool-0.0~git20200615.029c886/src/threadpool-utils.h Examining data/pthreadpool-0.0~git20200615.029c886/src/windows.c Examining data/pthreadpool-0.0~git20200615.029c886/test/pthreadpool.cc FINAL RESULTS: data/pthreadpool-0.0~git20200615.029c886/src/gcd.c:104: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(&threadpool->params, params, params_size); data/pthreadpool-0.0~git20200615.029c886/src/pthreads.c:331: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(&threadpool->params, params, params_size); data/pthreadpool-0.0~git20200615.029c886/src/windows.c:219:3: [2] (buffer) CopyMemory: Does not check for buffer overflows when copying to destination (CWE-120). Make sure destination can always hold the source data. CopyMemory(&threadpool->params, params, params_size); data/pthreadpool-0.0~git20200615.029c886/src/memory.c:34:16: [1] (free) memalign: On some systems (though not Linux-based systems) an attempt to free() results from memalign() may fail. This may, on a few systems, be exploitable. Also note that memalign() may not check that the boundary parameter is correct (CWE-676). Use posix_memalign instead (defined in POSIX's 1003.1d). Don't switch to valloc(); it is marked as obsolete in BSD 4.3, as legacy in SUSv2, and is no longer defined in SUSv3. In some cases, malloc()'s alignment may be sufficient. threadpool = memalign(PTHREADPOOL_CACHELINE_SIZE, threadpool_size); ANALYSIS SUMMARY: Hits = 4 Lines analyzed = 14578 in approximately 0.32 seconds (45455 lines/second) Physical Source Lines of Code (SLOC) = 11254 Hits@level = [0] 4 [1] 1 [2] 3 [3] 0 [4] 0 [5] 0 Hits@level+ = [0+] 8 [1+] 4 [2+] 3 [3+] 0 [4+] 0 [5+] 0 Hits/KSLOC@level+ = [0+] 0.710858 [1+] 0.355429 [2+] 0.266572 [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.