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/amule-emc-0.5.2/src/MuleCollection.cpp Examining data/amule-emc-0.5.2/src/MuleCollection.h Examining data/amule-emc-0.5.2/src/Types.h Examining data/amule-emc-0.5.2/src/amule-emc.cpp Examining data/amule-emc-0.5.2/src/amule-emc.h FINAL RESULTS: data/amule-emc-0.5.2/src/MuleCollection.cpp:163:9: [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). infile.open(File.c_str(), std::ifstream::in|std::ifstream::binary); data/amule-emc-0.5.2/src/MuleCollection.cpp:356:9: [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). infile.open(File.c_str(), std::ifstream::in|std::ifstream::binary); data/amule-emc-0.5.2/src/MuleCollection.cpp:135:9: [1] (buffer) read: Check buffer boundaries if used in a loop including recursive loops (CWE-120, CWE-20). infile.read(reinterpret_cast<char *>(&integer),sizeof(intType)); data/amule-emc-0.5.2/src/MuleCollection.cpp:143:10: [1] (buffer) read: Check buffer boundaries if used in a loop including recursive loops (CWE-120, CWE-20). infile.read(&buffer[0], TagType - 0x10); data/amule-emc-0.5.2/src/MuleCollection.cpp:151:10: [1] (buffer) read: Check buffer boundaries if used in a loop including recursive loops (CWE-120, CWE-20). infile.read(&buffer[0], TagStringSize); data/amule-emc-0.5.2/src/MuleCollection.cpp:217:11: [1] (buffer) read: Check buffer boundaries if used in a loop including recursive loops (CWE-120, CWE-20). infile.read(&CollectionAuthorKey[0], hTagBlobSize); data/amule-emc-0.5.2/src/MuleCollection.cpp:275:12: [1] (buffer) read: Check buffer boundaries if used in a loop including recursive loops (CWE-120, CWE-20). infile.read(&bFileHash[0], 16); ANALYSIS SUMMARY: Hits = 7 Lines analyzed = 795 in approximately 0.03 seconds (30789 lines/second) Physical Source Lines of Code (SLOC) = 499 Hits@level = [0] 0 [1] 5 [2] 2 [3] 0 [4] 0 [5] 0 Hits@level+ = [0+] 7 [1+] 7 [2+] 2 [3+] 0 [4+] 0 [5+] 0 Hits/KSLOC@level+ = [0+] 14.0281 [1+] 14.0281 [2+] 4.00802 [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.