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/globus-xio-gsi-driver-5.2/globus_xio_gsi.c Examining data/globus-xio-gsi-driver-5.2/globus_xio_gsi.h Examining data/globus-xio-gsi-driver-5.2/globus_i_xio_gsi.h FINAL RESULTS: data/globus-xio-gsi-driver-5.2/globus_i_xio_gsi.h:215: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. unsigned char header[4]; data/globus-xio-gsi-driver-5.2/globus_i_xio_gsi.h:255: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. unsigned char header[4]; data/globus-xio-gsi-driver-5.2/globus_xio_gsi.c:275:17: [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( data/globus-xio-gsi-driver-5.2/globus_xio_gsi.c:540:5: [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(attr, src, sizeof(globus_l_attr_t)); data/globus-xio-gsi-driver-5.2/globus_xio_gsi.c:570:9: [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(cp, attr->alpn_list, attr->alpn_list_len); data/globus-xio-gsi-driver-5.2/globus_xio_gsi.c:916:13: [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((globus_byte_t *) data/globus-xio-gsi-driver-5.2/globus_xio_gsi.c:934:13: [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((globus_byte_t *) data/globus-xio-gsi-driver-5.2/globus_xio_gsi.c:267:38: [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). alpn_list_len += 1 + strlen(in_protocols[i]); data/globus-xio-gsi-driver-5.2/globus_xio_gsi.c:272:39: [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 protocol_len = strlen(in_protocols[i]); data/globus-xio-gsi-driver-5.2/globus_xio_gsi.c:1468:21: [1] (buffer) equal: 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. int equal; data/globus-xio-gsi-driver-5.2/globus_xio_gsi.c:1476:39: [1] (buffer) equal: 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. &equal); data/globus-xio-gsi-driver-5.2/globus_xio_gsi.c:1485:22: [1] (buffer) equal: 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. if (!equal) data/globus-xio-gsi-driver-5.2/globus_xio_gsi.c:1520:21: [1] (buffer) equal: 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. if(!equal) data/globus-xio-gsi-driver-5.2/globus_xio_gsi.c:3966:23: [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). send_tok.length = strlen(val) + 1; data/globus-xio-gsi-driver-5.2/globus_xio_gsi.c:4206:34: [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). name_buffer.length = strlen(name_buffer.value); ANALYSIS SUMMARY: Hits = 15 Lines analyzed = 5272 in approximately 0.13 seconds (41425 lines/second) Physical Source Lines of Code (SLOC) = 3760 Hits@level = [0] 0 [1] 8 [2] 7 [3] 0 [4] 0 [5] 0 Hits@level+ = [0+] 15 [1+] 15 [2+] 7 [3+] 0 [4+] 0 [5+] 0 Hits/KSLOC@level+ = [0+] 3.98936 [1+] 3.98936 [2+] 1.8617 [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.