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/soapyuhd-0.3.6/SoapyUHDDevice.cpp Examining data/soapyuhd-0.3.6/TypeHelpers.hpp Examining data/soapyuhd-0.3.6/UHDSoapyDevice.cpp FINAL RESULTS: data/soapyuhd-0.3.6/SoapyUHDDevice.cpp:86:78: [4] (race) access: This usually indicates a security flaw. If an attacker can change anything along the path between the call to access() and the file's actual use (e.g., by moving files), the attacker can exploit the race condition (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid()) and try to open the file directly. if (tree->exists("/mboards/0/fw_version")) out["fw_version"] = tree->access<std::string>("/mboards/0/fw_version").get(); data/soapyuhd-0.3.6/SoapyUHDDevice.cpp:87:82: [4] (race) access: This usually indicates a security flaw. If an attacker can change anything along the path between the call to access() and the file's actual use (e.g., by moving files), the attacker can exploit the race condition (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid()) and try to open the file directly. if (tree->exists("/mboards/0/fpga_version")) out["fpga_version"] = tree->access<std::string>("/mboards/0/fpga_version").get(); data/soapyuhd-0.3.6/SoapyUHDDevice.cpp:591:71: [4] (race) access: This usually indicates a security flaw. If an attacker can change anything along the path between the call to access() and the file's actual use (e.g., by moving files), the attacker can exploit the race condition (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid()) and try to open the file directly. if (tree->exists(path)) return metaRangeToRangeList(tree->access<uhd::meta_range_t>(path).get()); data/soapyuhd-0.3.6/TypeHelpers.hpp:139:75: [2] (integer) atoi: Unless checked, the resulting number can exceed the expected range (CWE-190). If source untrusted, check both minimum and maximum, even if the input had no minus sign (large numbers can roll over into negative number; consider saving to an unsigned value if that is intended). case SoapySDR::ArgInfo::INT: return uhd::sensor_value_t(argInfo.name, atoi(value.c_str()), argInfo.units); data/soapyuhd-0.3.6/UHDSoapyDevice.cpp:582:69: [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. for (size_t i = 0; i < _nchan; i++) _offsetBuffs[i] = ((char *)buffs[i]) + total*_elemSize; data/soapyuhd-0.3.6/UHDSoapyDevice.cpp:770:69: [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. for (size_t i = 0; i < _nchan; i++) _offsetBuffs[i] = ((char *)buffs[i]) + total*_elemSize; ANALYSIS SUMMARY: Hits = 6 Lines analyzed = 2014 in approximately 0.07 seconds (29598 lines/second) Physical Source Lines of Code (SLOC) = 1551 Hits@level = [0] 2 [1] 0 [2] 3 [3] 0 [4] 3 [5] 0 Hits@level+ = [0+] 8 [1+] 6 [2+] 6 [3+] 3 [4+] 3 [5+] 0 Hits/KSLOC@level+ = [0+] 5.15796 [1+] 3.86847 [2+] 3.86847 [3+] 1.93424 [4+] 1.93424 [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.