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/haskell-network-3.1.1.1/cbits/HsNet.c Examining data/haskell-network-3.1.1.1/cbits/ancilData.c Examining data/haskell-network-3.1.1.1/cbits/asyncAccept.c Examining data/haskell-network-3.1.1.1/cbits/initWinSock.c Examining data/haskell-network-3.1.1.1/cbits/winSockErr.c Examining data/haskell-network-3.1.1.1/include/HsNet.h Examining data/haskell-network-3.1.1.1/include/HsNetDef.h FINAL RESULTS: data/haskell-network-3.1.1.1/cbits/ancilData.c:41: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 buf[2]; data/haskell-network-3.1.1.1/cbits/ancilData.c:47: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 ancBuffer[CMSG_SPACE(sizeof(int))]; data/haskell-network-3.1.1.1/cbits/ancilData.c:77: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 duffBuf[10]; data/haskell-network-3.1.1.1/cbits/winSockErr.c:12:10: [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. static char otherErrMsg[256]; data/haskell-network-3.1.1.1/cbits/winSockErr.c:70:5: [2] (buffer) sprintf: Does not check for buffer overflows (CWE-120). Use sprintf_s, snprintf, or vsnprintf. Risk is low because the source has a constant maximum length. sprintf(otherErrMsg, "Unknown WinSock error: %u", err); ANALYSIS SUMMARY: Hits = 5 Lines analyzed = 539 in approximately 0.07 seconds (7624 lines/second) Physical Source Lines of Code (SLOC) = 406 Hits@level = [0] 1 [1] 0 [2] 5 [3] 0 [4] 0 [5] 0 Hits@level+ = [0+] 6 [1+] 5 [2+] 5 [3+] 0 [4+] 0 [5+] 0 Hits/KSLOC@level+ = [0+] 14.7783 [1+] 12.3153 [2+] 12.3153 [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.