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/php-geos-1.0.0/geos.c Examining data/php-geos-1.0.0/php_geos.h FINAL RESULTS: data/php-geos-1.0.0/geos.c:130:5: [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(message, sizeof(message) - 1, fmt, args); data/php-geos-1.0.0/geos.c:142:5: [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(message, sizeof(message) - 1, fmt, args); data/php-geos-1.0.0/geos.c:127:5: [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 message[256]; data/php-geos-1.0.0/geos.c:139:5: [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 message[256]; data/php-geos-1.0.0/geos.c:3273: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(&WKTReader_object_handlers, data/php-geos-1.0.0/geos.c:3285: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(&WKTWriter_object_handlers, data/php-geos-1.0.0/geos.c:3297: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(&Geometry_object_handlers, data/php-geos-1.0.0/geos.c:3312: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(&WKBWriter_object_handlers, data/php-geos-1.0.0/geos.c:3324: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(&WKBReader_object_handlers, data/php-geos-1.0.0/geos.c:2339:23: [1] (buffer) read: Check buffer boundaries if used in a loop including recursive loops (CWE-120, CWE-20). PHP_METHOD(WKTReader, read); data/php-geos-1.0.0/geos.c:2343:23: [1] (buffer) read: Check buffer boundaries if used in a loop including recursive loops (CWE-120, CWE-20). PHP_ME(WKTReader, read, NULL, 0) data/php-geos-1.0.0/geos.c:2394:23: [1] (buffer) read: Check buffer boundaries if used in a loop including recursive loops (CWE-120, CWE-20). PHP_METHOD(WKTReader, read) data/php-geos-1.0.0/geos.c:2895:23: [1] (buffer) read: Check buffer boundaries if used in a loop including recursive loops (CWE-120, CWE-20). PHP_METHOD(WKBReader, read); data/php-geos-1.0.0/geos.c:2900:23: [1] (buffer) read: Check buffer boundaries if used in a loop including recursive loops (CWE-120, CWE-20). PHP_ME(WKBReader, read, NULL, 0) data/php-geos-1.0.0/geos.c:2951:23: [1] (buffer) read: Check buffer boundaries if used in a loop including recursive loops (CWE-120, CWE-20). PHP_METHOD(WKBReader, read) ANALYSIS SUMMARY: Hits = 15 Lines analyzed = 3488 in approximately 0.07 seconds (49437 lines/second) Physical Source Lines of Code (SLOC) = 2376 Hits@level = [0] 0 [1] 6 [2] 7 [3] 0 [4] 2 [5] 0 Hits@level+ = [0+] 15 [1+] 15 [2+] 9 [3+] 2 [4+] 2 [5+] 0 Hits/KSLOC@level+ = [0+] 6.31313 [1+] 6.31313 [2+] 3.78788 [3+] 0.841751 [4+] 0.841751 [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.