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/argagg-0.4.6/examples/gengetopt_main1.cpp Examining data/argagg-0.4.6/examples/joinargs.cpp Examining data/argagg-0.4.6/include/argagg/argagg.hpp Examining data/argagg-0.4.6/test/test.cpp FINAL RESULTS: data/argagg-0.4.6/include/argagg/argagg.hpp:1485:5: [4] (shell) execvp: This causes a new program to execute and is difficult to use safely (CWE-78). try using a library call that implements the same functionality if available. execvp(const_cast<char*>(argv[0]), const_cast<char**>(argv)); data/argagg-0.4.6/examples/joinargs.cpp:102:14: [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). g_dev_null.open("/dev/null"); // portable? eh... simple? yes! data/argagg-0.4.6/examples/joinargs.cpp:118:17: [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). output_file.open(filename); data/argagg-0.4.6/include/argagg/argagg.hpp:1499: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[64]; data/argagg-0.4.6/include/argagg/argagg.hpp:827:19: [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). auto len = std::strlen(s); data/argagg-0.4.6/include/argagg/argagg.hpp:861:14: [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). len = std::strlen(name); data/argagg-0.4.6/include/argagg/argagg.hpp:907:19: [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). auto len = std::strlen(s); data/argagg-0.4.6/include/argagg/argagg.hpp:941:14: [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). len = std::strlen(name); data/argagg-0.4.6/include/argagg/argagg.hpp:1109:27: [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). auto arg_i_len = std::strlen(arg_i_cstr); data/argagg-0.4.6/include/argagg/argagg.hpp:1501:23: [1] (buffer) read: Check buffer boundaries if used in a loop including recursive loops (CWE-120, CWE-20). auto read_count = read( data/argagg-0.4.6/test/test.cpp:897:14: [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). if (std::strlen(s) == 0) { data/argagg-0.4.6/test/test.cpp:903: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). ret.emplace_back(s, std::strlen(s)); ANALYSIS SUMMARY: Hits = 12 Lines analyzed = 2824 in approximately 0.09 seconds (30812 lines/second) Physical Source Lines of Code (SLOC) = 1867 Hits@level = [0] 0 [1] 8 [2] 3 [3] 0 [4] 1 [5] 0 Hits@level+ = [0+] 12 [1+] 12 [2+] 4 [3+] 1 [4+] 1 [5+] 0 Hits/KSLOC@level+ = [0+] 6.42742 [1+] 6.42742 [2+] 2.14247 [3+] 0.535619 [4+] 0.535619 [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.