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/nfstrace-0.4.3.2+git20200805+b220d04/analyzers/src/breakdown/analyzer.cpp
Examining data/nfstrace-0.4.3.2+git20200805+b220d04/analyzers/src/breakdown/breakdowncounter.cpp
Examining data/nfstrace-0.4.3.2+git20200805+b220d04/analyzers/src/breakdown/breakdowncounter.h
Examining data/nfstrace-0.4.3.2+git20200805+b220d04/analyzers/src/breakdown/cifsv1breakdownanalyzer.cpp
Examining data/nfstrace-0.4.3.2+git20200805+b220d04/analyzers/src/breakdown/cifsv1breakdownanalyzer.h
Examining data/nfstrace-0.4.3.2+git20200805+b220d04/analyzers/src/breakdown/cifsv1commands.cpp
Examining data/nfstrace-0.4.3.2+git20200805+b220d04/analyzers/src/breakdown/cifsv1commands.h
Examining data/nfstrace-0.4.3.2+git20200805+b220d04/analyzers/src/breakdown/cifsv2breakdownanalyzer.cpp
Examining data/nfstrace-0.4.3.2+git20200805+b220d04/analyzers/src/breakdown/cifsv2breakdownanalyzer.h
Examining data/nfstrace-0.4.3.2+git20200805+b220d04/analyzers/src/breakdown/cifsv2commands.cpp
Examining data/nfstrace-0.4.3.2+git20200805+b220d04/analyzers/src/breakdown/cifsv2commands.h
Examining data/nfstrace-0.4.3.2+git20200805+b220d04/analyzers/src/breakdown/commandrepresenter.h
Examining data/nfstrace-0.4.3.2+git20200805+b220d04/analyzers/src/breakdown/latencies.cpp
Examining data/nfstrace-0.4.3.2+git20200805+b220d04/analyzers/src/breakdown/latencies.h
Examining data/nfstrace-0.4.3.2+git20200805+b220d04/analyzers/src/breakdown/nfsv3breakdownanalyzer.cpp
Examining data/nfstrace-0.4.3.2+git20200805+b220d04/analyzers/src/breakdown/nfsv3breakdownanalyzer.h
Examining data/nfstrace-0.4.3.2+git20200805+b220d04/analyzers/src/breakdown/nfsv3commands.cpp
Examining data/nfstrace-0.4.3.2+git20200805+b220d04/analyzers/src/breakdown/nfsv3commands.h
Examining data/nfstrace-0.4.3.2+git20200805+b220d04/analyzers/src/breakdown/nfsv41breakdownanalyzer.cpp
Examining data/nfstrace-0.4.3.2+git20200805+b220d04/analyzers/src/breakdown/nfsv41breakdownanalyzer.h
Examining data/nfstrace-0.4.3.2+git20200805+b220d04/analyzers/src/breakdown/nfsv41commands.cpp
Examining data/nfstrace-0.4.3.2+git20200805+b220d04/analyzers/src/breakdown/nfsv41commands.h
Examining data/nfstrace-0.4.3.2+git20200805+b220d04/analyzers/src/breakdown/nfsv4breakdownanalyzer.cpp
Examining data/nfstrace-0.4.3.2+git20200805+b220d04/analyzers/src/breakdown/nfsv4breakdownanalyzer.h
Examining data/nfstrace-0.4.3.2+git20200805+b220d04/analyzers/src/breakdown/nfsv4commands.cpp
Examining data/nfstrace-0.4.3.2+git20200805+b220d04/analyzers/src/breakdown/nfsv4commands.h
Examining data/nfstrace-0.4.3.2+git20200805+b220d04/analyzers/src/breakdown/nfsv4representer.cpp
Examining data/nfstrace-0.4.3.2+git20200805+b220d04/analyzers/src/breakdown/nfsv4representer.h
Examining data/nfstrace-0.4.3.2+git20200805+b220d04/analyzers/src/breakdown/representer.cpp
Examining data/nfstrace-0.4.3.2+git20200805+b220d04/analyzers/src/breakdown/representer.h
Examining data/nfstrace-0.4.3.2+git20200805+b220d04/analyzers/src/breakdown/statistics.cpp
Examining data/nfstrace-0.4.3.2+git20200805+b220d04/analyzers/src/breakdown/statistics.h
Examining data/nfstrace-0.4.3.2+git20200805+b220d04/analyzers/src/breakdown/statisticscompositor.cpp
Examining data/nfstrace-0.4.3.2+git20200805+b220d04/analyzers/src/breakdown/statisticscompositor.h
Examining data/nfstrace-0.4.3.2+git20200805+b220d04/analyzers/src/json/abstract_tcp_service.cpp
Examining data/nfstrace-0.4.3.2+git20200805+b220d04/analyzers/src/json/abstract_tcp_service.h
Examining data/nfstrace-0.4.3.2+git20200805+b220d04/analyzers/src/json/ip_endpoint.cpp
Examining data/nfstrace-0.4.3.2+git20200805+b220d04/analyzers/src/json/ip_endpoint.h
Examining data/nfstrace-0.4.3.2+git20200805+b220d04/analyzers/src/json/json_analyzer.cpp
Examining data/nfstrace-0.4.3.2+git20200805+b220d04/analyzers/src/json/json_analyzer.h
Examining data/nfstrace-0.4.3.2+git20200805+b220d04/analyzers/src/json/json_plugin.cpp
Examining data/nfstrace-0.4.3.2+git20200805+b220d04/analyzers/src/json/json_tcp_service.cpp
Examining data/nfstrace-0.4.3.2+git20200805+b220d04/analyzers/src/json/json_tcp_service.h
Examining data/nfstrace-0.4.3.2+git20200805+b220d04/analyzers/src/test/test_analyzer.cpp
Examining data/nfstrace-0.4.3.2+git20200805+b220d04/analyzers/src/watch/nc_windows/header_window.cpp
Examining data/nfstrace-0.4.3.2+git20200805+b220d04/analyzers/src/watch/nc_windows/header_window.h
Examining data/nfstrace-0.4.3.2+git20200805+b220d04/analyzers/src/watch/nc_windows/main_window.cpp
Examining data/nfstrace-0.4.3.2+git20200805+b220d04/analyzers/src/watch/nc_windows/main_window.h
Examining data/nfstrace-0.4.3.2+git20200805+b220d04/analyzers/src/watch/nc_windows/nc_window_const.h
Examining data/nfstrace-0.4.3.2+git20200805+b220d04/analyzers/src/watch/nc_windows/statistics_window.cpp
Examining data/nfstrace-0.4.3.2+git20200805+b220d04/analyzers/src/watch/nc_windows/statistics_window.h
Examining data/nfstrace-0.4.3.2+git20200805+b220d04/analyzers/src/watch/protocols/abstract_protocol.cpp
Examining data/nfstrace-0.4.3.2+git20200805+b220d04/analyzers/src/watch/protocols/abstract_protocol.h
Examining data/nfstrace-0.4.3.2+git20200805+b220d04/analyzers/src/watch/protocols/cifsv1_protocol.cpp
Examining data/nfstrace-0.4.3.2+git20200805+b220d04/analyzers/src/watch/protocols/cifsv1_protocol.h
Examining data/nfstrace-0.4.3.2+git20200805+b220d04/analyzers/src/watch/protocols/cifsv2_protocol.cpp
Examining data/nfstrace-0.4.3.2+git20200805+b220d04/analyzers/src/watch/protocols/cifsv2_protocol.h
Examining data/nfstrace-0.4.3.2+git20200805+b220d04/analyzers/src/watch/protocols/nfsv3_protocol.cpp
Examining data/nfstrace-0.4.3.2+git20200805+b220d04/analyzers/src/watch/protocols/nfsv3_protocol.h
Examining data/nfstrace-0.4.3.2+git20200805+b220d04/analyzers/src/watch/protocols/nfsv41_protocol.cpp
Examining data/nfstrace-0.4.3.2+git20200805+b220d04/analyzers/src/watch/protocols/nfsv41_protocol.h
Examining data/nfstrace-0.4.3.2+git20200805+b220d04/analyzers/src/watch/protocols/nfsv4_protocol.cpp
Examining data/nfstrace-0.4.3.2+git20200805+b220d04/analyzers/src/watch/protocols/nfsv4_protocol.h
Examining data/nfstrace-0.4.3.2+git20200805+b220d04/analyzers/src/watch/user_gui.cpp
Examining data/nfstrace-0.4.3.2+git20200805+b220d04/analyzers/src/watch/user_gui.h
Examining data/nfstrace-0.4.3.2+git20200805+b220d04/analyzers/src/watch/watch_analyzer.cpp
Examining data/nfstrace-0.4.3.2+git20200805+b220d04/analyzers/src/watch/watch_analyzer.h
Examining data/nfstrace-0.4.3.2+git20200805+b220d04/docs/template.cpp
Examining data/nfstrace-0.4.3.2+git20200805+b220d04/docs/template.h
Examining data/nfstrace-0.4.3.2+git20200805+b220d04/src/analysis/analysis_manager.cpp
Examining data/nfstrace-0.4.3.2+git20200805+b220d04/src/analysis/analysis_manager.h
Examining data/nfstrace-0.4.3.2+git20200805+b220d04/src/analysis/analyzers.cpp
Examining data/nfstrace-0.4.3.2+git20200805+b220d04/src/analysis/analyzers.h
Examining data/nfstrace-0.4.3.2+git20200805+b220d04/src/analysis/cifs_parser.cpp
Examining data/nfstrace-0.4.3.2+git20200805+b220d04/src/analysis/cifs_parser.h
Examining data/nfstrace-0.4.3.2+git20200805+b220d04/src/analysis/nfs_parser.cpp
Examining data/nfstrace-0.4.3.2+git20200805+b220d04/src/analysis/nfs_parser.h
Examining data/nfstrace-0.4.3.2+git20200805+b220d04/src/analysis/parser_thread.h
Examining data/nfstrace-0.4.3.2+git20200805+b220d04/src/analysis/parsers.h
Examining data/nfstrace-0.4.3.2+git20200805+b220d04/src/analysis/plugin.cpp
Examining data/nfstrace-0.4.3.2+git20200805+b220d04/src/analysis/plugin.h
Examining data/nfstrace-0.4.3.2+git20200805+b220d04/src/analysis/print_analyzer.cpp
Examining data/nfstrace-0.4.3.2+git20200805+b220d04/src/analysis/print_analyzer.h
Examining data/nfstrace-0.4.3.2+git20200805+b220d04/src/analysis/rpc_sessions.h
Examining data/nfstrace-0.4.3.2+git20200805+b220d04/src/api/cifs2_commands.h
Examining data/nfstrace-0.4.3.2+git20200805+b220d04/src/api/cifs_commands.h
Examining data/nfstrace-0.4.3.2+git20200805+b220d04/src/api/cifs_pc_to_net.h
Examining data/nfstrace-0.4.3.2+git20200805+b220d04/src/api/cifs_types.h
Examining data/nfstrace-0.4.3.2+git20200805+b220d04/src/api/ianalyzer.h
Examining data/nfstrace-0.4.3.2+git20200805+b220d04/src/api/nfs3_types_rpcgen.h
Examining data/nfstrace-0.4.3.2+git20200805+b220d04/src/api/nfs41_types_rpcgen.h
Examining data/nfstrace-0.4.3.2+git20200805+b220d04/src/api/nfs4_types_rpcgen.h
Examining data/nfstrace-0.4.3.2+git20200805+b220d04/src/api/nfs_types.h
Examining data/nfstrace-0.4.3.2+git20200805+b220d04/src/api/procedure.h
Examining data/nfstrace-0.4.3.2+git20200805+b220d04/src/api/rpc_types.h
Examining data/nfstrace-0.4.3.2+git20200805+b220d04/src/api/session.h
Examining data/nfstrace-0.4.3.2+git20200805+b220d04/src/api/xdr_types.h
Examining data/nfstrace-0.4.3.2+git20200805+b220d04/src/controller/cmdline_args.cpp
Examining data/nfstrace-0.4.3.2+git20200805+b220d04/src/controller/cmdline_args.h
Examining data/nfstrace-0.4.3.2+git20200805+b220d04/src/controller/cmdline_parser.h
Examining data/nfstrace-0.4.3.2+git20200805+b220d04/src/controller/controller.cpp
Examining data/nfstrace-0.4.3.2+git20200805+b220d04/src/controller/controller.h
Examining data/nfstrace-0.4.3.2+git20200805+b220d04/src/controller/parameters.cpp
Examining data/nfstrace-0.4.3.2+git20200805+b220d04/src/controller/parameters.h
Examining data/nfstrace-0.4.3.2+git20200805+b220d04/src/controller/running_status.h
Examining data/nfstrace-0.4.3.2+git20200805+b220d04/src/controller/signal_handler.cpp
Examining data/nfstrace-0.4.3.2+git20200805+b220d04/src/controller/signal_handler.h
Examining data/nfstrace-0.4.3.2+git20200805+b220d04/src/filtration/cifs_filtrator.h
Examining data/nfstrace-0.4.3.2+git20200805+b220d04/src/filtration/dumping.cpp
Examining data/nfstrace-0.4.3.2+git20200805+b220d04/src/filtration/dumping.h
Examining data/nfstrace-0.4.3.2+git20200805+b220d04/src/filtration/filtration_manager.cpp
Examining data/nfstrace-0.4.3.2+git20200805+b220d04/src/filtration/filtration_manager.h
Examining data/nfstrace-0.4.3.2+git20200805+b220d04/src/filtration/filtration_processor.h
Examining data/nfstrace-0.4.3.2+git20200805+b220d04/src/filtration/filtratorimpl.h
Examining data/nfstrace-0.4.3.2+git20200805+b220d04/src/filtration/filtrators.h
Examining data/nfstrace-0.4.3.2+git20200805+b220d04/src/filtration/packet.h
Examining data/nfstrace-0.4.3.2+git20200805+b220d04/src/filtration/pcap/base_reader.h
Examining data/nfstrace-0.4.3.2+git20200805+b220d04/src/filtration/pcap/bpf.h
Examining data/nfstrace-0.4.3.2+git20200805+b220d04/src/filtration/pcap/capture_reader.cpp
Examining data/nfstrace-0.4.3.2+git20200805+b220d04/src/filtration/pcap/capture_reader.h
Examining data/nfstrace-0.4.3.2+git20200805+b220d04/src/filtration/pcap/file_reader.cpp
Examining data/nfstrace-0.4.3.2+git20200805+b220d04/src/filtration/pcap/file_reader.h
Examining data/nfstrace-0.4.3.2+git20200805+b220d04/src/filtration/pcap/network_interfaces.h
Examining data/nfstrace-0.4.3.2+git20200805+b220d04/src/filtration/pcap/packet_dumper.h
Examining data/nfstrace-0.4.3.2+git20200805+b220d04/src/filtration/pcap/pcap_error.h
Examining data/nfstrace-0.4.3.2+git20200805+b220d04/src/filtration/processing_thread.h
Examining data/nfstrace-0.4.3.2+git20200805+b220d04/src/filtration/queuing.h
Examining data/nfstrace-0.4.3.2+git20200805+b220d04/src/filtration/rpc_filtrator.h
Examining data/nfstrace-0.4.3.2+git20200805+b220d04/src/filtration/sessions_hash.h
Examining data/nfstrace-0.4.3.2+git20200805+b220d04/src/main.cpp
Examining data/nfstrace-0.4.3.2+git20200805+b220d04/src/protocols/cifs/cifs.cpp
Examining data/nfstrace-0.4.3.2+git20200805+b220d04/src/protocols/cifs/cifs.h
Examining data/nfstrace-0.4.3.2+git20200805+b220d04/src/protocols/cifs2/cifs2.cpp
Examining data/nfstrace-0.4.3.2+git20200805+b220d04/src/protocols/cifs2/cifs2.h
Examining data/nfstrace-0.4.3.2+git20200805+b220d04/src/protocols/cifs2/cifs2_utils.cpp
Examining data/nfstrace-0.4.3.2+git20200805+b220d04/src/protocols/cifs2/cifs2_utils.h
Examining data/nfstrace-0.4.3.2+git20200805+b220d04/src/protocols/ethernet/ethernet_header.h
Examining data/nfstrace-0.4.3.2+git20200805+b220d04/src/protocols/ip/ip_header.h
Examining data/nfstrace-0.4.3.2+git20200805+b220d04/src/protocols/ip/ipv4_header.h
Examining data/nfstrace-0.4.3.2+git20200805+b220d04/src/protocols/ip/ipv6_header.h
Examining data/nfstrace-0.4.3.2+git20200805+b220d04/src/protocols/netbios/netbios.cpp
Examining data/nfstrace-0.4.3.2+git20200805+b220d04/src/protocols/netbios/netbios.h
Examining data/nfstrace-0.4.3.2+git20200805+b220d04/src/protocols/nfs/nfs_procedure.h
Examining data/nfstrace-0.4.3.2+git20200805+b220d04/src/protocols/nfs/nfs_utils.cpp
Examining data/nfstrace-0.4.3.2+git20200805+b220d04/src/protocols/nfs/nfs_utils.h
Examining data/nfstrace-0.4.3.2+git20200805+b220d04/src/protocols/nfs3/nfs3_utils.cpp
Examining data/nfstrace-0.4.3.2+git20200805+b220d04/src/protocols/nfs3/nfs3_utils.h
Examining data/nfstrace-0.4.3.2+git20200805+b220d04/src/protocols/nfs4/nfs41_utils.cpp
Examining data/nfstrace-0.4.3.2+git20200805+b220d04/src/protocols/nfs4/nfs41_utils.h
Examining data/nfstrace-0.4.3.2+git20200805+b220d04/src/protocols/nfs4/nfs4_utils.cpp
Examining data/nfstrace-0.4.3.2+git20200805+b220d04/src/protocols/nfs4/nfs4_utils.h
Examining data/nfstrace-0.4.3.2+git20200805+b220d04/src/protocols/rpc/rpc_header.h
Examining data/nfstrace-0.4.3.2+git20200805+b220d04/src/protocols/tcp/tcp_header.h
Examining data/nfstrace-0.4.3.2+git20200805+b220d04/src/protocols/udp/udp_header.h
Examining data/nfstrace-0.4.3.2+git20200805+b220d04/src/protocols/xdr/xdr_decoder.h
Examining data/nfstrace-0.4.3.2+git20200805+b220d04/src/utils/block_allocator.h
Examining data/nfstrace-0.4.3.2+git20200805+b220d04/src/utils/dynamic_load.cpp
Examining data/nfstrace-0.4.3.2+git20200805+b220d04/src/utils/dynamic_load.h
Examining data/nfstrace-0.4.3.2+git20200805+b220d04/src/utils/filtered_data.h
Examining data/nfstrace-0.4.3.2+git20200805+b220d04/src/utils/log.cpp
Examining data/nfstrace-0.4.3.2+git20200805+b220d04/src/utils/log.h
Examining data/nfstrace-0.4.3.2+git20200805+b220d04/src/utils/noncopyable.h
Examining data/nfstrace-0.4.3.2+git20200805+b220d04/src/utils/out.cpp
Examining data/nfstrace-0.4.3.2+git20200805+b220d04/src/utils/out.h
Examining data/nfstrace-0.4.3.2+git20200805+b220d04/src/utils/profiler.h
Examining data/nfstrace-0.4.3.2+git20200805+b220d04/src/utils/queue.h
Examining data/nfstrace-0.4.3.2+git20200805+b220d04/src/utils/sessions.cpp
Examining data/nfstrace-0.4.3.2+git20200805+b220d04/src/utils/sessions.h
Examining data/nfstrace-0.4.3.2+git20200805+b220d04/src/utils/spinlock.h
Examining data/nfstrace-0.4.3.2+git20200805+b220d04/tests/unit/analyzers/breakdown/breakdown.cpp
Examining data/nfstrace-0.4.3.2+git20200805+b220d04/tests/unit/analyzers/breakdown/latency.cpp
Examining data/nfstrace-0.4.3.2+git20200805+b220d04/tests/unit/analyzers/breakdown/statistic.cpp
Examining data/nfstrace-0.4.3.2+git20200805+b220d04/tests/unit/analyzers/cifs.cpp
Examining data/nfstrace-0.4.3.2+git20200805+b220d04/tests/unit/filtration/cifsv2.cpp
Examining data/nfstrace-0.4.3.2+git20200805+b220d04/tests/unit/filtration/stream.cpp
Examining data/nfstrace-0.4.3.2+git20200805+b220d04/tests/unit/protocols/cifsv2.cpp
Examining data/nfstrace-0.4.3.2+git20200805+b220d04/tests/unit/utils/block_allocator.cpp
Examining data/nfstrace-0.4.3.2+git20200805+b220d04/tests/unit/utils/filtered_data.cpp
FINAL RESULTS:
data/nfstrace-0.4.3.2+git20200805+b220d04/src/utils/log.cpp:63:5: [5] (race) chmod:
This accepts filename arguments; if an attacker can move those files, a
race condition results. (CWE-362). Use fchmod( ) instead.
chmod(file_name.c_str(), S_IRUSR | S_IWUSR | S_IRGRP | S_IWGRP | S_IROTH | S_IWOTH);
data/nfstrace-0.4.3.2+git20200805+b220d04/src/analysis/print_analyzer.cpp:925:34: [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.
print_access3(out, args->access);
data/nfstrace-0.4.3.2+git20200805+b220d04/src/analysis/print_analyzer.cpp:939:60: [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.
print_access3(out, res->ACCESS3res_u.resok.access);
data/nfstrace-0.4.3.2+git20200805+b220d04/src/analysis/print_analyzer.cpp:1832:19: [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((args->access) & NFS4::ACCESS4_READ) {
data/nfstrace-0.4.3.2+git20200805+b220d04/src/analysis/print_analyzer.cpp:1835:19: [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((args->access) & NFS4::ACCESS4_LOOKUP) {
data/nfstrace-0.4.3.2+git20200805+b220d04/src/analysis/print_analyzer.cpp:1838:19: [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((args->access) & NFS4::ACCESS4_MODIFY) {
data/nfstrace-0.4.3.2+git20200805+b220d04/src/analysis/print_analyzer.cpp:1841:19: [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((args->access) & NFS4::ACCESS4_EXTEND) {
data/nfstrace-0.4.3.2+git20200805+b220d04/src/analysis/print_analyzer.cpp:1844:19: [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((args->access) & NFS4::ACCESS4_DELETE) {
data/nfstrace-0.4.3.2+git20200805+b220d04/src/analysis/print_analyzer.cpp:1847:19: [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((args->access) & NFS4::ACCESS4_EXECUTE) {
data/nfstrace-0.4.3.2+git20200805+b220d04/src/analysis/print_analyzer.cpp:1886:42: [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((res->ACCESS4res_u.resok4.access) & NFS4::ACCESS4_READ)
data/nfstrace-0.4.3.2+git20200805+b220d04/src/analysis/print_analyzer.cpp:1890:42: [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((res->ACCESS4res_u.resok4.access) & NFS4::ACCESS4_LOOKUP)
data/nfstrace-0.4.3.2+git20200805+b220d04/src/analysis/print_analyzer.cpp:1894:42: [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((res->ACCESS4res_u.resok4.access) & NFS4::ACCESS4_MODIFY)
data/nfstrace-0.4.3.2+git20200805+b220d04/src/analysis/print_analyzer.cpp:1898:42: [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((res->ACCESS4res_u.resok4.access) & NFS4::ACCESS4_EXTEND)
data/nfstrace-0.4.3.2+git20200805+b220d04/src/analysis/print_analyzer.cpp:1902:42: [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((res->ACCESS4res_u.resok4.access) & NFS4::ACCESS4_DELETE)
data/nfstrace-0.4.3.2+git20200805+b220d04/src/analysis/print_analyzer.cpp:1906:42: [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((res->ACCESS4res_u.resok4.access) & NFS4::ACCESS4_EXECUTE)
data/nfstrace-0.4.3.2+git20200805+b220d04/src/analysis/print_analyzer.cpp:2934:19: [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((args->access) & NFS41::ACCESS4_READ) {
data/nfstrace-0.4.3.2+git20200805+b220d04/src/analysis/print_analyzer.cpp:2937:19: [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((args->access) & NFS41::ACCESS4_LOOKUP) {
data/nfstrace-0.4.3.2+git20200805+b220d04/src/analysis/print_analyzer.cpp:2940:19: [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((args->access) & NFS41::ACCESS4_MODIFY) {
data/nfstrace-0.4.3.2+git20200805+b220d04/src/analysis/print_analyzer.cpp:2943:19: [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((args->access) & NFS41::ACCESS4_EXTEND) {
data/nfstrace-0.4.3.2+git20200805+b220d04/src/analysis/print_analyzer.cpp:2946:19: [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((args->access) & NFS41::ACCESS4_DELETE) {
data/nfstrace-0.4.3.2+git20200805+b220d04/src/analysis/print_analyzer.cpp:2949:19: [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((args->access) & NFS41::ACCESS4_EXECUTE) {
data/nfstrace-0.4.3.2+git20200805+b220d04/src/analysis/print_analyzer.cpp:2988:42: [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((res->ACCESS4res_u.resok4.access) & NFS41::ACCESS4_READ)
data/nfstrace-0.4.3.2+git20200805+b220d04/src/analysis/print_analyzer.cpp:2992:42: [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((res->ACCESS4res_u.resok4.access) & NFS41::ACCESS4_LOOKUP)
data/nfstrace-0.4.3.2+git20200805+b220d04/src/analysis/print_analyzer.cpp:2996:42: [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((res->ACCESS4res_u.resok4.access) & NFS41::ACCESS4_MODIFY)
data/nfstrace-0.4.3.2+git20200805+b220d04/src/analysis/print_analyzer.cpp:3000:42: [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((res->ACCESS4res_u.resok4.access) & NFS41::ACCESS4_EXTEND)
data/nfstrace-0.4.3.2+git20200805+b220d04/src/analysis/print_analyzer.cpp:3004:42: [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((res->ACCESS4res_u.resok4.access) & NFS41::ACCESS4_DELETE)
data/nfstrace-0.4.3.2+git20200805+b220d04/src/analysis/print_analyzer.cpp:3008:42: [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((res->ACCESS4res_u.resok4.access) & NFS41::ACCESS4_EXECUTE)
data/nfstrace-0.4.3.2+git20200805+b220d04/src/api/nfs3_types_rpcgen.h:365:12: [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.
uint32 access;
data/nfstrace-0.4.3.2+git20200805+b220d04/src/api/nfs3_types_rpcgen.h:371:12: [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.
uint32 access;
data/nfstrace-0.4.3.2+git20200805+b220d04/src/api/nfs41_types_rpcgen.h:1126:14: [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.
uint32_t access;
data/nfstrace-0.4.3.2+git20200805+b220d04/src/api/nfs41_types_rpcgen.h:1132:14: [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.
uint32_t access;
data/nfstrace-0.4.3.2+git20200805+b220d04/src/api/nfs4_types_rpcgen.h:574:14: [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.
uint32_t access;
data/nfstrace-0.4.3.2+git20200805+b220d04/src/api/nfs4_types_rpcgen.h:580:14: [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.
uint32_t access;
data/nfstrace-0.4.3.2+git20200805+b220d04/src/controller/parameters.cpp:182:12: [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(access(path.c_str(), F_OK) != -1)
data/nfstrace-0.4.3.2+git20200805+b220d04/src/filtration/dumping.cpp:98:12: [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.
if(execvp(args[0], &args[0]) == -1)
data/nfstrace-0.4.3.2+git20200805+b220d04/src/protocols/nfs3/nfs3_utils.cpp:1291:35: [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 (!xdr_uint32 (xdrs, &objp->access))
data/nfstrace-0.4.3.2+git20200805+b220d04/src/protocols/nfs3/nfs3_utils.cpp:1306:35: [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 (!xdr_uint32 (xdrs, &objp->access))
data/nfstrace-0.4.3.2+git20200805+b220d04/src/protocols/nfs4/nfs41_utils.cpp:3829:37: [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 (!xdr_uint32_t (xdrs, &objp->access))
data/nfstrace-0.4.3.2+git20200805+b220d04/src/protocols/nfs4/nfs41_utils.cpp:3843:37: [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 (!xdr_uint32_t (xdrs, &objp->access))
data/nfstrace-0.4.3.2+git20200805+b220d04/src/protocols/nfs4/nfs4_utils.cpp:1850:37: [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 (!xdr_uint32_t (xdrs, &objp->access))
data/nfstrace-0.4.3.2+git20200805+b220d04/src/protocols/nfs4/nfs4_utils.cpp:1864:37: [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 (!xdr_uint32_t (xdrs, &objp->access))
data/nfstrace-0.4.3.2+git20200805+b220d04/src/utils/log.cpp:159:5: [4] (format) vfprintf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
vfprintf(log_file, format, args);
data/nfstrace-0.4.3.2+git20200805+b220d04/src/controller/cmdline_parser.h:191:19: [3] (buffer) getopt_long:
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.
int opt = getopt_long(argc, argv, short_opts, long_opts, &opt_index);
data/nfstrace-0.4.3.2+git20200805+b220d04/tests/unit/analyzers/breakdown/breakdown.cpp:48:14: [3] (random) srand:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
std::srand(std::time(0)); //use current time as seed for random generator
data/nfstrace-0.4.3.2+git20200805+b220d04/tests/unit/analyzers/breakdown/latency.cpp:55:14: [3] (random) srand:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
std::srand(std::time(0)); //use current time as seed for random generator
data/nfstrace-0.4.3.2+git20200805+b220d04/tests/unit/analyzers/breakdown/statistic.cpp:47:14: [3] (random) srand:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
std::srand(std::time(0)); //use current time as seed for random generator
data/nfstrace-0.4.3.2+git20200805+b220d04/analyzers/src/watch/nc_windows/header_window.cpp:96:9: [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 HOST_NAME[HEADER::HOST_SIZE];
data/nfstrace-0.4.3.2+git20200805+b220d04/src/api/nfs3_types_rpcgen.h:56:9: [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.
typedef char cookieverf3[NFS3_COOKIEVERFSIZE];
data/nfstrace-0.4.3.2+git20200805+b220d04/src/api/nfs3_types_rpcgen.h:58:9: [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.
typedef char createverf3[NFS3_CREATEVERFSIZE];
data/nfstrace-0.4.3.2+git20200805+b220d04/src/api/nfs3_types_rpcgen.h:60:9: [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.
typedef char writeverf3[NFS3_WRITEVERFSIZE];
data/nfstrace-0.4.3.2+git20200805+b220d04/src/api/nfs41_types_rpcgen.h:214:9: [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.
typedef char sessionid4[NFS4_SESSIONID_SIZE];
data/nfstrace-0.4.3.2+git20200805+b220d04/src/api/nfs41_types_rpcgen.h:238:9: [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.
typedef char verifier4[NFS4_VERIFIER_SIZE];
data/nfstrace-0.4.3.2+git20200805+b220d04/src/api/nfs41_types_rpcgen.h:406: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 other[12];
data/nfstrace-0.4.3.2+git20200805+b220d04/src/api/nfs41_types_rpcgen.h:460:9: [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.
typedef char deviceid4[NFS4_DEVICEID4_SIZE];
data/nfstrace-0.4.3.2+git20200805+b220d04/src/api/nfs4_types_rpcgen.h:185:9: [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.
typedef char verifier4[NFS4_VERIFIER_SIZE];
data/nfstrace-0.4.3.2+git20200805+b220d04/src/api/nfs4_types_rpcgen.h:514: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 other[12];
data/nfstrace-0.4.3.2+git20200805+b220d04/src/controller/cmdline_parser.h:63:47: [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).
int to_int() const { return atoi(value); }
data/nfstrace-0.4.3.2+git20200805+b220d04/src/controller/cmdline_parser.h:157: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 short_opts[CLI::num * 2 + 2] = {0};
data/nfstrace-0.4.3.2+git20200805+b220d04/src/filtration/dumping.h:81:13: [2] (buffer) memcpy:
Does not check for buffer overflows when copying to destination (CWE-120).
Make sure destination can always hold the source data.
memcpy(buff, payload, payload_len);
data/nfstrace-0.4.3.2+git20200805+b220d04/src/filtration/dumping.h:104:13: [2] (buffer) memcpy:
Does not check for buffer overflows when copying to destination (CWE-120).
Make sure destination can always hold the source data.
memcpy(payload + payload_len, info.data, len);
data/nfstrace-0.4.3.2+git20200805+b220d04/src/filtration/dumping.h:149:17: [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 suffix[64];
data/nfstrace-0.4.3.2+git20200805+b220d04/src/filtration/dumping.h:150:17: [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(suffix, "-%u", part);
data/nfstrace-0.4.3.2+git20200805+b220d04/src/filtration/filtratorimpl.h:97:17: [2] (buffer) memcpy:
Does not check for buffer overflows when copying to destination (CWE-120).
Make sure destination can always hold the source data.
memcpy(buffer, collection.data(), data_size);
data/nfstrace-0.4.3.2+git20200805+b220d04/src/filtration/filtratorimpl.h:98:17: [2] (buffer) memcpy:
Does not check for buffer overflows when copying to destination (CWE-120).
Make sure destination can always hold the source data.
memcpy(buffer + data_size, info.data, callHeaderLen - data_size);
data/nfstrace-0.4.3.2+git20200805+b220d04/src/filtration/packet.h:347:9: [2] (buffer) memcpy:
Does not check for buffer overflows when copying to destination (CWE-120).
Make sure destination can always hold the source data.
memcpy(packet, info.packet, info.header->caplen); // copy packet data
data/nfstrace-0.4.3.2+git20200805+b220d04/src/filtration/pcap/capture_reader.cpp:35: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[PCAP_ERRBUF_SIZE]; // storage of error description
data/nfstrace-0.4.3.2+git20200805+b220d04/src/filtration/pcap/file_reader.cpp:34: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[PCAP_ERRBUF_SIZE];
data/nfstrace-0.4.3.2+git20200805+b220d04/src/filtration/pcap/network_interfaces.h:109:9: [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[PCAP_ERRBUF_SIZE];
data/nfstrace-0.4.3.2+git20200805+b220d04/src/filtration/pcap/network_interfaces.h:176:13: [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 ip[INET_ADDRSTRLEN]{};
data/nfstrace-0.4.3.2+git20200805+b220d04/src/filtration/pcap/network_interfaces.h:177:13: [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 netmask[INET_ADDRSTRLEN]{};
data/nfstrace-0.4.3.2+git20200805+b220d04/src/filtration/pcap/network_interfaces.h:193:17: [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 broadaddr[INET_ADDRSTRLEN]{};
data/nfstrace-0.4.3.2+git20200805+b220d04/src/filtration/pcap/network_interfaces.h:204:17: [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 destaddr[INET_ADDRSTRLEN]{};
data/nfstrace-0.4.3.2+git20200805+b220d04/src/filtration/pcap/network_interfaces.h:215:13: [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 ip6[INET6_ADDRSTRLEN]{};
data/nfstrace-0.4.3.2+git20200805+b220d04/src/filtration/pcap/network_interfaces.h:216:13: [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 netmask6[INET6_ADDRSTRLEN]{};
data/nfstrace-0.4.3.2+git20200805+b220d04/src/filtration/queuing.h:105:13: [2] (buffer) memcpy:
Does not check for buffer overflows when copying to destination (CWE-120).
Make sure destination can always hold the source data.
memcpy(offset_ptr, info.data, len);
data/nfstrace-0.4.3.2+git20200805+b220d04/src/filtration/sessions_hash.h:111:9: [2] (buffer) memcpy:
Does not check for buffer overflows when copying to destination (CWE-120).
Make sure destination can always hold the source data.
memcpy(d, src, sizeof(uint32_t) * 4);
data/nfstrace-0.4.3.2+git20200805+b220d04/src/utils/filtered_data.h:88:17: [2] (buffer) memcpy:
Does not check for buffer overflows when copying to destination (CWE-120).
Make sure destination can always hold the source data.
memcpy(memory, cache, dlen);
data/nfstrace-0.4.3.2+git20200805+b220d04/src/utils/filtered_data.h:98:17: [2] (buffer) memcpy:
Does not check for buffer overflows when copying to destination (CWE-120).
Make sure destination can always hold the source data.
memcpy(mem, memory, dlen);
data/nfstrace-0.4.3.2+git20200805+b220d04/src/utils/log.cpp:58:18: [2] (misc) fopen:
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* file = fopen(file_name.c_str(), "a+");
data/nfstrace-0.4.3.2+git20200805+b220d04/src/utils/log.h:86: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 buffer[256];
data/nfstrace-0.4.3.2+git20200805+b220d04/src/utils/sessions.cpp:82: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 buf[INET_ADDRSTRLEN];
data/nfstrace-0.4.3.2+git20200805+b220d04/src/utils/sessions.cpp:92: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 buf[INET6_ADDRSTRLEN];
data/nfstrace-0.4.3.2+git20200805+b220d04/src/utils/sessions.cpp:103: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 hostname[1025];
data/nfstrace-0.4.3.2+git20200805+b220d04/src/utils/sessions.cpp:104: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 service[65];
data/nfstrace-0.4.3.2+git20200805+b220d04/analyzers/src/json/json_plugin.cpp:75:33: [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).
std::size_t optsLen = strlen(opts);
data/nfstrace-0.4.3.2+git20200805+b220d04/src/analysis/print_analyzer.cpp:187: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).
size_t len = std::strlen(pTime);
data/nfstrace-0.4.3.2+git20200805+b220d04/src/api/nfs41_types_rpcgen.h:1550:31: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
open_read_delegation4 read;
data/nfstrace-0.4.3.2+git20200805+b220d04/src/api/nfs4_types_rpcgen.h:998:31: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
open_read_delegation4 read;
data/nfstrace-0.4.3.2+git20200805+b220d04/src/protocols/nfs4/nfs41_utils.cpp:1216:55: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
return out << ": " << obj.open_delegation4_u.read;
data/nfstrace-0.4.3.2+git20200805+b220d04/src/protocols/nfs4/nfs41_utils.cpp:4821:73: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
if (!xdr_open_read_delegation4 (xdrs, &objp->open_delegation4_u.read))
data/nfstrace-0.4.3.2+git20200805+b220d04/src/protocols/nfs4/nfs4_utils.cpp:700:55: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
return out << ": " << obj.open_delegation4_u.read;
data/nfstrace-0.4.3.2+git20200805+b220d04/src/protocols/nfs4/nfs4_utils.cpp:2874:73: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
if (!xdr_open_read_delegation4 (xdrs, &objp->open_delegation4_u.read))
ANALYSIS SUMMARY:
Hits = 92
Lines analyzed = 55718 in approximately 1.22 seconds (45766 lines/second)
Physical Source Lines of Code (SLOC) = 43621
Hits@level = [0] 4 [1] 8 [2] 38 [3] 4 [4] 41 [5] 1
Hits@level+ = [0+] 96 [1+] 92 [2+] 84 [3+] 46 [4+] 42 [5+] 1
Hits/KSLOC@level+ = [0+] 2.20077 [1+] 2.10908 [2+] 1.92568 [3+] 1.05454 [4+] 0.962839 [5+] 0.0229247
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.