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/yp-svipc-0.16/common/svipc.h Examining data/yp-svipc-0.16/common/svipc_misc.c Examining data/yp-svipc-0.16/common/svipc_msq.c Examining data/yp-svipc-0.16/common/svipc_msq.h Examining data/yp-svipc-0.16/common/svipc_sem.c Examining data/yp-svipc-0.16/common/svipc_sem.h Examining data/yp-svipc-0.16/common/svipc_shm.c Examining data/yp-svipc-0.16/common/svipc_shm.h Examining data/yp-svipc-0.16/common/svipc_misc.h Examining data/yp-svipc-0.16/python/svipc_module.c Examining data/yp-svipc-0.16/yorick/yorick_svipc.c FINAL RESULTS: data/yp-svipc-0.16/common/svipc_misc.h:58:8: [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, fmt, ## __VA_ARGS__); \ data/yp-svipc-0.16/common/svipc_msq.h:29: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 mtext[1]; /* pointer to message data */ data/yp-svipc-0.16/common/svipc_shm.c:73: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 desc[SLOT_DESC_STRING_MAX]; data/yp-svipc-0.16/common/svipc_shm.c:86: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 id[SLOT_DESC_STRING_MAX]; data/yp-svipc-0.16/common/svipc_shm.c:889: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((void *)p_addr, a->data, payload_bytes); data/yp-svipc-0.16/common/svipc_shm.c:945: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(a->data, p_addr, payload_bytes); data/yp-svipc-0.16/python/svipc_module.c:217: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(arr.number, PyArray_DIMS(inp_array), data/yp-svipc-0.16/python/svipc_module.c:670: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(msgp_pint, PyArray_DATA(inp_array), totalnumber * sizeoftype); data/yp-svipc-0.16/yorick/yorick_svipc.c:220: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(buff, arr.data, totalnumber * a->type.base->size); data/yp-svipc-0.16/yorick/yorick_svipc.c:449: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(msgp_pint, a, totalnumber * sizeoftype); data/yp-svipc-0.16/yorick/yorick_svipc.c:505: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(buff, msgp_pint, totalnumber * a->type.base->size); data/yp-svipc-0.16/common/svipc_misc.c:108:4: [1] (obsolete) usleep: This C routine is considered obsolete (as opposed to the shell command by the same name). The interaction of this function with SIGALRM and other timer functions such as sleep(), alarm(), setitimer(), and nanosleep() is unspecified (CWE-676). Use nanosleep(2) or setitimer(2) instead. usleep(SVIPC_USLEEP_QUANTUM); data/yp-svipc-0.16/common/svipc_shm.c:434:3: [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(m->sse[slot].desc, ""); data/yp-svipc-0.16/common/svipc_shm.c:803:4: [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(m->sse[i].desc, ""); data/yp-svipc-0.16/common/svipc_shm.c:1090:3: [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(this->id, ""); ANALYSIS SUMMARY: Hits = 15 Lines analyzed = 3310 in approximately 0.10 seconds (33959 lines/second) Physical Source Lines of Code (SLOC) = 2055 Hits@level = [0] 39 [1] 4 [2] 10 [3] 0 [4] 1 [5] 0 Hits@level+ = [0+] 54 [1+] 15 [2+] 11 [3+] 1 [4+] 1 [5+] 0 Hits/KSLOC@level+ = [0+] 26.2774 [1+] 7.29927 [2+] 5.3528 [3+] 0.486618 [4+] 0.486618 [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.