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/ums2net-0.1.3/src/configReader.cc Examining data/ums2net-0.1.3/src/configReader.h Examining data/ums2net-0.1.3/src/main.cc Examining data/ums2net-0.1.3/src/main.h Examining data/ums2net-0.1.3/src/servantThread.cc Examining data/ums2net-0.1.3/src/servantThread.h Examining data/ums2net-0.1.3/src/test/testUMS2NET-ConfRecord.cc Examining data/ums2net-0.1.3/src/test/testUMS2NET-ConfigReader.cc Examining data/ums2net-0.1.3/src/ums2netconfrecord.cc Examining data/ums2net-0.1.3/src/ums2netconfrecord.h FINAL RESULTS: data/ums2net-0.1.3/src/main.cc:115:17: [3] (buffer) getopt: Some older implementations do not protect against internal buffer overflows (CWE-120, CWE-20). Check implementation on installation, or limit the size of all string inputs. while ((opt = getopt(argc, argv, "dc:P:")) != -1) { data/ums2net-0.1.3/src/configReader.cc:36:8: [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). file.open(filename, std::ios::in); data/ums2net-0.1.3/src/main.cc:56:8: [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). fout.open(pidfile.c_str(), std::ofstream::out | std::ofstream::trunc); data/ums2net-0.1.3/src/main.cc:59: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 errbuf[1024]; data/ums2net-0.1.3/src/main.cc:97:7: [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 errbuf[1024]; data/ums2net-0.1.3/src/servantThread.cc:75:7: [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 errbuf[1024]; data/ums2net-0.1.3/src/servantThread.cc:150:15: [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 outFD = open(devFilename.c_str(), O_RDWR); data/ums2net-0.1.3/src/servantThread.cc:153: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 errbuf[1024]; data/ums2net-0.1.3/src/servantThread.cc:178:7: [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 errbuf[1024]; data/ums2net-0.1.3/src/servantThread.cc:187:7: [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 errbuf[1024]; data/ums2net-0.1.3/src/servantThread.cc:231: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 errbuf[1024]; data/ums2net-0.1.3/src/servantThread.cc:243: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 errbuf[1024]; data/ums2net-0.1.3/src/servantThread.cc:260: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 errbuf[1024]; data/ums2net-0.1.3/src/servantThread.cc:271: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 errbuf[1024]; data/ums2net-0.1.3/src/servantThread.cc:291:2: [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 errbuf[1024]; data/ums2net-0.1.3/src/servantThread.cc:305:7: [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 errbuf[1024]; data/ums2net-0.1.3/src/test/testUMS2NET-ConfigReader.cc:53:10: [2] (tmpfile) mkstemp: Potential for temporary file vulnerability in some circumstances. Some older Unix-like systems create temp files with permission to write by all by default, so be sure to set the umask to override this. Also, some older Unix systems might fail to use O_EXCL when opening the file, so make sure that O_EXCL is used by the library (CWE-377). fd = mkstemp(filename); data/ums2net-0.1.3/src/test/testUMS2NET-ConfigReader.cc:56:31: [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). w1 = write(fd, data[i], strlen(data[i])); ANALYSIS SUMMARY: Hits = 18 Lines analyzed = 1036 in approximately 0.04 seconds (26080 lines/second) Physical Source Lines of Code (SLOC) = 630 Hits@level = [0] 24 [1] 1 [2] 16 [3] 1 [4] 0 [5] 0 Hits@level+ = [0+] 42 [1+] 18 [2+] 17 [3+] 1 [4+] 0 [5+] 0 Hits/KSLOC@level+ = [0+] 66.6667 [1+] 28.5714 [2+] 26.9841 [3+] 1.5873 [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.