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/python-cryptography-3.2.1/src/_cffi_src/hazmat_src/padding.c Examining data/python-cryptography-3.2.1/src/_cffi_src/hazmat_src/padding.h Examining data/python-cryptography-3.2.1/src/_cffi_src/openssl/src/osrandom_engine.c Examining data/python-cryptography-3.2.1/src/_cffi_src/openssl/src/osrandom_engine.h FINAL RESULTS: data/python-cryptography-3.2.1/src/_cffi_src/openssl/src/osrandom_engine.c:532: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). strcpy((char *)p, name); data/python-cryptography-3.2.1/src/_cffi_src/openssl/src/osrandom_engine.c:106:14: [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(path, open_flags); data/python-cryptography-3.2.1/src/_cffi_src/openssl/src/osrandom_engine.c:334: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. char dest[1]; data/python-cryptography-3.2.1/src/_cffi_src/hazmat_src/padding.c:26:9: [1] (buffer) mismatch: Function does not check the second iterator for over-read conditions (CWE-126). This function is often discouraged by most C++ coding standards in favor of its safer alternatives provided since C++14. Consider using a form of this function that checks the second iterator before potentially overflowing it. mismatch |= (mask & (pad_size ^ b)); data/python-cryptography-3.2.1/src/_cffi_src/hazmat_src/padding.c:30:5: [1] (buffer) mismatch: Function does not check the second iterator for over-read conditions (CWE-126). This function is often discouraged by most C++ coding standards in favor of its safer alternatives provided since C++14. Consider using a form of this function that checks the second iterator before potentially overflowing it. mismatch |= ~Cryptography_constant_time_lt(0, pad_size); data/python-cryptography-3.2.1/src/_cffi_src/hazmat_src/padding.c:31:5: [1] (buffer) mismatch: Function does not check the second iterator for over-read conditions (CWE-126). This function is often discouraged by most C++ coding standards in favor of its safer alternatives provided since C++14. Consider using a form of this function that checks the second iterator before potentially overflowing it. mismatch |= Cryptography_constant_time_lt(block_len, pad_size); data/python-cryptography-3.2.1/src/_cffi_src/hazmat_src/padding.c:34:5: [1] (buffer) mismatch: Function does not check the second iterator for over-read conditions (CWE-126). This function is often discouraged by most C++ coding standards in favor of its safer alternatives provided since C++14. Consider using a form of this function that checks the second iterator before potentially overflowing it. mismatch |= mismatch >> 8; data/python-cryptography-3.2.1/src/_cffi_src/hazmat_src/padding.c:34:17: [1] (buffer) mismatch: Function does not check the second iterator for over-read conditions (CWE-126). This function is often discouraged by most C++ coding standards in favor of its safer alternatives provided since C++14. Consider using a form of this function that checks the second iterator before potentially overflowing it. mismatch |= mismatch >> 8; data/python-cryptography-3.2.1/src/_cffi_src/hazmat_src/padding.c:35:5: [1] (buffer) mismatch: Function does not check the second iterator for over-read conditions (CWE-126). This function is often discouraged by most C++ coding standards in favor of its safer alternatives provided since C++14. Consider using a form of this function that checks the second iterator before potentially overflowing it. mismatch |= mismatch >> 4; data/python-cryptography-3.2.1/src/_cffi_src/hazmat_src/padding.c:35:17: [1] (buffer) mismatch: Function does not check the second iterator for over-read conditions (CWE-126). This function is often discouraged by most C++ coding standards in favor of its safer alternatives provided since C++14. Consider using a form of this function that checks the second iterator before potentially overflowing it. mismatch |= mismatch >> 4; data/python-cryptography-3.2.1/src/_cffi_src/hazmat_src/padding.c:36:5: [1] (buffer) mismatch: Function does not check the second iterator for over-read conditions (CWE-126). This function is often discouraged by most C++ coding standards in favor of its safer alternatives provided since C++14. Consider using a form of this function that checks the second iterator before potentially overflowing it. mismatch |= mismatch >> 2; data/python-cryptography-3.2.1/src/_cffi_src/hazmat_src/padding.c:36:17: [1] (buffer) mismatch: Function does not check the second iterator for over-read conditions (CWE-126). This function is often discouraged by most C++ coding standards in favor of its safer alternatives provided since C++14. Consider using a form of this function that checks the second iterator before potentially overflowing it. mismatch |= mismatch >> 2; data/python-cryptography-3.2.1/src/_cffi_src/hazmat_src/padding.c:37:5: [1] (buffer) mismatch: Function does not check the second iterator for over-read conditions (CWE-126). This function is often discouraged by most C++ coding standards in favor of its safer alternatives provided since C++14. Consider using a form of this function that checks the second iterator before potentially overflowing it. mismatch |= mismatch >> 1; data/python-cryptography-3.2.1/src/_cffi_src/hazmat_src/padding.c:37:17: [1] (buffer) mismatch: Function does not check the second iterator for over-read conditions (CWE-126). This function is often discouraged by most C++ coding standards in favor of its safer alternatives provided since C++14. Consider using a form of this function that checks the second iterator before potentially overflowing it. mismatch |= mismatch >> 1; data/python-cryptography-3.2.1/src/_cffi_src/hazmat_src/padding.c:39:13: [1] (buffer) mismatch: Function does not check the second iterator for over-read conditions (CWE-126). This function is often discouraged by most C++ coding standards in favor of its safer alternatives provided since C++14. Consider using a form of this function that checks the second iterator before potentially overflowing it. return (mismatch & 1) == 0; data/python-cryptography-3.2.1/src/_cffi_src/hazmat_src/padding.c:51:9: [1] (buffer) mismatch: Function does not check the second iterator for over-read conditions (CWE-126). This function is often discouraged by most C++ coding standards in favor of its safer alternatives provided since C++14. Consider using a form of this function that checks the second iterator before potentially overflowing it. mismatch |= (mask & b); data/python-cryptography-3.2.1/src/_cffi_src/hazmat_src/padding.c:55:5: [1] (buffer) mismatch: Function does not check the second iterator for over-read conditions (CWE-126). This function is often discouraged by most C++ coding standards in favor of its safer alternatives provided since C++14. Consider using a form of this function that checks the second iterator before potentially overflowing it. mismatch |= ~Cryptography_constant_time_lt(0, pad_size); data/python-cryptography-3.2.1/src/_cffi_src/hazmat_src/padding.c:56:5: [1] (buffer) mismatch: Function does not check the second iterator for over-read conditions (CWE-126). This function is often discouraged by most C++ coding standards in favor of its safer alternatives provided since C++14. Consider using a form of this function that checks the second iterator before potentially overflowing it. mismatch |= Cryptography_constant_time_lt(block_len, pad_size); data/python-cryptography-3.2.1/src/_cffi_src/hazmat_src/padding.c:59:5: [1] (buffer) mismatch: Function does not check the second iterator for over-read conditions (CWE-126). This function is often discouraged by most C++ coding standards in favor of its safer alternatives provided since C++14. Consider using a form of this function that checks the second iterator before potentially overflowing it. mismatch |= mismatch >> 8; data/python-cryptography-3.2.1/src/_cffi_src/hazmat_src/padding.c:59:17: [1] (buffer) mismatch: Function does not check the second iterator for over-read conditions (CWE-126). This function is often discouraged by most C++ coding standards in favor of its safer alternatives provided since C++14. Consider using a form of this function that checks the second iterator before potentially overflowing it. mismatch |= mismatch >> 8; data/python-cryptography-3.2.1/src/_cffi_src/hazmat_src/padding.c:60:5: [1] (buffer) mismatch: Function does not check the second iterator for over-read conditions (CWE-126). This function is often discouraged by most C++ coding standards in favor of its safer alternatives provided since C++14. Consider using a form of this function that checks the second iterator before potentially overflowing it. mismatch |= mismatch >> 4; data/python-cryptography-3.2.1/src/_cffi_src/hazmat_src/padding.c:60:17: [1] (buffer) mismatch: Function does not check the second iterator for over-read conditions (CWE-126). This function is often discouraged by most C++ coding standards in favor of its safer alternatives provided since C++14. Consider using a form of this function that checks the second iterator before potentially overflowing it. mismatch |= mismatch >> 4; data/python-cryptography-3.2.1/src/_cffi_src/hazmat_src/padding.c:61:5: [1] (buffer) mismatch: Function does not check the second iterator for over-read conditions (CWE-126). This function is often discouraged by most C++ coding standards in favor of its safer alternatives provided since C++14. Consider using a form of this function that checks the second iterator before potentially overflowing it. mismatch |= mismatch >> 2; data/python-cryptography-3.2.1/src/_cffi_src/hazmat_src/padding.c:61:17: [1] (buffer) mismatch: Function does not check the second iterator for over-read conditions (CWE-126). This function is often discouraged by most C++ coding standards in favor of its safer alternatives provided since C++14. Consider using a form of this function that checks the second iterator before potentially overflowing it. mismatch |= mismatch >> 2; data/python-cryptography-3.2.1/src/_cffi_src/hazmat_src/padding.c:62:5: [1] (buffer) mismatch: Function does not check the second iterator for over-read conditions (CWE-126). This function is often discouraged by most C++ coding standards in favor of its safer alternatives provided since C++14. Consider using a form of this function that checks the second iterator before potentially overflowing it. mismatch |= mismatch >> 1; data/python-cryptography-3.2.1/src/_cffi_src/hazmat_src/padding.c:62:17: [1] (buffer) mismatch: Function does not check the second iterator for over-read conditions (CWE-126). This function is often discouraged by most C++ coding standards in favor of its safer alternatives provided since C++14. Consider using a form of this function that checks the second iterator before potentially overflowing it. mismatch |= mismatch >> 1; data/python-cryptography-3.2.1/src/_cffi_src/hazmat_src/padding.c:64:13: [1] (buffer) mismatch: Function does not check the second iterator for over-read conditions (CWE-126). This function is often discouraged by most C++ coding standards in favor of its safer alternatives provided since C++14. Consider using a form of this function that checks the second iterator before potentially overflowing it. return (mismatch & 1) == 0; data/python-cryptography-3.2.1/src/_cffi_src/openssl/src/osrandom_engine.c:210:22: [1] (buffer) read: Check buffer boundaries if used in a loop including recursive loops (CWE-120, CWE-20). n = (int)read(fd, buffer, (size_t)size); data/python-cryptography-3.2.1/src/_cffi_src/openssl/src/osrandom_engine.c:522:15: [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). len = strlen(name); ANALYSIS SUMMARY: Hits = 29 Lines analyzed = 849 in approximately 0.05 seconds (15444 lines/second) Physical Source Lines of Code (SLOC) = 653 Hits@level = [0] 0 [1] 26 [2] 2 [3] 0 [4] 1 [5] 0 Hits@level+ = [0+] 29 [1+] 29 [2+] 3 [3+] 1 [4+] 1 [5+] 0 Hits/KSLOC@level+ = [0+] 44.4104 [1+] 44.4104 [2+] 4.59418 [3+] 1.53139 [4+] 1.53139 [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.