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/systemtap-4.4/bpf-base.cxx
Examining data/systemtap-4.4/bpf-bitset.cxx
Examining data/systemtap-4.4/bpf-bitset.h
Examining data/systemtap-4.4/bpf-internal.h
Examining data/systemtap-4.4/bpf-opt.cxx
Examining data/systemtap-4.4/bpf-shared-globals.h
Examining data/systemtap-4.4/bpf-translate.cxx
Examining data/systemtap-4.4/bpf.h
Examining data/systemtap-4.4/buildrun.cxx
Examining data/systemtap-4.4/buildrun.h
Examining data/systemtap-4.4/cache.cxx
Examining data/systemtap-4.4/cache.h
Examining data/systemtap-4.4/client-http.cxx
Examining data/systemtap-4.4/client-http.h
Examining data/systemtap-4.4/client-nss.cxx
Examining data/systemtap-4.4/client-nss.h
Examining data/systemtap-4.4/cmdline.cxx
Examining data/systemtap-4.4/cmdline.h
Examining data/systemtap-4.4/coveragedb.cxx
Examining data/systemtap-4.4/coveragedb.h
Examining data/systemtap-4.4/csclient.cxx
Examining data/systemtap-4.4/csclient.h
Examining data/systemtap-4.4/cscommon.cxx
Examining data/systemtap-4.4/cscommon.h
Examining data/systemtap-4.4/doc/SystemTap_Tapset_Reference/docproc.c
Examining data/systemtap-4.4/dwarf_wrappers.cxx
Examining data/systemtap-4.4/dwarf_wrappers.h
Examining data/systemtap-4.4/dwflpp.cxx
Examining data/systemtap-4.4/dwflpp.h
Examining data/systemtap-4.4/elaborate.cxx
Examining data/systemtap-4.4/elaborate.h
Examining data/systemtap-4.4/hash.cxx
Examining data/systemtap-4.4/hash.h
Examining data/systemtap-4.4/httpd/api.cxx
Examining data/systemtap-4.4/httpd/api.h
Examining data/systemtap-4.4/httpd/backends.cxx
Examining data/systemtap-4.4/httpd/backends.h
Examining data/systemtap-4.4/httpd/main.cxx
Examining data/systemtap-4.4/httpd/nss_funcs.cxx
Examining data/systemtap-4.4/httpd/nss_funcs.h
Examining data/systemtap-4.4/httpd/server.cxx
Examining data/systemtap-4.4/httpd/server.h
Examining data/systemtap-4.4/httpd/utils.cxx
Examining data/systemtap-4.4/httpd/utils.h
Examining data/systemtap-4.4/includes/stap-probe.h
Examining data/systemtap-4.4/includes/sys/sdt.h
Examining data/systemtap-4.4/interactive.cxx
Examining data/systemtap-4.4/interactive.h
Examining data/systemtap-4.4/java/HelperSDT.c
Examining data/systemtap-4.4/java/HelperSDT.h
Examining data/systemtap-4.4/loc2stap.cxx
Examining data/systemtap-4.4/loc2stap.h
Examining data/systemtap-4.4/mdfour.c
Examining data/systemtap-4.4/mdfour.h
Examining data/systemtap-4.4/nss-server-info.cxx
Examining data/systemtap-4.4/nss-server-info.h
Examining data/systemtap-4.4/nsscommon.cxx
Examining data/systemtap-4.4/nsscommon.h
Examining data/systemtap-4.4/parse.cxx
Examining data/systemtap-4.4/parse.h
Examining data/systemtap-4.4/privilege.cxx
Examining data/systemtap-4.4/privilege.h
Examining data/systemtap-4.4/python/HelperSDT/_HelperSDT.c
Examining data/systemtap-4.4/remote.cxx
Examining data/systemtap-4.4/remote.h
Examining data/systemtap-4.4/rpm_finder.cxx
Examining data/systemtap-4.4/rpm_finder.h
Examining data/systemtap-4.4/runtime/addr-map.c
Examining data/systemtap-4.4/runtime/addr-map.h
Examining data/systemtap-4.4/runtime/alloc.c
Examining data/systemtap-4.4/runtime/arith.c
Examining data/systemtap-4.4/runtime/common_probe_context.h
Examining data/systemtap-4.4/runtime/common_session_state.h
Examining data/systemtap-4.4/runtime/compatdefs.h
Examining data/systemtap-4.4/runtime/copy.c
Examining data/systemtap-4.4/runtime/debug.h
Examining data/systemtap-4.4/runtime/docs/examples/argv.c
Examining data/systemtap-4.4/runtime/docs/examples/foreach.c
Examining data/systemtap-4.4/runtime/docs/examples/list.c
Examining data/systemtap-4.4/runtime/docs/examples/map.c
Examining data/systemtap-4.4/runtime/docs/examples/template.c
Examining data/systemtap-4.4/runtime/dyninst/addr-map.c
Examining data/systemtap-4.4/runtime/dyninst/alloc.c
Examining data/systemtap-4.4/runtime/dyninst/arith.c
Examining data/systemtap-4.4/runtime/dyninst/common_session_state.h
Examining data/systemtap-4.4/runtime/dyninst/copy.c
Examining data/systemtap-4.4/runtime/dyninst/debug.h
Examining data/systemtap-4.4/runtime/dyninst/ilog2.h
Examining data/systemtap-4.4/runtime/dyninst/io.c
Examining data/systemtap-4.4/runtime/dyninst/linux_defs.h
Examining data/systemtap-4.4/runtime/dyninst/linux_hash.h
Examining data/systemtap-4.4/runtime/dyninst/linux_types.h
Examining data/systemtap-4.4/runtime/dyninst/loc2c-runtime.h
Examining data/systemtap-4.4/runtime/dyninst/map_list.h
Examining data/systemtap-4.4/runtime/dyninst/map_runtime.h
Examining data/systemtap-4.4/runtime/dyninst/namespaces.h
Examining data/systemtap-4.4/runtime/dyninst/offptr.h
Examining data/systemtap-4.4/runtime/dyninst/offset_list.h
Examining data/systemtap-4.4/runtime/dyninst/perf.c
Examining data/systemtap-4.4/runtime/dyninst/print.c
Examining data/systemtap-4.4/runtime/dyninst/probe_lock.h
Examining data/systemtap-4.4/runtime/dyninst/regs.c
Examining data/systemtap-4.4/runtime/dyninst/runtime.h
Examining data/systemtap-4.4/runtime/dyninst/runtime_context.h
Examining data/systemtap-4.4/runtime/dyninst/runtime_defines.h
Examining data/systemtap-4.4/runtime/dyninst/session_attributes.c
Examining data/systemtap-4.4/runtime/dyninst/session_attributes.h
Examining data/systemtap-4.4/runtime/dyninst/shm.c
Examining data/systemtap-4.4/runtime/dyninst/stapdyn.h
Examining data/systemtap-4.4/runtime/dyninst/stat_runtime.h
Examining data/systemtap-4.4/runtime/dyninst/sym.c
Examining data/systemtap-4.4/runtime/dyninst/task_finder.c
Examining data/systemtap-4.4/runtime/dyninst/timer.c
Examining data/systemtap-4.4/runtime/dyninst/transport.c
Examining data/systemtap-4.4/runtime/dyninst/transport.h
Examining data/systemtap-4.4/runtime/dyninst/unwind.c
Examining data/systemtap-4.4/runtime/dyninst/uprobes-regs.c
Examining data/systemtap-4.4/runtime/dyninst/uprobes.c
Examining data/systemtap-4.4/runtime/dyninst/uprobes.h
Examining data/systemtap-4.4/runtime/io.c
Examining data/systemtap-4.4/runtime/k_syms.h
Examining data/systemtap-4.4/runtime/linux/access_process_vm.h
Examining data/systemtap-4.4/runtime/linux/addr-map.c
Examining data/systemtap-4.4/runtime/linux/alloc.c
Examining data/systemtap-4.4/runtime/linux/arith.c
Examining data/systemtap-4.4/runtime/linux/autoconf-access_ok_2args.c
Examining data/systemtap-4.4/runtime/linux/autoconf-alloc-percpu-align.c
Examining data/systemtap-4.4/runtime/linux/autoconf-asm-syscall.c
Examining data/systemtap-4.4/runtime/linux/autoconf-atomic_fetch_add_unless.c
Examining data/systemtap-4.4/runtime/linux/autoconf-bio-bi_opf.c
Examining data/systemtap-4.4/runtime/linux/autoconf-blk-types.c
Examining data/systemtap-4.4/runtime/linux/autoconf-compat-utimbuf.c
Examining data/systemtap-4.4/runtime/linux/autoconf-compat_sigaction.c
Examining data/systemtap-4.4/runtime/linux/autoconf-constant-tsc.c
Examining data/systemtap-4.4/runtime/linux/autoconf-cpu-clock.c
Examining data/systemtap-4.4/runtime/linux/autoconf-dpath-path.c
Examining data/systemtap-4.4/runtime/linux/autoconf-from_kuid_munged.c
Examining data/systemtap-4.4/runtime/linux/autoconf-fs_supers-hlist.c
Examining data/systemtap-4.4/runtime/linux/autoconf-generated-compile.c
Examining data/systemtap-4.4/runtime/linux/autoconf-get_user_pages-flags.c
Examining data/systemtap-4.4/runtime/linux/autoconf-get_user_pages-notask_struct.c
Examining data/systemtap-4.4/runtime/linux/autoconf-get_user_pages_remote-flags.c
Examining data/systemtap-4.4/runtime/linux/autoconf-get_user_pages_remote-flags_locked.c
Examining data/systemtap-4.4/runtime/linux/autoconf-get_user_pages_remote-notask_struct.c
Examining data/systemtap-4.4/runtime/linux/autoconf-grsecurity.c
Examining data/systemtap-4.4/runtime/linux/autoconf-hlist-4args.c
Examining data/systemtap-4.4/runtime/linux/autoconf-hrtimer-getset-expires.c
Examining data/systemtap-4.4/runtime/linux/autoconf-hrtimer-rel.c
Examining data/systemtap-4.4/runtime/linux/autoconf-hw_breakpoint_context.c
Examining data/systemtap-4.4/runtime/linux/autoconf-inode-private.c
Examining data/systemtap-4.4/runtime/linux/autoconf-inode-rwsem.c
Examining data/systemtap-4.4/runtime/linux/autoconf-inode-uretprobes.c
Examining data/systemtap-4.4/runtime/linux/autoconf-kernel_read_file_from_path-offset.c
Examining data/systemtap-4.4/runtime/linux/autoconf-kprobe-symbol-name.c
Examining data/systemtap-4.4/runtime/linux/autoconf-ktime-get-real.c
Examining data/systemtap-4.4/runtime/linux/autoconf-linux-sched_headers.c
Examining data/systemtap-4.4/runtime/linux/autoconf-local-clock.c
Examining data/systemtap-4.4/runtime/linux/autoconf-lockdown-debugfs.c
Examining data/systemtap-4.4/runtime/linux/autoconf-mm-context-vdso-base.c
Examining data/systemtap-4.4/runtime/linux/autoconf-mm-context-vdso.c
Examining data/systemtap-4.4/runtime/linux/autoconf-mm-shmempages.c
Examining data/systemtap-4.4/runtime/linux/autoconf-mmap_lock.c
Examining data/systemtap-4.4/runtime/linux/autoconf-mod_kallsyms.c
Examining data/systemtap-4.4/runtime/linux/autoconf-module-sect-attrs.c
Examining data/systemtap-4.4/runtime/linux/autoconf-module_layout.c
Examining data/systemtap-4.4/runtime/linux/autoconf-nameidata.c
Examining data/systemtap-4.4/runtime/linux/autoconf-netfilter-313b.c
Examining data/systemtap-4.4/runtime/linux/autoconf-netfilter-4_1.c
Examining data/systemtap-4.4/runtime/linux/autoconf-netfilter-4_4.c
Examining data/systemtap-4.4/runtime/linux/autoconf-netfilter.c
Examining data/systemtap-4.4/runtime/linux/autoconf-old-inode-uprobes.c
Examining data/systemtap-4.4/runtime/linux/autoconf-oneachcpu-retry.c
Examining data/systemtap-4.4/runtime/linux/autoconf-pagefault_disable.c
Examining data/systemtap-4.4/runtime/linux/autoconf-perf-structpid.c
Examining data/systemtap-4.4/runtime/linux/autoconf-proc_ops.c
Examining data/systemtap-4.4/runtime/linux/autoconf-procfs-owner.c
Examining data/systemtap-4.4/runtime/linux/autoconf-rcu_is_watching.c
Examining data/systemtap-4.4/runtime/linux/autoconf-real-parent.c
Examining data/systemtap-4.4/runtime/linux/autoconf-regset.c
Examining data/systemtap-4.4/runtime/linux/autoconf-relay-umode_t.c
Examining data/systemtap-4.4/runtime/linux/autoconf-relay_buf-per_cpu_ptr.c
Examining data/systemtap-4.4/runtime/linux/autoconf-ring_buffer-flags.c
Examining data/systemtap-4.4/runtime/linux/autoconf-ring_buffer_lost_events.c
Examining data/systemtap-4.4/runtime/linux/autoconf-ring_buffer_read_prepare.c
Examining data/systemtap-4.4/runtime/linux/autoconf-save-stack-trace-no-bp.c
Examining data/systemtap-4.4/runtime/linux/autoconf-save-stack-trace.c
Examining data/systemtap-4.4/runtime/linux/autoconf-set_fs.c
Examining data/systemtap-4.4/runtime/linux/autoconf-smpcall-4args.c
Examining data/systemtap-4.4/runtime/linux/autoconf-smpcall-5args.c
Examining data/systemtap-4.4/runtime/linux/autoconf-stack-trace-save-regs.c
Examining data/systemtap-4.4/runtime/linux/autoconf-stacktrace_ops-int-address.c
Examining data/systemtap-4.4/runtime/linux/autoconf-stacktrace_ops-warning.c
Examining data/systemtap-4.4/runtime/linux/autoconf-syscall_get_args_3args.c
Examining data/systemtap-4.4/runtime/linux/autoconf-task-uid.c
Examining data/systemtap-4.4/runtime/linux/autoconf-task_work-struct.c
Examining data/systemtap-4.4/runtime/linux/autoconf-time32-old.c
Examining data/systemtap-4.4/runtime/linux/autoconf-time32.c
Examining data/systemtap-4.4/runtime/linux/autoconf-timerfd.c
Examining data/systemtap-4.4/runtime/linux/autoconf-trace-printk.c
Examining data/systemtap-4.4/runtime/linux/autoconf-tracepoint-has-data.c
Examining data/systemtap-4.4/runtime/linux/autoconf-tracepoint-strings.c
Examining data/systemtap-4.4/runtime/linux/autoconf-uaccess.c
Examining data/systemtap-4.4/runtime/linux/autoconf-uapi-mount.c
Examining data/systemtap-4.4/runtime/linux/autoconf-udelay_simple.c
Examining data/systemtap-4.4/runtime/linux/autoconf-uidgid.c
Examining data/systemtap-4.4/runtime/linux/autoconf-unwind-stack-trace.c
Examining data/systemtap-4.4/runtime/linux/autoconf-uprobe-get-pc.c
Examining data/systemtap-4.4/runtime/linux/autoconf-utrace-regset.c
Examining data/systemtap-4.4/runtime/linux/autoconf-utrace-via-tracepoints.c
Examining data/systemtap-4.4/runtime/linux/autoconf-vm-area-pte.c
Examining data/systemtap-4.4/runtime/linux/autoconf-walk-stack.c
Examining data/systemtap-4.4/runtime/linux/autoconf-x86-fs.c
Examining data/systemtap-4.4/runtime/linux/autoconf-x86-gs.c
Examining data/systemtap-4.4/runtime/linux/autoconf-x86-uniregs.c
Examining data/systemtap-4.4/runtime/linux/autoconf-x86-xfs.c
Examining data/systemtap-4.4/runtime/linux/common_session_state.h
Examining data/systemtap-4.4/runtime/linux/compat_net.h
Examining data/systemtap-4.4/runtime/linux/compat_structs.h
Examining data/systemtap-4.4/runtime/linux/compat_unistd.h
Examining data/systemtap-4.4/runtime/linux/copy.c
Examining data/systemtap-4.4/runtime/linux/debug.h
Examining data/systemtap-4.4/runtime/linux/io.c
Examining data/systemtap-4.4/runtime/linux/itrace.c
Examining data/systemtap-4.4/runtime/linux/kprobes.c
Examining data/systemtap-4.4/runtime/linux/loc2c-runtime.h
Examining data/systemtap-4.4/runtime/linux/map_list.h
Examining data/systemtap-4.4/runtime/linux/map_runtime.h
Examining data/systemtap-4.4/runtime/linux/namespaces.h
Examining data/systemtap-4.4/runtime/linux/netfilter.c
Examining data/systemtap-4.4/runtime/linux/perf.c
Examining data/systemtap-4.4/runtime/linux/perf.h
Examining data/systemtap-4.4/runtime/linux/perf_event_counter_context.c
Examining data/systemtap-4.4/runtime/linux/perf_probe_handler_nmi.c
Examining data/systemtap-4.4/runtime/linux/perf_read.h
Examining data/systemtap-4.4/runtime/linux/print.c
Examining data/systemtap-4.4/runtime/linux/probe_lock.h
Examining data/systemtap-4.4/runtime/linux/regs-ia64.c
Examining data/systemtap-4.4/runtime/linux/regs.c
Examining data/systemtap-4.4/runtime/linux/runtime.h
Examining data/systemtap-4.4/runtime/linux/runtime_context.h
Examining data/systemtap-4.4/runtime/linux/runtime_defines.h
Examining data/systemtap-4.4/runtime/linux/stap_mmap_lock.h
Examining data/systemtap-4.4/runtime/linux/stat_runtime.h
Examining data/systemtap-4.4/runtime/linux/stp_tls.h
Examining data/systemtap-4.4/runtime/linux/stp_tracepoint.c
Examining data/systemtap-4.4/runtime/linux/stp_tracepoint.h
Examining data/systemtap-4.4/runtime/linux/syscalls-common.h
Examining data/systemtap-4.4/runtime/linux/task_finder.c
Examining data/systemtap-4.4/runtime/linux/task_finder2.c
Examining data/systemtap-4.4/runtime/linux/task_finder_map.c
Examining data/systemtap-4.4/runtime/linux/task_finder_stubs.c
Examining data/systemtap-4.4/runtime/linux/task_work_compatibility.h
Examining data/systemtap-4.4/runtime/linux/timer.c
Examining data/systemtap-4.4/runtime/linux/timer.h
Examining data/systemtap-4.4/runtime/linux/timer_compatibility.h
Examining data/systemtap-4.4/runtime/linux/uprobes-common.c
Examining data/systemtap-4.4/runtime/linux/uprobes-common.h
Examining data/systemtap-4.4/runtime/linux/uprobes-inc.h
Examining data/systemtap-4.4/runtime/linux/uprobes-inode.c
Examining data/systemtap-4.4/runtime/linux/uprobes/uprobes.c
Examining data/systemtap-4.4/runtime/linux/uprobes/uprobes.h
Examining data/systemtap-4.4/runtime/linux/uprobes/uprobes_arch.c
Examining data/systemtap-4.4/runtime/linux/uprobes/uprobes_arch.h
Examining data/systemtap-4.4/runtime/linux/uprobes/uprobes_i386.c
Examining data/systemtap-4.4/runtime/linux/uprobes/uprobes_i386.h
Examining data/systemtap-4.4/runtime/linux/uprobes/uprobes_ppc.c
Examining data/systemtap-4.4/runtime/linux/uprobes/uprobes_ppc.h
Examining data/systemtap-4.4/runtime/linux/uprobes/uprobes_s390.c
Examining data/systemtap-4.4/runtime/linux/uprobes/uprobes_s390.h
Examining data/systemtap-4.4/runtime/linux/uprobes/uprobes_x86.c
Examining data/systemtap-4.4/runtime/linux/uprobes/uprobes_x86.h
Examining data/systemtap-4.4/runtime/linux/uprobes/uprobes_x86_64.c
Examining data/systemtap-4.4/runtime/linux/uprobes/uprobes_x86_64.h
Examining data/systemtap-4.4/runtime/linux/uprobes2/uprobes.c
Examining data/systemtap-4.4/runtime/linux/uprobes2/uprobes.h
Examining data/systemtap-4.4/runtime/linux/uprobes2/uprobes_arch.c
Examining data/systemtap-4.4/runtime/linux/uprobes2/uprobes_arch.h
Examining data/systemtap-4.4/runtime/linux/uprobes2/uprobes_arm.c
Examining data/systemtap-4.4/runtime/linux/uprobes2/uprobes_arm.h
Examining data/systemtap-4.4/runtime/linux/uprobes2/uprobes_x86.c
Examining data/systemtap-4.4/runtime/linux/uprobes2/uprobes_x86.h
Examining data/systemtap-4.4/runtime/loc2c-runtime.h
Examining data/systemtap-4.4/runtime/map-gen.c
Examining data/systemtap-4.4/runtime/map-stat.c
Examining data/systemtap-4.4/runtime/map.c
Examining data/systemtap-4.4/runtime/map.h
Examining data/systemtap-4.4/runtime/mempool.c
Examining data/systemtap-4.4/runtime/namespaces.h
Examining data/systemtap-4.4/runtime/pmap-gen.c
Examining data/systemtap-4.4/runtime/print.c
Examining data/systemtap-4.4/runtime/print.h
Examining data/systemtap-4.4/runtime/print_flush.c
Examining data/systemtap-4.4/runtime/probe_lock.h
Examining data/systemtap-4.4/runtime/proc_fs_compatibility.h
Examining data/systemtap-4.4/runtime/procfs-probes.c
Examining data/systemtap-4.4/runtime/procfs-probes.h
Examining data/systemtap-4.4/runtime/procfs.c
Examining data/systemtap-4.4/runtime/ptrace_compatibility.h
Examining data/systemtap-4.4/runtime/regs.c
Examining data/systemtap-4.4/runtime/regs.h
Examining data/systemtap-4.4/runtime/runtime.h
Examining data/systemtap-4.4/runtime/runtime_context.h
Examining data/systemtap-4.4/runtime/runtime_defines.h
Examining data/systemtap-4.4/runtime/softfloat.c
Examining data/systemtap-4.4/runtime/softfloat.h
Examining data/systemtap-4.4/runtime/softfloat/internals.h
Examining data/systemtap-4.4/runtime/softfloat/opt-GCC.h
Examining data/systemtap-4.4/runtime/softfloat/platform.h
Examining data/systemtap-4.4/runtime/softfloat/primitiveTypes.h
Examining data/systemtap-4.4/runtime/softfloat/primitives.h
Examining data/systemtap-4.4/runtime/softfloat/softfloat_types.h
Examining data/systemtap-4.4/runtime/softfloat/specialize.h
Examining data/systemtap-4.4/runtime/stack-arm.c
Examining data/systemtap-4.4/runtime/stack-ia64.c
Examining data/systemtap-4.4/runtime/stack-mips.c
Examining data/systemtap-4.4/runtime/stack-s390.c
Examining data/systemtap-4.4/runtime/stack.c
Examining data/systemtap-4.4/runtime/stat-common.c
Examining data/systemtap-4.4/runtime/stat.c
Examining data/systemtap-4.4/runtime/stat.h
Examining data/systemtap-4.4/runtime/stp_helper_lock.h
Examining data/systemtap-4.4/runtime/stp_string.c
Examining data/systemtap-4.4/runtime/stp_string.h
Examining data/systemtap-4.4/runtime/stp_task_work.c
Examining data/systemtap-4.4/runtime/stp_utrace.c
Examining data/systemtap-4.4/runtime/stp_utrace.h
Examining data/systemtap-4.4/runtime/sym.c
Examining data/systemtap-4.4/runtime/sym.h
Examining data/systemtap-4.4/runtime/syscall.h
Examining data/systemtap-4.4/runtime/task_finder_vma.c
Examining data/systemtap-4.4/runtime/time.c
Examining data/systemtap-4.4/runtime/timer.c
Examining data/systemtap-4.4/runtime/timer.h
Examining data/systemtap-4.4/runtime/transport/control.c
Examining data/systemtap-4.4/runtime/transport/control.h
Examining data/systemtap-4.4/runtime/transport/debugfs.c
Examining data/systemtap-4.4/runtime/transport/procfs.c
Examining data/systemtap-4.4/runtime/transport/relay_compat.h
Examining data/systemtap-4.4/runtime/transport/relay_v2.c
Examining data/systemtap-4.4/runtime/transport/symbols.c
Examining data/systemtap-4.4/runtime/transport/transport.c
Examining data/systemtap-4.4/runtime/transport/transport.h
Examining data/systemtap-4.4/runtime/transport/transport_msgs.h
Examining data/systemtap-4.4/runtime/uidgid_compatibility.h
Examining data/systemtap-4.4/runtime/unwind.c
Examining data/systemtap-4.4/runtime/unwind/arm.h
Examining data/systemtap-4.4/runtime/unwind/arm64.h
Examining data/systemtap-4.4/runtime/unwind/i386.h
Examining data/systemtap-4.4/runtime/unwind/mips.h
Examining data/systemtap-4.4/runtime/unwind/ppc64.h
Examining data/systemtap-4.4/runtime/unwind/s390x.h
Examining data/systemtap-4.4/runtime/unwind/unwind.h
Examining data/systemtap-4.4/runtime/unwind/x86_64.h
Examining data/systemtap-4.4/runtime/utrace_compatibility.h
Examining data/systemtap-4.4/runtime/vma.c
Examining data/systemtap-4.4/runtime/vsprintf.c
Examining data/systemtap-4.4/runtime/vsprintf.h
Examining data/systemtap-4.4/scripts/kprobes_test/kprobe_module.c
Examining data/systemtap-4.4/scripts/probe_perf/bench.c
Examining data/systemtap-4.4/sdt_types.h
Examining data/systemtap-4.4/session.cxx
Examining data/systemtap-4.4/session.h
Examining data/systemtap-4.4/setupdwfl.cxx
Examining data/systemtap-4.4/setupdwfl.h
Examining data/systemtap-4.4/stap-authorize-cert.cxx
Examining data/systemtap-4.4/stap-gen-cert.cxx
Examining data/systemtap-4.4/stap-serverd.cxx
Examining data/systemtap-4.4/stap-sign-module.cxx
Examining data/systemtap-4.4/stapbpf/bpfinterp.cxx
Examining data/systemtap-4.4/stapbpf/bpfinterp.h
Examining data/systemtap-4.4/stapbpf/libbpf.c
Examining data/systemtap-4.4/stapbpf/libbpf.h
Examining data/systemtap-4.4/stapbpf/stapbpf.cxx
Examining data/systemtap-4.4/stapdyn/dynprobe.cxx
Examining data/systemtap-4.4/stapdyn/dynprobe.h
Examining data/systemtap-4.4/stapdyn/dynsdt.cxx
Examining data/systemtap-4.4/stapdyn/dynutil.cxx
Examining data/systemtap-4.4/stapdyn/dynutil.h
Examining data/systemtap-4.4/stapdyn/mutatee.cxx
Examining data/systemtap-4.4/stapdyn/mutatee.h
Examining data/systemtap-4.4/stapdyn/mutator.cxx
Examining data/systemtap-4.4/stapdyn/mutator.h
Examining data/systemtap-4.4/stapdyn/stapdyn.cxx
Examining data/systemtap-4.4/staplog.c
Examining data/systemtap-4.4/stapregex-defines.h
Examining data/systemtap-4.4/stapregex-dfa.cxx
Examining data/systemtap-4.4/stapregex-dfa.h
Examining data/systemtap-4.4/stapregex-parse.cxx
Examining data/systemtap-4.4/stapregex-parse.h
Examining data/systemtap-4.4/stapregex-tree.cxx
Examining data/systemtap-4.4/stapregex-tree.h
Examining data/systemtap-4.4/stapregex.cxx
Examining data/systemtap-4.4/stapregex.h
Examining data/systemtap-4.4/staprun/common.c
Examining data/systemtap-4.4/staprun/ctl.c
Examining data/systemtap-4.4/staprun/mainloop.c
Examining data/systemtap-4.4/staprun/modverify.c
Examining data/systemtap-4.4/staprun/modverify.h
Examining data/systemtap-4.4/staprun/monitor.c
Examining data/systemtap-4.4/staprun/relay.c
Examining data/systemtap-4.4/staprun/relay_old.c
Examining data/systemtap-4.4/staprun/stap_merge.c
Examining data/systemtap-4.4/staprun/stapio.c
Examining data/systemtap-4.4/staprun/staprun.c
Examining data/systemtap-4.4/staprun/staprun.h
Examining data/systemtap-4.4/staprun/staprun_funcs.c
Examining data/systemtap-4.4/staprun/stapsh.c
Examining data/systemtap-4.4/staprun/strfloctime.c
Examining data/systemtap-4.4/stapsslerr.h
Examining data/systemtap-4.4/staptree.cxx
Examining data/systemtap-4.4/staptree.h
Examining data/systemtap-4.4/stapvirt.c
Examining data/systemtap-4.4/stringtable.cxx
Examining data/systemtap-4.4/stringtable.h
Examining data/systemtap-4.4/tapset-been.cxx
Examining data/systemtap-4.4/tapset-dynprobe.cxx
Examining data/systemtap-4.4/tapset-dynprobe.h
Examining data/systemtap-4.4/tapset-itrace.cxx
Examining data/systemtap-4.4/tapset-mark.cxx
Examining data/systemtap-4.4/tapset-method.cxx
Examining data/systemtap-4.4/tapset-netfilter.cxx
Examining data/systemtap-4.4/tapset-perfmon.cxx
Examining data/systemtap-4.4/tapset-procfs.cxx
Examining data/systemtap-4.4/tapset-python.cxx
Examining data/systemtap-4.4/tapset-timers.cxx
Examining data/systemtap-4.4/tapset-utrace.cxx
Examining data/systemtap-4.4/tapsets.cxx
Examining data/systemtap-4.4/tapsets.h
Examining data/systemtap-4.4/task_finder.cxx
Examining data/systemtap-4.4/task_finder.h
Examining data/systemtap-4.4/testsuite/sys/sdt.h
Examining data/systemtap-4.4/testsuite/systemtap.base/addr_op_1.c
Examining data/systemtap-4.4/testsuite/systemtap.base/addr_op_4.c
Examining data/systemtap-4.4/testsuite/systemtap.base/at_deref.c
Examining data/systemtap-4.4/testsuite/systemtap.base/at_register.c
Examining data/systemtap-4.4/testsuite/systemtap.base/at_var.c
Examining data/systemtap-4.4/testsuite/systemtap.base/at_var_cu_1.c
Examining data/systemtap-4.4/testsuite/systemtap.base/at_var_cu_2.c
Examining data/systemtap-4.4/testsuite/systemtap.base/at_var_cu_3.c
Examining data/systemtap-4.4/testsuite/systemtap.base/at_var_lvalue.c
Examining data/systemtap-4.4/testsuite/systemtap.base/at_var_print_1.c
Examining data/systemtap-4.4/testsuite/systemtap.base/at_var_timer_profile.c
Examining data/systemtap-4.4/testsuite/systemtap.base/at_var_void_stmt.c
Examining data/systemtap-4.4/testsuite/systemtap.base/atcast-index_1.c
Examining data/systemtap-4.4/testsuite/systemtap.base/atcast-index_2.c
Examining data/systemtap-4.4/testsuite/systemtap.base/auto_path.c
Examining data/systemtap-4.4/testsuite/systemtap.base/bad-code.c
Examining data/systemtap-4.4/testsuite/systemtap.base/buildid.c
Examining data/systemtap-4.4/testsuite/systemtap.base/bz10078.c
Examining data/systemtap-4.4/testsuite/systemtap.base/bz5274.c
Examining data/systemtap-4.4/testsuite/systemtap.base/bz6850.c
Examining data/systemtap-4.4/testsuite/systemtap.base/callee.extern.2.c
Examining data/systemtap-4.4/testsuite/systemtap.base/callee.extern.c
Examining data/systemtap-4.4/testsuite/systemtap.base/callee.inlined.c
Examining data/systemtap-4.4/testsuite/systemtap.base/callee.multicalls.c
Examining data/systemtap-4.4/testsuite/systemtap.base/callee.reloc.c
Examining data/systemtap-4.4/testsuite/systemtap.base/callee.reloc.lib.c
Examining data/systemtap-4.4/testsuite/systemtap.base/callee.simple.c
Examining data/systemtap-4.4/testsuite/systemtap.base/cast-scope.cxx
Examining data/systemtap-4.4/testsuite/systemtap.base/cast-user.c
Examining data/systemtap-4.4/testsuite/systemtap.base/const_value.c
Examining data/systemtap-4.4/testsuite/systemtap.base/const_value_func.c
Examining data/systemtap-4.4/testsuite/systemtap.base/cu-decl-1.c
Examining data/systemtap-4.4/testsuite/systemtap.base/cu-decl-2.c
Examining data/systemtap-4.4/testsuite/systemtap.base/cxxclass.cxx
Examining data/systemtap-4.4/testsuite/systemtap.base/dtrace-inc-dtest.h
Examining data/systemtap-4.4/testsuite/systemtap.base/dw_entry_value.c
Examining data/systemtap-4.4/testsuite/systemtap.base/externalvar.c
Examining data/systemtap-4.4/testsuite/systemtap.base/externalvar_lib.c
Examining data/systemtap-4.4/testsuite/systemtap.base/func_alias.c
Examining data/systemtap-4.4/testsuite/systemtap.base/global_var_distance.c
Examining data/systemtap-4.4/testsuite/systemtap.base/global_var_main.c
Examining data/systemtap-4.4/testsuite/systemtap.base/global_var_speed.c
Examining data/systemtap-4.4/testsuite/systemtap.base/gtod.c
Examining data/systemtap-4.4/testsuite/systemtap.base/hash_add_buildid1.c
Examining data/systemtap-4.4/testsuite/systemtap.base/hash_add_buildid2.c
Examining data/systemtap-4.4/testsuite/systemtap.base/implicitptr.c
Examining data/systemtap-4.4/testsuite/systemtap.base/inherit.cxx
Examining data/systemtap-4.4/testsuite/systemtap.base/inlinedvars.c
Examining data/systemtap-4.4/testsuite/systemtap.base/jennie.c
Examining data/systemtap-4.4/testsuite/systemtap.base/listing_mode.c
Examining data/systemtap-4.4/testsuite/systemtap.base/minidebug.c
Examining data/systemtap-4.4/testsuite/systemtap.base/multisym_baz.c
Examining data/systemtap-4.4/testsuite/systemtap.base/multisym_main.c
Examining data/systemtap-4.4/testsuite/systemtap.base/openmp-stmt.c
Examining data/systemtap-4.4/testsuite/systemtap.base/partial-class-type-heap.cxx
Examining data/systemtap-4.4/testsuite/systemtap.base/partial-class-type-main.cxx
Examining data/systemtap-4.4/testsuite/systemtap.base/partial-inline.c
Examining data/systemtap-4.4/testsuite/systemtap.base/plt.c
Examining data/systemtap-4.4/testsuite/systemtap.base/probewrite_3.c
Examining data/systemtap-4.4/testsuite/systemtap.base/proc_by_pid.c
Examining data/systemtap-4.4/testsuite/systemtap.base/proc_exec.c
Examining data/systemtap-4.4/testsuite/systemtap.base/proc_fork_exec.c
Examining data/systemtap-4.4/testsuite/systemtap.base/proc_thread_exec.c
Examining data/systemtap-4.4/testsuite/systemtap.base/process-begin-user_1.c
Examining data/systemtap-4.4/testsuite/systemtap.base/process-begin-user_2.c
Examining data/systemtap-4.4/testsuite/systemtap.base/process-begin-user_3.c
Examining data/systemtap-4.4/testsuite/systemtap.base/process_by_cmd.c
Examining data/systemtap-4.4/testsuite/systemtap.base/process_by_pid.c
Examining data/systemtap-4.4/testsuite/systemtap.base/process_resume.c
Examining data/systemtap-4.4/testsuite/systemtap.base/pthread_stacks.c
Examining data/systemtap-4.4/testsuite/systemtap.base/ptridx.c
Examining data/systemtap-4.4/testsuite/systemtap.base/register_x64_1.c
Examining data/systemtap-4.4/testsuite/systemtap.base/register_x64_2.c
Examining data/systemtap-4.4/testsuite/systemtap.base/register_x64_3.c
Examining data/systemtap-4.4/testsuite/systemtap.base/register_x64_4.c
Examining data/systemtap-4.4/testsuite/systemtap.base/register_x86_1.c
Examining data/systemtap-4.4/testsuite/systemtap.base/register_x86_2.c
Examining data/systemtap-4.4/testsuite/systemtap.base/register_x86_3.c
Examining data/systemtap-4.4/testsuite/systemtap.base/register_x86_4.c
Examining data/systemtap-4.4/testsuite/systemtap.base/rep_ret.c
Examining data/systemtap-4.4/testsuite/systemtap.base/ret-uprobe-var_1.c
Examining data/systemtap-4.4/testsuite/systemtap.base/retblacklist.c
Examining data/systemtap-4.4/testsuite/systemtap.base/sdt.c
Examining data/systemtap-4.4/testsuite/systemtap.base/sdt_buildid.c
Examining data/systemtap-4.4/testsuite/systemtap.base/sdt_casm.c
Examining data/systemtap-4.4/testsuite/systemtap.base/sdt_misc.c
Examining data/systemtap-4.4/testsuite/systemtap.base/sdt_types.c
Examining data/systemtap-4.4/testsuite/systemtap.base/sdt_va_args.c
Examining data/systemtap-4.4/testsuite/systemtap.base/sdt_varname.c
Examining data/systemtap-4.4/testsuite/systemtap.base/set_user.c
Examining data/systemtap-4.4/testsuite/systemtap.base/setjmp.c
Examining data/systemtap-4.4/testsuite/systemtap.base/stap_hwbkpt_kmod.c
Examining data/systemtap-4.4/testsuite/systemtap.base/stap_kmodule.c
Examining data/systemtap-4.4/testsuite/systemtap.base/statement.c
Examining data/systemtap-4.4/testsuite/systemtap.base/stmt_inlines.c
Examining data/systemtap-4.4/testsuite/systemtap.base/stmt_rel_user.c
Examining data/systemtap-4.4/testsuite/systemtap.base/task_fd_lookup.c
Examining data/systemtap-4.4/testsuite/systemtap.base/tls1.c
Examining data/systemtap-4.4/testsuite/systemtap.base/tls1_.c
Examining data/systemtap-4.4/testsuite/systemtap.base/tls2_.c
Examining data/systemtap-4.4/testsuite/systemtap.base/tlserrno.c
Examining data/systemtap-4.4/testsuite/systemtap.base/towers.c
Examining data/systemtap-4.4/testsuite/systemtap.base/unresolved-struct-typedef.c
Examining data/systemtap-4.4/testsuite/systemtap.base/ustack_1.c
Examining data/systemtap-4.4/testsuite/systemtap.base/utf_pretty.cxx
Examining data/systemtap-4.4/testsuite/systemtap.base/utf_user.c
Examining data/systemtap-4.4/testsuite/systemtap.base/utf_user_trunc.c
Examining data/systemtap-4.4/testsuite/systemtap.base/utrace_p5_multi.c
Examining data/systemtap-4.4/testsuite/systemtap.base/utrace_syscall_args.c
Examining data/systemtap-4.4/testsuite/systemtap.base/vma_vdso.c
Examining data/systemtap-4.4/testsuite/systemtap.base/vta-test.c
Examining data/systemtap-4.4/testsuite/systemtap.clone/dtrace_child.c
Examining data/systemtap-4.4/testsuite/systemtap.clone/dtrace_clone.c
Examining data/systemtap-4.4/testsuite/systemtap.clone/dtrace_fork_parent.c
Examining data/systemtap-4.4/testsuite/systemtap.clone/dtrace_vfork_parent.c
Examining data/systemtap-4.4/testsuite/systemtap.clone/main_quiesce.c
Examining data/systemtap-4.4/testsuite/systemtap.clone/probe_by_pid.c
Examining data/systemtap-4.4/testsuite/systemtap.context/fib.c
Examining data/systemtap-4.4/testsuite/systemtap.context/systemtap_test_module1.c
Examining data/systemtap-4.4/testsuite/systemtap.context/systemtap_test_module2.c
Examining data/systemtap-4.4/testsuite/systemtap.context/uprobe_stmt_num.c
Examining data/systemtap-4.4/testsuite/systemtap.context/uprobe_uaddr_mark.c
Examining data/systemtap-4.4/testsuite/systemtap.context/usymbols.c
Examining data/systemtap-4.4/testsuite/systemtap.context/usymbols_lib.c
Examining data/systemtap-4.4/testsuite/systemtap.context/usymfileline.cxx
Examining data/systemtap-4.4/testsuite/systemtap.exelib/pthreadprobes.c
Examining data/systemtap-4.4/testsuite/systemtap.exelib/uprobes_exe.c
Examining data/systemtap-4.4/testsuite/systemtap.exelib/uprobes_lib.c
Examining data/systemtap-4.4/testsuite/systemtap.pass1-4/debugtypes.cxx
Examining data/systemtap-4.4/testsuite/systemtap.printf/memory1_module.c
Examining data/systemtap-4.4/testsuite/systemtap.printf/pretty-bits.h
Examining data/systemtap-4.4/testsuite/systemtap.printf/pretty-char.h
Examining data/systemtap-4.4/testsuite/systemtap.printf/print_user_buffer.c
Examining data/systemtap-4.4/testsuite/systemtap.speculate/speculate.c
Examining data/systemtap-4.4/testsuite/systemtap.syscall/accept.c
Examining data/systemtap-4.4/testsuite/systemtap.syscall/accept4.c
Examining data/systemtap-4.4/testsuite/systemtap.syscall/access.c
Examining data/systemtap-4.4/testsuite/systemtap.syscall/acct.c
Examining data/systemtap-4.4/testsuite/systemtap.syscall/adjtimex.c
Examining data/systemtap-4.4/testsuite/systemtap.syscall/aio.c
Examining data/systemtap-4.4/testsuite/systemtap.syscall/alarm.c
Examining data/systemtap-4.4/testsuite/systemtap.syscall/arch_prctl.c
Examining data/systemtap-4.4/testsuite/systemtap.syscall/arg_write/dcookie.c
Examining data/systemtap-4.4/testsuite/systemtap.syscall/arg_write/dir.c
Examining data/systemtap-4.4/testsuite/systemtap.syscall/arg_write/poll.c
Examining data/systemtap-4.4/testsuite/systemtap.syscall/bind.c
Examining data/systemtap-4.4/testsuite/systemtap.syscall/bpf.c
Examining data/systemtap-4.4/testsuite/systemtap.syscall/brk.c
Examining data/systemtap-4.4/testsuite/systemtap.syscall/capability.c
Examining data/systemtap-4.4/testsuite/systemtap.syscall/chmod.c
Examining data/systemtap-4.4/testsuite/systemtap.syscall/chroot.c
Examining data/systemtap-4.4/testsuite/systemtap.syscall/clock.c
Examining data/systemtap-4.4/testsuite/systemtap.syscall/clone.c
Examining data/systemtap-4.4/testsuite/systemtap.syscall/connect.c
Examining data/systemtap-4.4/testsuite/systemtap.syscall/copy_file_range.c
Examining data/systemtap-4.4/testsuite/systemtap.syscall/dcookie.c
Examining data/systemtap-4.4/testsuite/systemtap.syscall/dir.c
Examining data/systemtap-4.4/testsuite/systemtap.syscall/domainname.c
Examining data/systemtap-4.4/testsuite/systemtap.syscall/dup.c
Examining data/systemtap-4.4/testsuite/systemtap.syscall/eventfd.c
Examining data/systemtap-4.4/testsuite/systemtap.syscall/execve.c
Examining data/systemtap-4.4/testsuite/systemtap.syscall/execveat.c
Examining data/systemtap-4.4/testsuite/systemtap.syscall/exit.c
Examining data/systemtap-4.4/testsuite/systemtap.syscall/exit_group.c
Examining data/systemtap-4.4/testsuite/systemtap.syscall/fadvise64.c
Examining data/systemtap-4.4/testsuite/systemtap.syscall/fallocate.c
Examining data/systemtap-4.4/testsuite/systemtap.syscall/fanotify.c
Examining data/systemtap-4.4/testsuite/systemtap.syscall/flock.c
Examining data/systemtap-4.4/testsuite/systemtap.syscall/forkwait.c
Examining data/systemtap-4.4/testsuite/systemtap.syscall/futex.c
Examining data/systemtap-4.4/testsuite/systemtap.syscall/futimes.c
Examining data/systemtap-4.4/testsuite/systemtap.syscall/fxattr.c
Examining data/systemtap-4.4/testsuite/systemtap.syscall/getcpu.c
Examining data/systemtap-4.4/testsuite/systemtap.syscall/getdents.c
Examining data/systemtap-4.4/testsuite/systemtap.syscall/getgroups.c
Examining data/systemtap-4.4/testsuite/systemtap.syscall/getitimer.c
Examining data/systemtap-4.4/testsuite/systemtap.syscall/getpeername.c
Examining data/systemtap-4.4/testsuite/systemtap.syscall/getpriority.c
Examining data/systemtap-4.4/testsuite/systemtap.syscall/getrandom.c
Examining data/systemtap-4.4/testsuite/systemtap.syscall/getrlimit.c
Examining data/systemtap-4.4/testsuite/systemtap.syscall/getrusage.c
Examining data/systemtap-4.4/testsuite/systemtap.syscall/getsid.c
Examining data/systemtap-4.4/testsuite/systemtap.syscall/getsockname.c
Examining data/systemtap-4.4/testsuite/systemtap.syscall/getsockopt.c
Examining data/systemtap-4.4/testsuite/systemtap.syscall/handle_at.c
Examining data/systemtap-4.4/testsuite/systemtap.syscall/hostname.c
Examining data/systemtap-4.4/testsuite/systemtap.syscall/inotify.c
Examining data/systemtap-4.4/testsuite/systemtap.syscall/ioctl.c
Examining data/systemtap-4.4/testsuite/systemtap.syscall/ioperm.c
Examining data/systemtap-4.4/testsuite/systemtap.syscall/ioprio.c
Examining data/systemtap-4.4/testsuite/systemtap.syscall/itimer.c
Examining data/systemtap-4.4/testsuite/systemtap.syscall/kcmp.c
Examining data/systemtap-4.4/testsuite/systemtap.syscall/kexec_load.c
Examining data/systemtap-4.4/testsuite/systemtap.syscall/keyctl.c
Examining data/systemtap-4.4/testsuite/systemtap.syscall/kill.c
Examining data/systemtap-4.4/testsuite/systemtap.syscall/link.c
Examining data/systemtap-4.4/testsuite/systemtap.syscall/listen.c
Examining data/systemtap-4.4/testsuite/systemtap.syscall/lseek.c
Examining data/systemtap-4.4/testsuite/systemtap.syscall/lxattr.c
Examining data/systemtap-4.4/testsuite/systemtap.syscall/madvise.c
Examining data/systemtap-4.4/testsuite/systemtap.syscall/membarrier.c
Examining data/systemtap-4.4/testsuite/systemtap.syscall/memfd_create.c
Examining data/systemtap-4.4/testsuite/systemtap.syscall/mempolicy.c
Examining data/systemtap-4.4/testsuite/systemtap.syscall/mincore.c
Examining data/systemtap-4.4/testsuite/systemtap.syscall/mknod.c
Examining data/systemtap-4.4/testsuite/systemtap.syscall/mmap.c
Examining data/systemtap-4.4/testsuite/systemtap.syscall/modify_ldt.c
Examining data/systemtap-4.4/testsuite/systemtap.syscall/module.c
Examining data/systemtap-4.4/testsuite/systemtap.syscall/mount.c
Examining data/systemtap-4.4/testsuite/systemtap.syscall/mq.c
Examining data/systemtap-4.4/testsuite/systemtap.syscall/msg_queue.c
Examining data/systemtap-4.4/testsuite/systemtap.syscall/net1.c
Examining data/systemtap-4.4/testsuite/systemtap.syscall/nfsservctl.c
Examining data/systemtap-4.4/testsuite/systemtap.syscall/nice.c
Examining data/systemtap-4.4/testsuite/systemtap.syscall/numa.c
Examining data/systemtap-4.4/testsuite/systemtap.syscall/openclose.c
Examining data/systemtap-4.4/testsuite/systemtap.syscall/perf_event.c
Examining data/systemtap-4.4/testsuite/systemtap.syscall/personality.c
Examining data/systemtap-4.4/testsuite/systemtap.syscall/pgid.c
Examining data/systemtap-4.4/testsuite/systemtap.syscall/pipe.c
Examining data/systemtap-4.4/testsuite/systemtap.syscall/pivot_root.c
Examining data/systemtap-4.4/testsuite/systemtap.syscall/pkey.c
Examining data/systemtap-4.4/testsuite/systemtap.syscall/poll.c
Examining data/systemtap-4.4/testsuite/systemtap.syscall/prctl.c
Examining data/systemtap-4.4/testsuite/systemtap.syscall/pread.c
Examining data/systemtap-4.4/testsuite/systemtap.syscall/preadv.c
Examining data/systemtap-4.4/testsuite/systemtap.syscall/prlimit.c
Examining data/systemtap-4.4/testsuite/systemtap.syscall/process_vm.c
Examining data/systemtap-4.4/testsuite/systemtap.syscall/ptrace.c
Examining data/systemtap-4.4/testsuite/systemtap.syscall/pwrite.c
Examining data/systemtap-4.4/testsuite/systemtap.syscall/pwritev.c
Examining data/systemtap-4.4/testsuite/systemtap.syscall/quotactl.c
Examining data/systemtap-4.4/testsuite/systemtap.syscall/readahead.c
Examining data/systemtap-4.4/testsuite/systemtap.syscall/readdir.c
Examining data/systemtap-4.4/testsuite/systemtap.syscall/readv.c
Examining data/systemtap-4.4/testsuite/systemtap.syscall/readwrite.c
Examining data/systemtap-4.4/testsuite/systemtap.syscall/reboot.c
Examining data/systemtap-4.4/testsuite/systemtap.syscall/recv.c
Examining data/systemtap-4.4/testsuite/systemtap.syscall/recvfrom.c
Examining data/systemtap-4.4/testsuite/systemtap.syscall/recvmmsg.c
Examining data/systemtap-4.4/testsuite/systemtap.syscall/recvmsg.c
Examining data/systemtap-4.4/testsuite/systemtap.syscall/remap_file_pages.c
Examining data/systemtap-4.4/testsuite/systemtap.syscall/rename.c
Examining data/systemtap-4.4/testsuite/systemtap.syscall/restart_syscall.c
Examining data/systemtap-4.4/testsuite/systemtap.syscall/robust_list.c
Examining data/systemtap-4.4/testsuite/systemtap.syscall/rt_signal.c
Examining data/systemtap-4.4/testsuite/systemtap.syscall/sched.c
Examining data/systemtap-4.4/testsuite/systemtap.syscall/sched_attr.c
Examining data/systemtap-4.4/testsuite/systemtap.syscall/sched_getaffinity.c
Examining data/systemtap-4.4/testsuite/systemtap.syscall/sched_getscheduler.c
Examining data/systemtap-4.4/testsuite/systemtap.syscall/sched_rr_get_interval.c
Examining data/systemtap-4.4/testsuite/systemtap.syscall/sched_setaffinity.c
Examining data/systemtap-4.4/testsuite/systemtap.syscall/sched_setscheduler.c
Examining data/systemtap-4.4/testsuite/systemtap.syscall/seccomp.c
Examining data/systemtap-4.4/testsuite/systemtap.syscall/select.c
Examining data/systemtap-4.4/testsuite/systemtap.syscall/semctl.c
Examining data/systemtap-4.4/testsuite/systemtap.syscall/semget.c
Examining data/systemtap-4.4/testsuite/systemtap.syscall/semop.c
Examining data/systemtap-4.4/testsuite/systemtap.syscall/send.c
Examining data/systemtap-4.4/testsuite/systemtap.syscall/sendfile.c
Examining data/systemtap-4.4/testsuite/systemtap.syscall/sendmmsg.c
Examining data/systemtap-4.4/testsuite/systemtap.syscall/sendmsg.c
Examining data/systemtap-4.4/testsuite/systemtap.syscall/sendto.c
Examining data/systemtap-4.4/testsuite/systemtap.syscall/set_tid_address.c
Examining data/systemtap-4.4/testsuite/systemtap.syscall/setgroups.c
Examining data/systemtap-4.4/testsuite/systemtap.syscall/setitimer.c
Examining data/systemtap-4.4/testsuite/systemtap.syscall/setns.c
Examining data/systemtap-4.4/testsuite/systemtap.syscall/setpriority.c
Examining data/systemtap-4.4/testsuite/systemtap.syscall/setsid.c
Examining data/systemtap-4.4/testsuite/systemtap.syscall/setsockopt.c
Examining data/systemtap-4.4/testsuite/systemtap.syscall/shmat.c
Examining data/systemtap-4.4/testsuite/systemtap.syscall/shmget.c
Examining data/systemtap-4.4/testsuite/systemtap.syscall/shutdown.c
Examining data/systemtap-4.4/testsuite/systemtap.syscall/sigaltstack.c
Examining data/systemtap-4.4/testsuite/systemtap.syscall/sigmask.c
Examining data/systemtap-4.4/testsuite/systemtap.syscall/signal.c
Examining data/systemtap-4.4/testsuite/systemtap.syscall/signalfd.c
Examining data/systemtap-4.4/testsuite/systemtap.syscall/socket.c
Examining data/systemtap-4.4/testsuite/systemtap.syscall/socketpair.c
Examining data/systemtap-4.4/testsuite/systemtap.syscall/stat.c
Examining data/systemtap-4.4/testsuite/systemtap.syscall/statfs.c
Examining data/systemtap-4.4/testsuite/systemtap.syscall/swap.c
Examining data/systemtap-4.4/testsuite/systemtap.syscall/sync.c
Examining data/systemtap-4.4/testsuite/systemtap.syscall/sync_file_range.c
Examining data/systemtap-4.4/testsuite/systemtap.syscall/syncfs.c
Examining data/systemtap-4.4/testsuite/systemtap.syscall/sysctl.c
Examining data/systemtap-4.4/testsuite/systemtap.syscall/sysfs.c
Examining data/systemtap-4.4/testsuite/systemtap.syscall/sysinfo.c
Examining data/systemtap-4.4/testsuite/systemtap.syscall/syslog.c
Examining data/systemtap-4.4/testsuite/systemtap.syscall/tee.c
Examining data/systemtap-4.4/testsuite/systemtap.syscall/thread_area.c
Examining data/systemtap-4.4/testsuite/systemtap.syscall/timer.c
Examining data/systemtap-4.4/testsuite/systemtap.syscall/timerfd.c
Examining data/systemtap-4.4/testsuite/systemtap.syscall/times.c
Examining data/systemtap-4.4/testsuite/systemtap.syscall/trunc.c
Examining data/systemtap-4.4/testsuite/systemtap.syscall/uid.c
Examining data/systemtap-4.4/testsuite/systemtap.syscall/uid16.c
Examining data/systemtap-4.4/testsuite/systemtap.syscall/umask.c
Examining data/systemtap-4.4/testsuite/systemtap.syscall/uname.c
Examining data/systemtap-4.4/testsuite/systemtap.syscall/unlink.c
Examining data/systemtap-4.4/testsuite/systemtap.syscall/unshare.c
Examining data/systemtap-4.4/testsuite/systemtap.syscall/uselib.c
Examining data/systemtap-4.4/testsuite/systemtap.syscall/userfaultfd.c
Examining data/systemtap-4.4/testsuite/systemtap.syscall/vforkwait.c
Examining data/systemtap-4.4/testsuite/systemtap.syscall/vhangup.c
Examining data/systemtap-4.4/testsuite/systemtap.syscall/wait.c
Examining data/systemtap-4.4/testsuite/systemtap.syscall/wait4.c
Examining data/systemtap-4.4/testsuite/systemtap.syscall/writev.c
Examining data/systemtap-4.4/testsuite/systemtap.syscall/xattr.c
Examining data/systemtap-4.4/testsuite/systemtap.unprivileged/libloop.c
Examining data/systemtap-4.4/testsuite/systemtap.unprivileged/loop.c
Examining data/systemtap-4.4/translate.cxx
Examining data/systemtap-4.4/translate.h
Examining data/systemtap-4.4/translator-output.cxx
Examining data/systemtap-4.4/translator-output.h
Examining data/systemtap-4.4/util.cxx
Examining data/systemtap-4.4/util.h
Examining data/systemtap-4.4/version.h
Examining data/systemtap-4.4/main.cxx
FINAL RESULTS:
data/systemtap-4.4/doc/SystemTap_Tapset_Reference/docproc.c:99:4: [5] (buffer) strncat:
Easily used incorrectly (e.g., incorrectly computing the correct maximum
size to add) [MS-banned] (CWE-120). Consider strcat_s, strlcat, snprintf,
or automatically resizing strings. Risk is high; the length parameter
appears to be a constant, instead of computing the number of characters
left.
strncat(real_filename, srctree, PATH_MAX - 1);
data/systemtap-4.4/doc/SystemTap_Tapset_Reference/docproc.c:180:3: [5] (buffer) strncat:
Easily used incorrectly (e.g., incorrectly computing the correct maximum
size to add) [MS-banned] (CWE-120). Consider strcat_s, strlcat, snprintf,
or automatically resizing strings. Risk is high; the length parameter
appears to be a constant, instead of computing the number of characters
left.
strncat(real_filename, srctree, PATH_MAX - 1);
data/systemtap-4.4/httpd/nss_funcs.cxx:166:3: [5] (race) chmod:
This accepts filename arguments; if an attacker can move those files, a
race condition results. (CWE-362). Use fchmod( ) instead.
chmod (pem_tmp.c_str(), (unsigned int)(S_IRUSR | S_IWUSR));
data/systemtap-4.4/nss-server-info.cxx:522:8: [5] (race) chmod:
This accepts filename arguments; if an attacker can move those files, a
race condition results. (CWE-362). Use fchmod( ) instead.
if (chmod (filename.c_str (), 0644) != 0)
data/systemtap-4.4/nsscommon.cxx:976:8: [5] (race) chmod:
This accepts filename arguments; if an attacker can move those files, a
race condition results. (CWE-362). Use fchmod( ) instead.
if (chmod (globbuf.gl_pathv[i], mode) != 0)
data/systemtap-4.4/staplog.c:437:4: [5] (buffer) strncat:
Easily used incorrectly (e.g., incorrectly computing the correct maximum
size to add) [MS-banned] (CWE-120). Consider strcat_s, strlcat, snprintf,
or automatically resizing strings. Risk is high; the length parameter
appears to be a constant, instead of computing the number of characters
left.
strncat(fname, ".may_broken", MAX_FNAME - 1);
data/systemtap-4.4/testsuite/systemtap.syscall/chmod.c:28:3: [5] (race) chmod:
This accepts filename arguments; if an attacker can move those files, a
race condition results. (CWE-362). Use fchmod( ) instead.
chmod("foobar", 0644);
data/systemtap-4.4/testsuite/systemtap.syscall/chmod.c:39:3: [5] (race) chmod:
This accepts filename arguments; if an attacker can move those files, a
race condition results. (CWE-362). Use fchmod( ) instead.
chmod((char *)-1, 0644);
data/systemtap-4.4/testsuite/systemtap.syscall/chmod.c:58:3: [5] (race) chmod:
This accepts filename arguments; if an attacker can move those files, a
race condition results. (CWE-362). Use fchmod( ) instead.
chmod("foobar", -1);
data/systemtap-4.4/testsuite/systemtap.syscall/chmod.c:73:3: [5] (race) chown:
This accepts filename arguments; if an attacker can move those files, a
race condition results. (CWE-362). Use fchown( ) instead.
chown((char *)-1, 5000, 5001);
data/systemtap-4.4/testsuite/systemtap.syscall/chmod.c:80:3: [5] (race) chown:
This accepts filename arguments; if an attacker can move those files, a
race condition results. (CWE-362). Use fchown( ) instead.
chown("foobar", 5000, -1);
data/systemtap-4.4/testsuite/systemtap.syscall/chmod.c:83:3: [5] (race) chown:
This accepts filename arguments; if an attacker can move those files, a
race condition results. (CWE-362). Use fchown( ) instead.
chown("foobar", -1, 5001);
data/systemtap-4.4/testsuite/systemtap.syscall/link.c:127:3: [5] (race) readlink:
This accepts filename arguments; if an attacker can move those files or
change the link content, a race condition results. Also, it does not
terminate with ASCII NUL. (CWE-362, CWE-20). Reconsider approach.
readlink("Sfoobar", buf, sizeof(buf));
data/systemtap-4.4/testsuite/systemtap.syscall/link.c:130:3: [5] (race) readlink:
This accepts filename arguments; if an attacker can move those files or
change the link content, a race condition results. Also, it does not
terminate with ASCII NUL. (CWE-362, CWE-20). Reconsider approach.
readlink((char *)-1, buf, sizeof(buf));
data/systemtap-4.4/testsuite/systemtap.syscall/link.c:137:3: [5] (race) readlink:
This accepts filename arguments; if an attacker can move those files or
change the link content, a race condition results. Also, it does not
terminate with ASCII NUL. (CWE-362, CWE-20). Reconsider approach.
readlink("Sfoobar", (char *)-1, sizeof(buf));
data/systemtap-4.4/testsuite/systemtap.syscall/link.c:144:3: [5] (race) readlink:
This accepts filename arguments; if an attacker can move those files or
change the link content, a race condition results. Also, it does not
terminate with ASCII NUL. (CWE-362, CWE-20). Reconsider approach.
readlink("Sfoobar", buf, -1);
data/systemtap-4.4/util.cxx:481:11: [5] (race) readlink:
This accepts filename arguments; if an attacker can move those files or
change the link content, a race condition results. Also, it does not
terminate with ASCII NUL. (CWE-362, CWE-20). Reconsider approach.
r = readlink(f, linkname, st.st_size + 1);
data/systemtap-4.4/util.cxx:509:9: [5] (race) readlink:
This accepts filename arguments; if an attacker can move those files or
change the link content, a race condition results. Also, it does not
terminate with ASCII NUL. (CWE-362, CWE-20). Reconsider approach.
r = readlink(f1, linkname, st.st_size + 1);
data/systemtap-4.4/util.cxx:1460:17: [5] (race) readlink:
This accepts filename arguments; if an attacker can move those files or
change the link content, a race condition results. Also, it does not
terminate with ASCII NUL. (CWE-362, CWE-20). Reconsider approach.
ssize_t len = readlink(file, buf, sizeof(buf) - 1);
data/systemtap-4.4/bpf-internal.h:182:6: [4] (buffer) sprintf:
Does not check for buffer overflows (CWE-120). Use sprintf_s, snprintf, or
vsnprintf.
FN(sprintf), \
data/systemtap-4.4/client-nss.cxx:136:7: [4] (format) fprintf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
fprintf (stderr, STAP_CSC_01, expected);
data/systemtap-4.4/client-nss.cxx:334:7: [4] (format) fprintf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
fprintf (stderr, STAP_CSC_02,
data/systemtap-4.4/client-nss.cxx:342:7: [4] (format) fprintf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
fprintf (stderr, STAP_CSC_03, connectionState->infileName);
data/systemtap-4.4/client-nss.cxx:379:7: [4] (format) fprintf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
fprintf (stderr, STAP_CSC_04, connectionState->outfileName);
data/systemtap-4.4/client-nss.cxx:400:4: [4] (format) fprintf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
fprintf (stderr, STAP_CSC_05, connectionState->outfileName);
data/systemtap-4.4/doc/SystemTap_Tapset_Reference/docproc.c:102:4: [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(real_filename, svec);
data/systemtap-4.4/nsscommon.cxx:613:4: [4] (buffer) strcpy:
Does not check for buffer overflows when copying to destination [MS-banned]
(CWE-120). Consider using snprintf, strcpy_s, or strlcpy (warning: strncpy
easily misused).
strcpy (tbuf, components[i].c_str ());
data/systemtap-4.4/remote.cxx:696:9: [4] (buffer) strcpy:
Does not check for buffer overflows when copying to destination [MS-banned]
(CWE-120). Consider using snprintf, strcpy_s, or strlcpy (warning: strncpy
easily misused).
strcpy(server.sun_path, ud.path.c_str());
data/systemtap-4.4/rpm_finder.cxx:92:11: [4] (buffer) sprintf:
Does not check for buffer overflows (CWE-120). Use sprintf_s, snprintf, or
vsnprintf.
sprintf(header, "%%{sourcerpm}%s%s", rpm_type, arch);
data/systemtap-4.4/runtime/dyninst/io.c:26:24: [4] (format) printf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
__attribute ((format (printf, 4, 0)));
data/systemtap-4.4/runtime/dyninst/io.c:56:3: [4] (buffer) strcpy:
Does not check for buffer overflows when copying to destination [MS-banned]
(CWE-120). Consider using snprintf, strcpy_s, or strlcpy (warning: strncpy
easily misused).
strcpy(buf, WARN_STRING);
data/systemtap-4.4/runtime/dyninst/io.c:63:3: [4] (buffer) strcpy:
Does not check for buffer overflows when copying to destination [MS-banned]
(CWE-120). Consider using snprintf, strcpy_s, or strlcpy (warning: strncpy
easily misused).
strcpy(buf, ERR_STRING);
data/systemtap-4.4/runtime/dyninst/io.c:68:8: [4] (format) vsnprintf:
If format strings can be influenced by an attacker, they can be exploited,
and note that sprintf variations do not always \0-terminate (CWE-134). Use
a constant for the format specification.
num = vsnprintf(buf + start, STP_LOG_BUF_LEN - start - 1, fmt, args);
data/systemtap-4.4/runtime/dyninst/transport.c:165:24: [4] (format) printf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
__attribute ((format (printf, 1, 2)));
data/systemtap-4.4/runtime/dyninst/transport.c:170:2: [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 (stderr, fmt, args);
data/systemtap-4.4/runtime/linux/io.c:30:31: [4] (format) printf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
__attribute ((format (printf, 4, 0)));
data/systemtap-4.4/runtime/linux/io.c:43:3: [4] (buffer) strcpy:
Does not check for buffer overflows when copying to destination [MS-banned]
(CWE-120). Consider using snprintf, strcpy_s, or strlcpy (warning: strncpy
easily misused).
strcpy (buf, WARN_STRING);
data/systemtap-4.4/runtime/linux/io.c:48:3: [4] (buffer) strcpy:
Does not check for buffer overflows when copying to destination [MS-banned]
(CWE-120). Consider using snprintf, strcpy_s, or strlcpy (warning: strncpy
easily misused).
strcpy (buf, ERR_STRING);
data/systemtap-4.4/runtime/linux/loc2c-runtime.h:35:9: [4] (format) snprintf:
If format strings can be influenced by an attacker, they can be exploited,
and note that sprintf variations do not always \0-terminate (CWE-134). Use
a constant for the format specification.
snprintf(c->error_buffer, sizeof(c->error_buffer), \
data/systemtap-4.4/runtime/linux/loc2c-runtime.h:45:9: [4] (format) snprintf:
If format strings can be influenced by an attacker, they can be exploited,
and note that sprintf variations do not always \0-terminate (CWE-134). Use
a constant for the format specification.
snprintf(c->error_buffer, sizeof(c->error_buffer), \
data/systemtap-4.4/runtime/linux/runtime.h:94:98: [4] (format) printf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
static void _stp_dbug (const char *func, int line, const char *fmt, ...) __attribute__ ((format (printf, 3, 4)));
data/systemtap-4.4/runtime/linux/runtime.h:95:71: [4] (format) printf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
static void _stp_error (const char *fmt, ...) __attribute__ ((format (printf, 1, 2)));
data/systemtap-4.4/runtime/linux/runtime.h:96:70: [4] (format) printf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
static void _stp_warn (const char *fmt, ...) __attribute__ ((format (printf, 1, 2)));
data/systemtap-4.4/runtime/linux/runtime.h:163:5: [4] (format) snprintf:
If format strings can be influenced by an attacker, they can be exploited,
and note that sprintf variations do not always \0-terminate (CWE-134). Use
a constant for the format specification.
snprintf (CONTEXT->error_buffer, MAXSTRINGLEN, STAP_MSG_RUNTIME_H_01, \
data/systemtap-4.4/runtime/loc2c-runtime.h:41:2: [4] (format) snprintf:
If format strings can be influenced by an attacker, they can be exploited,
and note that sprintf variations do not always \0-terminate (CWE-134). Use
a constant for the format specification.
snprintf(c->error_buffer, sizeof(c->error_buffer), \
data/systemtap-4.4/runtime/loc2c-runtime.h:50:2: [4] (format) snprintf:
If format strings can be influenced by an attacker, they can be exploited,
and note that sprintf variations do not always \0-terminate (CWE-134). Use
a constant for the format specification.
snprintf(c->error_buffer, sizeof(c->error_buffer), \
data/systemtap-4.4/runtime/loc2c-runtime.h:240:5: [4] (format) snprintf:
If format strings can be influenced by an attacker, they can be exploited,
and note that sprintf variations do not always \0-terminate (CWE-134). Use
a constant for the format specification.
snprintf(c->error_buffer, sizeof(c->error_buffer), \
data/systemtap-4.4/runtime/loc2c-runtime.h:247:5: [4] (format) snprintf:
If format strings can be influenced by an attacker, they can be exploited,
and note that sprintf variations do not always \0-terminate (CWE-134). Use
a constant for the format specification.
snprintf(c->error_buffer, sizeof(c->error_buffer), \
data/systemtap-4.4/runtime/softfloat.c:604:5: [4] (buffer) strcat:
Does not check for buffer overflows when concatenating to destination
[MS-banned] (CWE-120). Consider using strcat_s, strncat, strlcat, or
snprintf (warning: strncat is easily misused).
strcat(result, iPart);
data/systemtap-4.4/runtime/softfloat.c:614:9: [4] (buffer) strcat:
Does not check for buffer overflows when concatenating to destination
[MS-banned] (CWE-120). Consider using strcat_s, strncat, strlcat, or
snprintf (warning: strncat is easily misused).
strcat(result, fTemp);
data/systemtap-4.4/runtime/softfloat.c:632:5: [4] (buffer) strcat:
Does not check for buffer overflows when concatenating to destination
[MS-banned] (CWE-120). Consider using strcat_s, strncat, strlcat, or
snprintf (warning: strncat is easily misused).
strcat(result, fTemp);
data/systemtap-4.4/session.cxx:1955:30: [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(download_dbinfo != 0 && access ("/usr/bin/abrt-action-install-debuginfo-to-abrt-cache", X_OK) < 0
data/systemtap-4.4/session.cxx:1956:30: [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.
&& access ("/usr/libexec/abrt-action-install-debuginfo-to-abrt-cache", X_OK) < 0)
data/systemtap-4.4/setupdwfl.cxx:102:22: [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.
(access ("/usr/bin/abrt-action-install-debuginfo-to-abrt-cache", X_OK) == 0
data/systemtap-4.4/setupdwfl.cxx:104:24: [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.
: (access ("/usr/libexec/abrt-action-install-debuginfo-to-abrt-cache", X_OK) == 0
data/systemtap-4.4/setupdwfl.cxx:336:3: [4] (buffer) strcpy:
Does not check for buffer overflows when copying to destination [MS-banned]
(CWE-120). Consider using snprintf, strcpy_s, or strlcpy (warning: strncpy
easily misused).
strcpy (path_new, path.c_str());
data/systemtap-4.4/stapbpf/bpfinterp.cxx:390:3: [4] (format) snprintf:
If format strings can be influenced by an attacker, they can be exploited,
and note that sprintf variations do not always \0-terminate (CWE-134). Use
a constant for the format specification.
snprintf(s, 256, fstr, arg1, arg2, arg3);
data/systemtap-4.4/stapbpf/bpfinterp.cxx:687:7: [4] (format) fprintf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
fprintf(ctx->output_f, format_str.c_str(),
data/systemtap-4.4/stapbpf/bpfinterp.cxx:994:13: [4] (format) fprintf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
dr = fprintf(output_f, remove_tag(as_str(regs[1])).c_str(),
data/systemtap-4.4/stapbpf/stapbpf.cxx:228:10: [4] (shell) system:
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.
string system;
data/systemtap-4.4/stapbpf/stapbpf.cxx:235:7: [4] (shell) system:
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.
: system(s), name(n), prog_fd(fd), event_id(-1), event_fd(-1)
data/systemtap-4.4/stapbpf/stapbpf.cxx:257:3: [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(stderr, str, va);
data/systemtap-4.4/stapbpf/stapbpf.cxx:638:13: [4] (buffer) sscanf:
The scanf() family's %s operation, without a limit specification, permits
buffer overflows (CWE-120, CWE-20). Specify a limit to %s, or use a
different input function.
int res = sscanf(name, "procfsprobe/%lu/%c/%lu/%s", &umask, &type, &maxsize_val, fifoname);
data/systemtap-4.4/stapbpf/stapbpf.cxx:671:13: [4] (buffer) sscanf:
The scanf() family's %s operation, without a limit specification, permits
buffer overflows (CWE-120, CWE-20). Specify a limit to %s, or use a
different input function.
int res = sscanf(name, "uprobe/%c/%d/%llu%s", &type, &pid, &off, path);
data/systemtap-4.4/stapbpf/stapbpf.cxx:732:13: [4] (buffer) sscanf:
The scanf() family's %s operation, without a limit specification, permits
buffer overflows (CWE-120, CWE-20). Specify a limit to %s, or use a
different input function.
int res = sscanf(name, "trace/%[^/]/%s", tp_system, tp_name);
data/systemtap-4.4/stapbpf/stapbpf.cxx:749:13: [4] (buffer) sscanf:
The scanf() family's %s operation, without a limit specification, permits
buffer overflows (CWE-120, CWE-20). Specify a limit to %s, or use a
different input function.
int res = sscanf(name, "raw_trace/%[^/]/%s", tp_system, tp_name);
data/systemtap-4.4/stapbpf/stapbpf.cxx:856:21: [4] (format) snprintf:
If format strings can be influenced by an attacker, they can be exploited,
and note that sprintf variations do not always \0-terminate (CWE-134). Use
a constant for the format specification.
ssize_t len = snprintf(fnbuf, sizeof(fnbuf),
data/systemtap-4.4/stapbpf/stapbpf.cxx:975:21: [4] (format) snprintf:
If format strings can be influenced by an attacker, they can be exploited,
and note that sprintf variations do not always \0-terminate (CWE-134). Use
a constant for the format specification.
ssize_t len = snprintf(fnbuf, sizeof(fnbuf),
data/systemtap-4.4/stapbpf/stapbpf.cxx:1098:21: [4] (format) snprintf:
If format strings can be influenced by an attacker, they can be exploited,
and note that sprintf variations do not always \0-terminate (CWE-134). Use
a constant for the format specification.
ssize_t len = snprintf(fnbuf, sizeof(fnbuf),
data/systemtap-4.4/stapbpf/stapbpf.cxx:1100:32: [4] (shell) system:
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.
t.system.c_str(), t.name.c_str());
data/systemtap-4.4/stapbpf/stapbpf.cxx:1115:23: [4] (shell) system:
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.
t.system.c_str(), t.name.c_str(), EVENTS);
data/systemtap-4.4/staplog.c:336:2: [4] (buffer) sprintf:
Does not check for buffer overflows (CWE-120). Use sprintf_s, snprintf, or
vsnprintf.
sprintf(output_file,"%s/%s", dname, fname);
data/systemtap-4.4/staprun/common.c:77:2: [4] (buffer) strcpy:
Does not check for buffer overflows when copying to destination [MS-banned]
(CWE-120). Consider using snprintf, strcpy_s, or strlcpy (warning: strncpy
easily misused).
strcpy(&path_buf[len + 1], path);
data/systemtap-4.4/staprun/common.c:693:3: [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(stderr, fmt, va);
data/systemtap-4.4/staprun/ctl.c:58: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.
(access (buf2, W_OK)==0)) {
data/systemtap-4.4/staprun/ctl.c:63:17: [4] (buffer) strcpy:
Does not check for buffer overflows when copying to destination [MS-banned]
(CWE-120). Consider using snprintf, strcpy_s, or strlcpy (warning: strncpy
easily misused).
strcpy(buf, buf2); // committed
data/systemtap-4.4/staprun/ctl.c:77:38: [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 (relay_basedir_fd < 0 && (access(buf2, W_OK)==0)) {
data/systemtap-4.4/staprun/ctl.c:78:17: [4] (buffer) strcpy:
Does not check for buffer overflows when copying to destination [MS-banned]
(CWE-120). Consider using snprintf, strcpy_s, or strlcpy (warning: strncpy
easily misused).
strcpy(buf, buf2); // committed
data/systemtap-4.4/staprun/ctl.c:112:30: [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 (control_channel >= 0 && access(buf, R_OK|W_OK) != 0) {
data/systemtap-4.4/staprun/mainloop.c:304:13: [4] (buffer) sprintf:
Does not check for buffer overflows (CWE-120). Use sprintf_s, snprintf, or
vsnprintf.
sprintf(buf, "%s < /dev/null", target_cmd);
data/systemtap-4.4/staprun/mainloop.c:362:9: [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 ((sh_c_argv[0] == NULL ? words.we_wordv[0] : sh_c_argv[0]),
data/systemtap-4.4/staprun/mainloop.c:436:7: [4] (shell) execlp:
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 (execlp("sh", "sh", "-c", cmd, NULL) < 0)
data/systemtap-4.4/staprun/mainloop.c:594:19: [4] (shell) execlp:
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.
execlp("sh", "sh", "-c", cmd, NULL);
data/systemtap-4.4/staprun/modverify.c:200:3: [4] (buffer) sprintf:
Does not check for buffer overflows (CWE-120). Use sprintf_s, snprintf, or
vsnprintf.
sprintf (fileName, "%s/cert8.db", cert_db_path);
data/systemtap-4.4/staprun/modverify.c:202:3: [4] (buffer) sprintf:
Does not check for buffer overflows (CWE-120). Use sprintf_s, snprintf, or
vsnprintf.
sprintf (fileName, "%s/key3.db", cert_db_path);
data/systemtap-4.4/staprun/modverify.c:204:3: [4] (buffer) sprintf:
Does not check for buffer overflows (CWE-120). Use sprintf_s, snprintf, or
vsnprintf.
sprintf (fileName, "%s/secmod.db", cert_db_path);
data/systemtap-4.4/staprun/staprun.c:123:17: [4] (shell) execv:
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 (execv(path, argv) < 0)
data/systemtap-4.4/staprun/staprun.c:685: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("/sys/kernel/notes", R_OK))
data/systemtap-4.4/staprun/staprun.h:119:8: [4] (format) snprintf:
If format strings can be influenced by an attacker, they can be exploited,
and note that sprintf variations do not always \0-terminate (CWE-134). Use
a constant for the format specification.
_rc = snprintf(str, sizeof(str), args); \
data/systemtap-4.4/staprun/staprun.h:132:8: [4] (format) snprintf:
If format strings can be influenced by an attacker, they can be exploited,
and note that sprintf variations do not always \0-terminate (CWE-134). Use
a constant for the format specification.
_rc = snprintf(str, size, args); \
data/systemtap-4.4/staprun/staprun_funcs.c:95:3: [4] (buffer) strcat:
Does not check for buffer overflows when concatenating to destination
[MS-banned] (CWE-120). Consider using strcat_s, strncat, strlcat, or
snprintf (warning: strncat is easily misused).
strcat(opts, options[i]);
data/systemtap-4.4/staprun/staprun_funcs.c:437:3: [4] (buffer) sprintf:
Does not check for buffer overflows (CWE-120). Use sprintf_s, snprintf, or
vsnprintf.
sprintf (signature_realpath, "%s.sgn", path);
data/systemtap-4.4/staprun/stapsh.c:170:5: [4] (format) fprintf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
fprintf (stapsh_err, "stapsh:%s:%d " format, \
data/systemtap-4.4/staprun/stapsh.c:177: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 (stapsh_err, format, args); \
data/systemtap-4.4/staprun/stapsh.c:182:5: [4] (format) fprintf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
fprintf (stapsh_err, "stapsh:%s:%d " format, \
data/systemtap-4.4/staprun/stapsh.c:190:36: [4] (format) printf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
static int __attribute__ ((format (printf, 1, 2)))
data/systemtap-4.4/staprun/stapsh.c:199:13: [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.
int ret = vfprintf (stapsh_out, format, args);
data/systemtap-4.4/staprun/stapsh.c:586:5: [4] (buffer) strcpy:
Does not check for buffer overflows when copying to destination [MS-banned]
(CWE-120). Consider using snprintf, strcpy_s, or strlcpy (warning: strncpy
easily misused).
strcpy(staprun, BINDIR "/stapdyn");
data/systemtap-4.4/staprun/stapsh.c:604:7: [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(staprun, X_OK) != 0)
data/systemtap-4.4/stapvirt.c:31:5: [4] (format) fprintf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
fprintf (stderr, format, ## args); } while (0)
data/systemtap-4.4/stapvirt.c:756:9: [4] (format) printf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
printf(pers ? "persistent" : "transient");
data/systemtap-4.4/tapsets.cxx:8712:21: [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 (new_path.c_str(), X_OK) == 0
data/systemtap-4.4/tapsets.cxx:12277:10: [4] (shell) system:
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.
string system; // target subsystem(s) to query
data/systemtap-4.4/tapsets.cxx:12336:8: [4] (shell) system:
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 (!system.empty())
data/systemtap-4.4/tapsets.cxx:12341:64: [4] (shell) system:
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.
|| !dw.function_name_matches_pattern(current_system, system))
data/systemtap-4.4/testsuite/systemtap.base/proc_exec.c:17:9: [4] (shell) execv:
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 (execv(new_argv[0], new_argv) < 0)
data/systemtap-4.4/testsuite/systemtap.base/proc_fork_exec.c:30:6: [4] (shell) execv:
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 (execv(new_argv[0], new_argv) < 0)
data/systemtap-4.4/testsuite/systemtap.base/proc_thread_exec.c:10:9: [4] (shell) execv:
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 (execv(new_argv[0], new_argv) < 0)
data/systemtap-4.4/testsuite/systemtap.syscall/access.c:26:3: [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.
access("foobar1", F_OK);
data/systemtap-4.4/testsuite/systemtap.syscall/access.c:34:3: [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.
access("foobar1", R_OK);
data/systemtap-4.4/testsuite/systemtap.syscall/access.c:42:3: [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.
access("foobar1", W_OK);
data/systemtap-4.4/testsuite/systemtap.syscall/access.c:50:3: [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.
access("foobar1", X_OK);
data/systemtap-4.4/testsuite/systemtap.syscall/access.c:58:3: [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.
access("foobar1", R_OK|W_OK);
data/systemtap-4.4/testsuite/systemtap.syscall/access.c:66:3: [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.
access("foobar1", R_OK|W_OK|X_OK);
data/systemtap-4.4/testsuite/systemtap.syscall/access.c:74:3: [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.
access((char *)-1, F_OK);
data/systemtap-4.4/testsuite/systemtap.syscall/access.c:81:3: [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.
access("foobar1", -1);
data/systemtap-4.4/testsuite/systemtap.syscall/madvise.c:21:5: [4] (buffer) sprintf:
Does not check for buffer overflows (CWE-120). Use sprintf_s, snprintf, or
vsnprintf.
sprintf(filename, "%s-out.%d", *argv, getpid());
data/systemtap-4.4/testsuite/systemtap.syscall/recvmmsg.c:162:5: [4] (buffer) strcpy:
Does not check for buffer overflows when copying to destination [MS-banned]
(CWE-120). Consider using snprintf, strcpy_s, or strlcpy (warning: strncpy
easily misused).
strcpy(sun1.sun_path, tmpsunpath);
data/systemtap-4.4/testsuite/systemtap.syscall/recvmsg.c:160:5: [4] (buffer) strcpy:
Does not check for buffer overflows when copying to destination [MS-banned]
(CWE-120). Consider using snprintf, strcpy_s, or strlcpy (warning: strncpy
easily misused).
strcpy(sun1.sun_path, tmpsunpath);
data/systemtap-4.4/util.cxx:495:8: [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(f1, X_OK) == 0
data/systemtap-4.4/util.cxx:570:11: [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(f, X_OK) == 0
data/systemtap-4.4/util.cxx:637: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 (access(f, X_OK) == 0
data/systemtap-4.4/util.cxx:877:21: [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(*it == '/' && (access(args[0].c_str(), X_OK)==-1)) //checking to see if staprun is executable
data/systemtap-4.4/util.h:133:74: [4] (format) printf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
std::string autosprintf(const char* format, ...) __attribute__ ((format (printf, 1, 2)));
data/systemtap-4.4/buildrun.cxx:99:25: [3] (buffer) getenv:
Environment variables are untrustable input if they can be set by an
attacker. They can have any content and length, and the same variable can
be set more than once (CWE-807, CWE-20). Check environment variables
carefully before using them.
const char *oldpath = getenv("PATH");
data/systemtap-4.4/buildrun.cxx:838:24: [3] (buffer) getenv:
Environment variables are untrustable input if they can be set by an
attacker. They can have any content and length, and the same variable can
be set more than once (CWE-807, CWE-20). Check environment variables
carefully before using them.
vector<string> cmd { getenv("SYSTEMTAP_STAPDYN") ?: BINDIR "/stapdyn" };
data/systemtap-4.4/buildrun.cxx:876:24: [3] (buffer) getenv:
Environment variables are untrustable input if they can be set by an
attacker. They can have any content and length, and the same variable can
be set more than once (CWE-807, CWE-20). Check environment variables
carefully before using them.
vector<string> cmd { getenv("SYSTEMTAP_STAPRUN") ?: BINDIR "/staprun" };
data/systemtap-4.4/buildrun.cxx:952:17: [3] (buffer) getenv:
Environment variables are untrustable input if they can be set by an
attacker. They can have any content and length, and the same variable can
be set more than once (CWE-807, CWE-20). Check environment variables
carefully before using them.
cmd.push_back(getenv("SYSTEMTAP_STAPBPF") ?: BINDIR "/stapbpf");
data/systemtap-4.4/csclient.cxx:404:19: [3] (buffer) getenv:
Environment variables are untrustable input if they can be set by an
attacker. They can have any content and length, and the same variable can
be set more than once (CWE-807, CWE-20). Check environment variables
carefully before using them.
char* var = getenv((*it).c_str());
data/systemtap-4.4/doc/SystemTap_Tapset_Reference/docproc.c:382:12: [3] (buffer) getenv:
Environment variables are untrustable input if they can be set by an
attacker. They can have any content and length, and the same variable can
be set more than once (CWE-807, CWE-20). Check environment variables
carefully before using them.
srctree = getenv("SRCTREE");
data/systemtap-4.4/dwflpp.cxx:4897:7: [3] (buffer) getenv:
Environment variables are untrustable input if they can be set by an
attacker. They can have any content and length, and the same variable can
be set more than once (CWE-807, CWE-20). Check environment variables
carefully before using them.
if (getenv ("PR15123_DISABLE"))
data/systemtap-4.4/dwflpp.cxx:4903:8: [3] (buffer) getenv:
Environment variables are untrustable input if they can be set by an
attacker. They can have any content and length, and the same variable can
be set more than once (CWE-807, CWE-20). Check environment variables
carefully before using them.
if (!getenv ("PR15123_ASSUME_MFENTRY")) {
data/systemtap-4.4/hash.cxx:191:21: [3] (buffer) getenv:
Environment variables are untrustable input if they can be set by an
attacker. They can have any content and length, and the same variable can
be set more than once (CWE-807, CWE-20). Check environment variables
carefully before using them.
const char *s_n = getenv("SYSTEMTAP_NLEVELS");
data/systemtap-4.4/httpd/api.cxx:726:12: [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 grc = getopt_long(argc, argv, STAP_SHORT_OPTIONS,
data/systemtap-4.4/httpd/main.cxx:116:12: [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 grc = getopt_long(argc, argv, "", long_options, NULL);
data/systemtap-4.4/httpd/utils.cxx:172:8: [3] (buffer) getenv:
Environment variables are untrustable input if they can be set by an
attacker. They can have any content and length, and the same variable can
be set more than once (CWE-807, CWE-20). Check environment variables
carefully before using them.
(getenv("TMPDIR") ?: "/tmp"));
data/systemtap-4.4/interactive.cxx:829:19: [3] (buffer) getenv:
Environment variables are untrustable input if they can be set by an
attacker. They can have any content and length, and the same variable can
be set more than once (CWE-807, CWE-20). Check environment variables
carefully before using them.
if ((editor = getenv ("EDITOR")) == NULL)
data/systemtap-4.4/nsscommon.cxx:85:21: [3] (buffer) getenv:
Environment variables are untrustable input if they can be set by an
attacker. They can have any content and length, and the same variable can
be set more than once (CWE-807, CWE-20). Check environment variables
carefully before using them.
const char* s_d = getenv ("SYSTEMTAP_DIR");
data/systemtap-4.4/nsscommon.cxx:97:21: [3] (buffer) getenv:
Environment variables are untrustable input if they can be set by an
attacker. They can have any content and length, and the same variable can
be set more than once (CWE-807, CWE-20). Check environment variables
carefully before using them.
const char* s_d = getenv ("SYSTEMTAP_DIR");
data/systemtap-4.4/nsscommon.cxx:197:14: [3] (buffer) getenv:
Environment variables are untrustable input if they can be set by an
attacker. They can have any content and length, and the same variable can
be set more than once (CWE-807, CWE-20). Check environment variables
carefully before using them.
char *sd = getenv("SYSTEMTAP_DIR");
data/systemtap-4.4/nsscommon.cxx:479:3: [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.
srand (time (NULL));
data/systemtap-4.4/python/HelperSDT/_HelperSDT.c:232:19: [3] (buffer) getenv:
Environment variables are untrustable input if they can be set by an
attacker. They can have any content and length, and the same variable can
be set more than once (CWE-807, CWE-20). Check environment variables
carefully before using them.
stap_module = getenv("SYSTEMTAP_MODULE");
data/systemtap-4.4/session.cxx:183:15: [3] (buffer) getenv:
Environment variables are untrustable input if they can be set by an
attacker. They can have any content and length, and the same variable can
be set more than once (CWE-807, CWE-20). Check environment variables
carefully before using them.
&& strcmp(getenv("TERM") ?: "notdumb", "dumb"); // on auto
data/systemtap-4.4/session.cxx:194:21: [3] (buffer) getenv:
Environment variables are untrustable input if they can be set by an
attacker. They can have any content and length, and the same variable can
be set more than once (CWE-807, CWE-20). Check environment variables
carefully before using them.
const char* s_p = getenv ("SYSTEMTAP_TAPSET");
data/systemtap-4.4/session.cxx:210:22: [3] (buffer) getenv:
Environment variables are untrustable input if they can be set by an
attacker. They can have any content and length, and the same variable can
be set more than once (CWE-807, CWE-20). Check environment variables
carefully before using them.
const char* s_p1 = getenv ("XDG_DATA_DIRS");
data/systemtap-4.4/session.cxx:221:21: [3] (buffer) getenv:
Environment variables are untrustable input if they can be set by an
attacker. They can have any content and length, and the same variable can
be set more than once (CWE-807, CWE-20). Check environment variables
carefully before using them.
const char* s_r = getenv ("SYSTEMTAP_RUNTIME");
data/systemtap-4.4/session.cxx:227:21: [3] (buffer) getenv:
Environment variables are untrustable input if they can be set by an
attacker. They can have any content and length, and the same variable can
be set more than once (CWE-807, CWE-20). Check environment variables
carefully before using them.
const char* s_d = getenv ("SYSTEMTAP_DIR");
data/systemtap-4.4/session.cxx:250:22: [3] (buffer) getenv:
Environment variables are untrustable input if they can be set by an
attacker. They can have any content and length, and the same variable can
be set more than once (CWE-807, CWE-20). Check environment variables
carefully before using them.
const char* s_tc = getenv ("SYSTEMTAP_COVERAGE");
data/systemtap-4.4/session.cxx:254:22: [3] (buffer) getenv:
Environment variables are untrustable input if they can be set by an
attacker. They can have any content and length, and the same variable can
be set more than once (CWE-807, CWE-20). Check environment variables
carefully before using them.
const char* s_kr = getenv ("SYSTEMTAP_RELEASE");
data/systemtap-4.4/session.cxx:751:17: [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 grc = getopt_long (argc, argv, STAP_SHORT_OPTIONS, stap_long_options, NULL);
data/systemtap-4.4/session.cxx:1614:28: [3] (buffer) getenv:
Environment variables are untrustable input if they can be set by an
attacker. They can have any content and length, and the same variable can
be set more than once (CWE-807, CWE-20). Check environment variables
carefully before using them.
strcmp(getenv("TERM") ?: "notdumb", "dumb"));
data/systemtap-4.4/session.cxx:1974:24: [3] (buffer) getenv:
Environment variables are untrustable input if they can be set by an
attacker. They can have any content and length, and the same variable can
be set more than once (CWE-807, CWE-20). Check environment variables
carefully before using them.
const char *tmpdir = getenv("TMPDIR");
data/systemtap-4.4/session.cxx:2636:29: [3] (buffer) getenv:
Environment variables are untrustable input if they can be set by an
attacker. They can have any content and length, and the same variable can
be set more than once (CWE-807, CWE-20). Check environment variables
carefully before using them.
const char * tmpdir_env = getenv("TMPDIR");
data/systemtap-4.4/session.cxx:2756:9: [3] (buffer) getenv:
Environment variables are untrustable input if they can be set by an
attacker. They can have any content and length, and the same variable can
be set more than once (CWE-807, CWE-20). Check environment variables
carefully before using them.
key = getenv("SYSTEMTAP_COLORS");
data/systemtap-4.4/session.cxx:2805:7: [3] (buffer) getenv:
Environment variables are untrustable input if they can be set by an
attacker. They can have any content and length, and the same variable can
be set more than once (CWE-807, CWE-20). Check environment variables
carefully before using them.
if (getenv("SYSTEMTAP_SIGN"))
data/systemtap-4.4/setupdwfl.cxx:41:40: [3] (buffer) getenv:
Environment variables are untrustable input if they can be set by an
attacker. They can have any content and length, and the same variable can
be set more than once (CWE-807, CWE-20). Check environment variables
carefully before using them.
static const char *debuginfo_env_arr = getenv("SYSTEMTAP_DEBUGINFO_PATH");
data/systemtap-4.4/stap-gen-cert.cxx:54: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.
int grc = getopt (argc, argv, "P");
data/systemtap-4.4/stap-serverd.cxx:224:17: [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 grc = getopt_long (argc, argv, "a:B:D:I:kPr:R:", long_options, NULL);
data/systemtap-4.4/stap-serverd.cxx:978:3: [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.
srand (time (NULL));
data/systemtap-4.4/stap-serverd.cxx:998:9: [3] (buffer) getenv:
Environment variables are untrustable input if they can be set by an
attacker. They can have any content and length, and the same variable can
be set more than once (CWE-807, CWE-20). Check environment variables
carefully before using them.
if (! getenv ("STAP_PR11197_OVERRIDE")) {
data/systemtap-4.4/stap-serverd.cxx:1582:17: [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 grc = getopt_long (argc, argv, STAP_SHORT_OPTIONS, stap_long_options, NULL);
data/systemtap-4.4/stap-serverd.cxx:1751:32: [3] (buffer) getenv:
Environment variables are untrustable input if they can be set by an
attacker. They can have any content and length, and the same variable can
be set more than once (CWE-807, CWE-20). Check environment variables
carefully before using them.
stapargv.push_back ((char *)(getenv ("SYSTEMTAP_STAP") ?: STAP_PREFIX "/bin/stap"));
data/systemtap-4.4/stap-serverd.cxx:2260:64: [3] (buffer) getenv:
Environment variables are untrustable input if they can be set by an
attacker. They can have any content and length, and the same variable can
be set more than once (CWE-807, CWE-20). Check environment variables
carefully before using them.
retlen = snprintf(tmpdir, PATH_MAX, "%s/stap-server.XXXXXX", getenv("TMPDIR") ?: "/tmp");
data/systemtap-4.4/stapbpf/stapbpf.cxx:2101:16: [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.
while ((rc = getopt_long(argc, argv, "hvVwx:o:", long_opts, NULL)) >= 0)
data/systemtap-4.4/stapdyn/dynutil.cxx:73:18: [3] (buffer) getenv:
Environment variables are untrustable input if they can be set by an
attacker. They can have any content and length, and the same variable can
be set more than once (CWE-807, CWE-20). Check environment variables
carefully before using them.
char* rt_env = getenv(rt_env_name);
data/systemtap-4.4/stapdyn/dynutil.cxx:278:9: [3] (buffer) getenv:
Environment variables are untrustable input if they can be set by an
attacker. They can have any content and length, and the same variable can
be set more than once (CWE-807, CWE-20). Check environment variables
carefully before using them.
key = getenv("SYSTEMTAP_COLORS");
data/systemtap-4.4/stapdyn/stapdyn.cxx:73:15: [3] (buffer) getenv:
Environment variables are untrustable input if they can be set by an
attacker. They can have any content and length, and the same variable can
be set more than once (CWE-807, CWE-20). Check environment variables
carefully before using them.
&& strcmp(getenv("TERM") ?: "notdumb", "dumb");
data/systemtap-4.4/stapdyn/stapdyn.cxx:77: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, "c:x:vwo:VhC:")) != -1)
data/systemtap-4.4/stapdyn/stapdyn.cxx:115:25: [3] (buffer) getenv:
Environment variables are untrustable input if they can be set by an
attacker. They can have any content and length, and the same variable can
be set more than once (CWE-807, CWE-20). Check environment variables
carefully before using them.
&& strcmp(getenv("TERM") ?: "notdumb", "dumb");
data/systemtap-4.4/staplog.c:478:14: [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 ((c = getopt(argcnt, args, "+ao:")) != EOF) {
data/systemtap-4.4/staprun/common.c:141:27: [3] (buffer) getenv:
Environment variables are untrustable input if they can be set by an
attacker. They can have any content and length, and the same variable can
be set more than once (CWE-807, CWE-20). Check environment variables
carefully before using them.
&& strcmp(getenv("TERM") ?: "notdumb", "dumb");
data/systemtap-4.4/staprun/common.c:143:14: [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 ((c = getopt(argc, argv, "ALu::vihb:t:dc:o:x:N:S:DwRr:VT:C:M:"
data/systemtap-4.4/staprun/common.c:266:17: [3] (buffer) getenv:
Environment variables are untrustable input if they can be set by an
attacker. They can have any content and length, and the same variable can
be set more than once (CWE-807, CWE-20). Check environment variables
carefully before using them.
&& strcmp(getenv("TERM") ?: "notdumb", "dumb"));
data/systemtap-4.4/staprun/common.c:735:8: [3] (buffer) getenv:
Environment variables are untrustable input if they can be set by an
attacker. They can have any content and length, and the same variable can
be set more than once (CWE-807, CWE-20). Check environment variables
carefully before using them.
key = getenv("SYSTEMTAP_COLORS");
data/systemtap-4.4/staprun/mainloop.c:567:13: [3] (buffer) getenv:
Environment variables are untrustable input if they can be set by an
attacker. They can have any content and length, and the same variable can
be set more than once (CWE-807, CWE-20). Check environment variables
carefully before using them.
staprun = getenv ("SYSTEMTAP_STAPRUN") ?: BINDIR "/staprun";
data/systemtap-4.4/staprun/stap_merge.c:52:14: [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 ((c = getopt (argc, argv, "vo:")) != EOF) {
data/systemtap-4.4/staprun/staprun.c:165:8: [3] (buffer) getenv:
Environment variables are untrustable input if they can be set by an
attacker. They can have any content and length, and the same variable can
be set more than once (CWE-807, CWE-20). Check environment variables
carefully before using them.
(getenv("SYSTEMTAP_RUNTIME") ?: PKGDATADIR "/runtime"));
data/systemtap-4.4/staprun/staprun.c:202:36: [3] (buffer) getenv:
Environment variables are untrustable input if they can be set by an
attacker. They can have any content and length, and the same variable can
be set more than once (CWE-807, CWE-20). Check environment variables
carefully before using them.
if ((fips_mode != '0') && !getenv("STAP_FIPS_OVERRIDE")) {
data/systemtap-4.4/staprun/staprun.c:314:13: [3] (buffer) getenv:
Environment variables are untrustable input if they can be set by an
attacker. They can have any content and length, and the same variable can
be set more than once (CWE-807, CWE-20). Check environment variables
carefully before using them.
if (getenv ("STAP_PR13193_OVERRIDE"))
data/systemtap-4.4/staprun/staprun.c:361:13: [3] (buffer) getenv:
Environment variables are untrustable input if they can be set by an
attacker. They can have any content and length, and the same variable can
be set more than once (CWE-807, CWE-20). Check environment variables
carefully before using them.
if (getenv ("STAP_BZ1552745_OVERRIDE"))
data/systemtap-4.4/staprun/staprun.c:522:12: [3] (buffer) getenv:
Environment variables are untrustable input if they can be set by an
attacker. They can have any content and length, and the same variable can
be set more than once (CWE-807, CWE-20). Check environment variables
carefully before using them.
argv[0] = getenv ("SYSTEMTAP_STAPIO") ?: PKGLIBDIR "/stapio";
data/systemtap-4.4/staprun/staprun_funcs.c:100:6: [3] (buffer) realpath:
This function does not protect against buffer overflows, and some
implementations can overflow internally (CWE-120/CWE-785!). Ensure that the
destination buffer is at least of size MAXPATHLEN, andto protect against
implementation problems, the input argument should also be checked to
ensure it is no larger than MAXPATHLEN.
if (realpath(path, module_realpath) == NULL) {
data/systemtap-4.4/staprun/staprun_funcs.c:188:13: [3] (buffer) getenv:
Environment variables are untrustable input if they can be set by an
attacker. They can have any content and length, and the same variable can
be set more than once (CWE-807, CWE-20). Check environment variables
carefully before using them.
if (getenv ("SYSTEMTAP_SYNC") != NULL)
data/systemtap-4.4/staprun/staprun_funcs.c:472:6: [3] (buffer) realpath:
This function does not protect against buffer overflows, and some
implementations can overflow internally (CWE-120/CWE-785!). Ensure that the
destination buffer is at least of size MAXPATHLEN, andto protect against
implementation problems, the input argument should also be checked to
ensure it is no larger than MAXPATHLEN.
if (realpath(staplib_dir_path, staplib_dir_realpath) == NULL) {
data/systemtap-4.4/staprun/staprun_funcs.c:776:24: [3] (buffer) getenv:
Environment variables are untrustable input if they can be set by an
attacker. They can have any content and length, and the same variable can
be set more than once (CWE-807, CWE-20). Check environment variables
carefully before using them.
const char *env_id = getenv("SYSTEMTAP_REAL_UID");
data/systemtap-4.4/staprun/staprun_funcs.c:782:12: [3] (buffer) getenv:
Environment variables are untrustable input if they can be set by an
attacker. They can have any content and length, and the same variable can
be set more than once (CWE-807, CWE-20). Check environment variables
carefully before using them.
env_id = getenv("SYSTEMTAP_REAL_GID");
data/systemtap-4.4/staprun/stapsh.c:321:15: [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 ((c = getopt (argc, argv, "vl:")) != -1)
data/systemtap-4.4/staprun/stapsh.c:758:12: [3] (buffer) getenv:
Environment variables are untrustable input if they can be set by an
attacker. They can have any content and length, and the same variable can
be set more than once (CWE-807, CWE-20). Check environment variables
carefully before using them.
getenv("TMPDIR") ?: "/tmp");
data/systemtap-4.4/stapvirt.c:1289: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 ((c = getopt(argc, argv, "c:d:hv")) != -1) {
data/systemtap-4.4/testsuite/systemtap.base/vta-test.c:25:3: [3] (random) srandom:
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.
srandom (c.i);
data/systemtap-4.4/testsuite/systemtap.base/vta-test.c:28:3: [3] (random) srandom:
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.
srandom (c.i);
data/systemtap-4.4/testsuite/systemtap.base/vta-test.c:31:3: [3] (random) srandom:
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.
srandom (c.i + 4);
data/systemtap-4.4/testsuite/systemtap.base/vta-test.c:41:3: [3] (random) srandom:
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.
srandom (c.i);
data/systemtap-4.4/testsuite/systemtap.base/vta-test.c:44:3: [3] (random) srandom:
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.
srandom (c.i);
data/systemtap-4.4/testsuite/systemtap.base/vta-test.c:47:3: [3] (random) srandom:
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.
srandom (c.i + 4);
data/systemtap-4.4/testsuite/systemtap.base/vta-test.c:57:3: [3] (random) srandom:
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.
srandom (c.i);
data/systemtap-4.4/testsuite/systemtap.base/vta-test.c:60:3: [3] (random) srandom:
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.
srandom (c.i);
data/systemtap-4.4/testsuite/systemtap.base/vta-test.c:63:3: [3] (random) srandom:
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.
srandom (c.i + 4);
data/systemtap-4.4/testsuite/systemtap.context/uprobe_stmt_num.c:22:2: [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.
srand(func(42));
data/systemtap-4.4/testsuite/systemtap.syscall/chroot.c:7:5: [3] (misc) chroot:
chroot can be very helpful, but is hard to use correctly (CWE-250, CWE-22).
Make sure the program immediately chdir("/"), closes file descriptors, and
drops root privileges, and that all necessary files (and no more!) are in
the new root.
chroot("/tmp");
data/systemtap-4.4/testsuite/systemtap.syscall/chroot.c:10:5: [3] (misc) chroot:
chroot can be very helpful, but is hard to use correctly (CWE-250, CWE-22).
Make sure the program immediately chdir("/"), closes file descriptors, and
drops root privileges, and that all necessary files (and no more!) are in
the new root.
chroot((const char *)-1);
data/systemtap-4.4/util.cxx:63:19: [3] (buffer) getenv:
Environment variables are untrustable input if they can be set by an
attacker. They can have any content and length, and the same variable can
be set more than once (CWE-807, CWE-20). Check environment variables
carefully before using them.
const char *p = getenv("HOME");
data/systemtap-4.4/util.cxx:257:15: [3] (buffer) getenv:
Environment variables are untrustable input if they can be set by an
attacker. They can have any content and length, and the same variable can
be set more than once (CWE-807, CWE-20). Check environment variables
carefully before using them.
char *env = getenv(env_name);
data/systemtap-4.4/util.cxx:623:16: [3] (buffer) getenv:
Environment variables are untrustable input if they can be set by an
attacker. They can have any content and length, and the same variable can
be set more than once (CWE-807, CWE-20). Check environment variables
carefully before using them.
path = getenv(env_path.c_str());
data/systemtap-4.4/util.h:369:25: [3] (buffer) realpath:
This function does not protect against buffer overflows, and some
implementations can overflow internally (CWE-120/CWE-785!). Ensure that the
destination buffer is at least of size MAXPATHLEN, andto protect against
implementation problems, the input argument should also be checked to
ensure it is no larger than MAXPATHLEN.
char* resolved_path = realpath(path.c_str(), NULL);
data/systemtap-4.4/bpf-bitset.cxx:106:3: [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(data, o.data, words * sizeof(word_t));
data/systemtap-4.4/bpf-bitset.cxx:123:3: [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(data, o.data, n1 * w2 * sizeof(word_t));
data/systemtap-4.4/bpf-bitset.h:166:5: [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(data, o.data, words * sizeof(*data));
data/systemtap-4.4/bpf-bitset.h:240:5: [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(data, o.data, n1 * w2 * sizeof(word_t));
data/systemtap-4.4/bpf-translate.cxx:4810:12: [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 fd = open(module.c_str(), O_RDWR | O_CREAT | O_TRUNC, 0666);
data/systemtap-4.4/cache.cxx:115: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).
fd_stapconf = open(s.stapconf_path.c_str(), O_RDONLY);
data/systemtap-4.4/cache.cxx:155: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).
fd_module = open(s.hash_path.c_str(), O_RDONLY);
data/systemtap-4.4/cache.cxx:163:10: [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).
fd_c = open(c_src_path.c_str(), O_RDONLY);
data/systemtap-4.4/client-http.cxx:377:30: [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).
std::FILE *File = std::fopen (filepath.c_str(), "wb");
data/systemtap-4.4/client-http.cxx:549:13: [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).
if ((fd = open (fname.c_str(), O_RDONLY)) < 0)
data/systemtap-4.4/client-http.cxx:583:12: [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 fd = open (notesfile, O_RDONLY);
data/systemtap-4.4/client-http.cxx:590:16: [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.
unsigned char data[8192];
data/systemtap-4.4/client-http.cxx:875:12: [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).
int fd = mkstemp ((char*)pem_tmp.c_str());
data/systemtap-4.4/client-http.cxx:1018: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 cwd[PATH_MAX];
data/systemtap-4.4/client-http.cxx:1191:20: [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).
int fd = mkstemp ((char*)pem_tmp.c_str());
data/systemtap-4.4/client-http.cxx:1433: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 hostname[NI_MAXHOST];
data/systemtap-4.4/client-http.cxx:1458:16: [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).
int fd = mkstemp ((char*)pem_tmp.c_str());
data/systemtap-4.4/client-http.cxx:1513:12: [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).
int fd = mkstemp ((char*)pem_tmp.c_str());
data/systemtap-4.4/client-nss.cxx:584: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 cwd[PATH_MAX];
data/systemtap-4.4/doc/SystemTap_Tapset_Reference/docproc.c:90: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 real_filename[PATH_MAX + 1];
data/systemtap-4.4/doc/SystemTap_Tapset_Reference/docproc.c:176: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 line[MAXLINESZ];
data/systemtap-4.4/doc/SystemTap_Tapset_Reference/docproc.c:178: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 real_filename[PATH_MAX + 1];
data/systemtap-4.4/doc/SystemTap_Tapset_Reference/docproc.c:184:8: [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).
fp = fopen(real_filename, "r");
data/systemtap-4.4/doc/SystemTap_Tapset_Reference/docproc.c:269: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 *vec[200]; /* Enough for specific functions */
data/systemtap-4.4/doc/SystemTap_Tapset_Reference/docproc.c:300: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 *vec[6]; /* kerneldoc -docbook -function "section" file NULL */
data/systemtap-4.4/doc/SystemTap_Tapset_Reference/docproc.c:327: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 line[MAXLINESZ];
data/systemtap-4.4/doc/SystemTap_Tapset_Reference/docproc.c:390:11: [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).
infile = fopen(argv[2], "r");
data/systemtap-4.4/dwflpp.cxx:1381:11: [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 linebuf[256];
data/systemtap-4.4/dwflpp.cxx:1382:11: [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 soname[256];
data/systemtap-4.4/dwflpp.cxx:1383:11: [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 shlib[256];
data/systemtap-4.4/hash.cxx:105:12: [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.
unsigned char sum[16];
data/systemtap-4.4/hash.cxx:125:12: [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).
log_file.open(hash_log_path.c_str());
data/systemtap-4.4/hash.cxx:194:17: [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).
nlevels = atoi(s_n);
data/systemtap-4.4/httpd/api.cxx:713:23: [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 **argv = new char *[argc + 1];
data/systemtap-4.4/httpd/api.cxx:869:10: [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(stdout_path, ios::out);
data/systemtap-4.4/httpd/api.cxx:872:10: [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(stderr_path, ios::out);
data/systemtap-4.4/httpd/backends.cxx:54:19: [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).
stdout_stream.open(stdout_path);
data/systemtap-4.4/httpd/backends.cxx:60:19: [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).
stderr_stream.open(stderr_path);
data/systemtap-4.4/httpd/backends.cxx:327:21: [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).
build_data_file.open(build_data_path, ios::out);
data/systemtap-4.4/httpd/backends.cxx:340: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 datetime[13] = { '\0' };
data/systemtap-4.4/httpd/nss_funcs.cxx:151:12: [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).
int fd = mkstemp ((char*)pk12_tmp.c_str());
data/systemtap-4.4/httpd/nss_funcs.cxx:162:8: [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 ((char*)pem_tmp.c_str());
data/systemtap-4.4/httpd/server.cxx:256: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).
ufi.fd = open(full_path.c_str(),
data/systemtap-4.4/httpd/server.cxx:540:11: [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 fd = open(response.file.c_str(), O_RDONLY);
data/systemtap-4.4/httpd/utils.cxx:118:14: [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.
unsigned char sum[16];
data/systemtap-4.4/httpd/utils.cxx:121: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).
int fd = open(pathname.c_str(), O_RDONLY);
data/systemtap-4.4/httpd/utils.cxx:170: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 tmpdir[PATH_MAX];
data/systemtap-4.4/interactive.cxx:833: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(temp_path);
data/systemtap-4.4/interactive.cxx:896: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 line[2048];
data/systemtap-4.4/mdfour.c:120:12: [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.
unsigned char buf[128];
data/systemtap-4.4/mdfour.c:129:10: [2] (buffer) memcpy:
Does not check for buffer overflows when copying to destination (CWE-120).
Make sure destination can always hold the source data.
if (n) memcpy(buf, in, n);
data/systemtap-4.4/mdfour.c:163:7: [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(md->tail+md->tail_len, in, len);
data/systemtap-4.4/mdfour.c:187:2: [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(md->tail, in, n);
data/systemtap-4.4/mdfour.h:27:12: [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.
unsigned char tail[64];
data/systemtap-4.4/nss-server-info.cxx:131:6: [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[MAX_NETADDR_SIZE];
data/systemtap-4.4/nss-server-info.cxx:773:6: [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[MAX_NETADDR_SIZE];
data/systemtap-4.4/nss-server-info.cxx:1969:8: [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 hbuf[NI_MAXHOST];
data/systemtap-4.4/nss-server-info.cxx:2120: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 a[AVAHI_ADDRESS_STR_MAX];
data/systemtap-4.4/nsscommon.cxx:122:11: [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).
logfile.open (arg, ios_base::app);
data/systemtap-4.4/nsscommon.cxx:480: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 randbuf[64];
data/systemtap-4.4/nsscommon.cxx:612:18: [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 *tbuf = (char *)PORT_ArenaAlloc (arena, components[i].size () + 1);
data/systemtap-4.4/nsscommon.cxx:802: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 *inFile = fopen (inFileName.c_str (), "rb");
data/systemtap-4.4/nsscommon.cxx:1104:13: [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).
outFile = fopen (outFileName.c_str (), "wb");
data/systemtap-4.4/nsscommon.cxx:1325: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 timeString[256];
data/systemtap-4.4/nsscommon.cxx:1556:12: [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.
unsigned char buffer[4096];
data/systemtap-4.4/nsscommon.cxx:1689:20: [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 *certFile = fopen (certPath.c_str (), "rb");
data/systemtap-4.4/nsscommon.cxx:1784:12: [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.
unsigned char fingerprint_buf[SHA1_LENGTH];
data/systemtap-4.4/remote.cxx:184:23: [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[4096];
data/systemtap-4.4/remote.cxx:202:27: [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 cmdbuf[1024];
data/systemtap-4.4/remote.cxx:249:31: [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[4096];
data/systemtap-4.4/remote.cxx:280: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 reply[4096];
data/systemtap-4.4/remote.cxx:312:19: [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* f = fopen(filename.c_str(), "r");
data/systemtap-4.4/remote.cxx:328: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 buf[4096];
data/systemtap-4.4/rpm_finder.cxx:90:4: [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 header[31] = {};
data/systemtap-4.4/rpm_finder.cxx:133:4: [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 (s2, rpm_type, rpminfolen);
data/systemtap-4.4/runtime/common_probe_context.h:102:1: [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[128];
data/systemtap-4.4/runtime/docs/examples/list.c:7:6: [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 (buf, "Item%d", i);
data/systemtap-4.4/runtime/dyninst/arith.c:60:11: [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 fd = open("/dev/urandom", O_RDONLY);
data/systemtap-4.4/runtime/dyninst/copy.c:71:16: [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).
_stp_mem_fd = open("/proc/self/mem", O_RDWR /*| O_LARGEFILE*/);
data/systemtap-4.4/runtime/dyninst/io.c:33: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 local_buffer[STP_LOG_BUF_LEN];
data/systemtap-4.4/runtime/dyninst/linux_defs.h:106:3: [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(dest, src, len);
data/systemtap-4.4/runtime/dyninst/linux_defs.h:126:2: [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(dest, src, len);
data/systemtap-4.4/runtime/dyninst/session_attributes.h:18: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 tz_name[MAXSTRINGLEN];
data/systemtap-4.4/runtime/dyninst/session_attributes.h:19: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 module_name[MAXSTRINGLEN];
data/systemtap-4.4/runtime/dyninst/session_attributes.h:20: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 outfile_name[PATH_MAX];
data/systemtap-4.4/runtime/dyninst/shm.c:23:8: [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.
static char _stp_shm_name[NAME_MAX] = { '\0' };
data/systemtap-4.4/runtime/dyninst/shm.c:49: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 name[NAME_MAX];
data/systemtap-4.4/runtime/dyninst/transport.c:270: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 *spawn_argv[4] = { "sh", "-c", command, NULL };
data/systemtap-4.4/runtime/dyninst/transport.c:339: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[PATH_MAX];
data/systemtap-4.4/runtime/dyninst/transport.c:349:12: [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).
out_fd = open (buf, O_CREAT|O_TRUNC|O_WRONLY|O_CLOEXEC, 0666);
data/systemtap-4.4/runtime/dyninst/transport.c:548:2: [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, len);
data/systemtap-4.4/runtime/dyninst/transport.h:91: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 print_buf[_STP_DYNINST_BUFFER_SIZE];
data/systemtap-4.4/runtime/dyninst/transport.h:105: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 log_buf[_STP_DYNINST_LOG_BUF_LEN];
data/systemtap-4.4/runtime/linux/access_process_vm.h:132:3: [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 (dst, src, len);
data/systemtap-4.4/runtime/linux/access_process_vm.h:140:3: [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 (dst, src, len);
data/systemtap-4.4/runtime/linux/addr-map.c:316:7: [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(&new_map->entries, old_map->entries,
data/systemtap-4.4/runtime/linux/addr-map.c:319: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(new_entry + 1, &old_map->entries[existing],
data/systemtap-4.4/runtime/linux/print.c:40: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 buf[STP_BUFFER_SIZE];
data/systemtap-4.4/runtime/linux/print.c:50: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 _stp_lbuf[STP_LOG_BUF_LEN];
data/systemtap-4.4/runtime/linux/regs.c:356: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 symbol_name[KSYM_SYMBOL_LEN];
data/systemtap-4.4/runtime/linux/runtime.h:319:10: [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.
return sprintf(buffer, "%lli", (long long)*((int64_t *)kp->arg));
data/systemtap-4.4/runtime/linux/stp_tracepoint.c:61: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 name[0];
data/systemtap-4.4/runtime/linux/stp_tracepoint.c:160:2: [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(&e->name[0], name, name_len);
data/systemtap-4.4/runtime/linux/task_finder2.c:672:11: [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.
unsigned char tsk_build_id[MAX_HEXSTR_LEN + 1];
data/systemtap-4.4/runtime/linux/uprobes/uprobes.c:284:2: [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(&ppt->opcode, ppt->insn, BP_INSN_SIZE);
data/systemtap-4.4/runtime/linux/uprobes/uprobes.c:1283: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 buf[UPROBES_SSOL_TAGSZ];
data/systemtap-4.4/runtime/linux/uprobes2/uprobes.c:285:2: [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(&ppt->opcode, ppt->insn, BP_INSN_SIZE);
data/systemtap-4.4/runtime/linux/uprobes2/uprobes.c:1422: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 buf[UPROBES_SSOL_TAGSZ];
data/systemtap-4.4/runtime/linux/uprobes2/uprobes_arm.h:108:3: [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(dst, src, len); \
data/systemtap-4.4/runtime/map-gen.c:49: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.
#define VALSTOR char value[MAP_STRING_LENGTH]
data/systemtap-4.4/runtime/map-gen.c:131:18: [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.
#define KEY1STOR char key1[MAP_STRING_LENGTH]
data/systemtap-4.4/runtime/map-gen.c:163:18: [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.
#define KEY2STOR char key2[MAP_STRING_LENGTH]
data/systemtap-4.4/runtime/map-gen.c:184:18: [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.
#define KEY3STOR char key3[MAP_STRING_LENGTH]
data/systemtap-4.4/runtime/map-gen.c:205:18: [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.
#define KEY4STOR char key4[MAP_STRING_LENGTH]
data/systemtap-4.4/runtime/map-gen.c:226:18: [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.
#define KEY5STOR char key5[MAP_STRING_LENGTH]
data/systemtap-4.4/runtime/map-gen.c:247:18: [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.
#define KEY6STOR char key6[MAP_STRING_LENGTH]
data/systemtap-4.4/runtime/map-gen.c:268:18: [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.
#define KEY7STOR char key7[MAP_STRING_LENGTH]
data/systemtap-4.4/runtime/map-gen.c:289:18: [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.
#define KEY8STOR char key8[MAP_STRING_LENGTH]
data/systemtap-4.4/runtime/map-gen.c:310:18: [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.
#define KEY9STOR char key9[MAP_STRING_LENGTH]
data/systemtap-4.4/runtime/print_flush.c:59:5: [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(_stp_data_entry_data(entry), bufp,
data/systemtap-4.4/runtime/print_flush.c:100:4: [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(_stp_data_entry_data(entry), &t, sizeof(t));
data/systemtap-4.4/runtime/print_flush.c:111:5: [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(_stp_data_entry_data(entry), bufp,
data/systemtap-4.4/runtime/print_flush.c:174:5: [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(_stp_data_entry_data(entry), bufp,
data/systemtap-4.4/runtime/runtime_defines.h:27: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 string_t[MAXSTRINGLEN];
data/systemtap-4.4/runtime/softfloat.c:557:12: [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.
static char buf[32] = {0};
data/systemtap-4.4/runtime/stp_utrace.c:192:2: [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(&utrace_work->regs, regs, sizeof(struct pt_regs));
data/systemtap-4.4/runtime/stp_utrace.c:337:16: [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.
static char kmem_cache1_name[50];
data/systemtap-4.4/runtime/stp_utrace.c:338:16: [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.
static char kmem_cache2_name[50];
data/systemtap-4.4/runtime/sym.c:258:10: [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.
static char fullpath [MAXSTRINGLEN];
data/systemtap-4.4/runtime/sym.c:650:16: [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.
static const char hexnibble[16]="0123456789abcdef";
data/systemtap-4.4/runtime/sym.c:651: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 hexstring_theory[max_buildid_hexstring], hexstring_practice[max_buildid_hexstring];
data/systemtap-4.4/runtime/sym.c:851:12: [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.
unsigned char practice_id_bits[MAXSTRINGLEN];
data/systemtap-4.4/runtime/syscall.h:342:2: [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(args, ®s->bx + i, n * sizeof(args[0]));
data/systemtap-4.4/runtime/syscall.h:344:2: [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(args, ®s->ebx + i, n * sizeof(args[0]));
data/systemtap-4.4/runtime/syscall.h:479:2: [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(args, ®s->gpr[3 + i], n * sizeof(args[0]));
data/systemtap-4.4/runtime/syscall.h:667:2: [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(args, ®s->uregs[i], n * sizeof(args[0]));
data/systemtap-4.4/runtime/task_finder_vma.c:57: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 path[TASK_FINDER_VMA_ENTRY_PATHLEN]; /* mmpath name, if known */
data/systemtap-4.4/runtime/transport/control.c:221: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 buf[64];
data/systemtap-4.4/runtime/transport/control.c:326:2: [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(&_stp_ctl_oob_warn->buf, msg, len);
data/systemtap-4.4/runtime/transport/control.c:337:2: [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(&_stp_ctl_oob_err->buf, msg, len);
data/systemtap-4.4/runtime/transport/control.c:348:2: [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(&_stp_ctl_system_warn->buf, msg, len);
data/systemtap-4.4/runtime/transport/control.c:359:2: [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(&_stp_ctl_realtime_err->buf, msg, len);
data/systemtap-4.4/runtime/transport/control.c:427:3: [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(bptr->buf, data, len);
data/systemtap-4.4/runtime/transport/control.c:494:4: [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(bptr->buf, data, len);
data/systemtap-4.4/runtime/transport/control.h:27: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 buf[STP_CTL_BUFFER_SIZE];
data/systemtap-4.4/runtime/transport/procfs.c:30: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.
static char proc_root_name[STP_MODULE_NAME_LEN + sizeof("systemtap/")];
data/systemtap-4.4/runtime/transport/procfs.c:156:4: [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(bptr->buf + bptr->len, data, len);
data/systemtap-4.4/runtime/transport/procfs.c:169:12: [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.
int len = sprintf(page, "%d,%d\n", _stp_nsubbufs, _stp_subbuf_size);
data/systemtap-4.4/runtime/transport/procfs.c:232:61: [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).
relay_procfs_operations.proc_open = relay_file_operations.open;
data/systemtap-4.4/runtime/transport/procfs.c:321: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 fullpath[sizeof("/proc/systemtap") + STP_MODULE_NAME_LEN + sizeof("/traceNNNNN") + 42];
data/systemtap-4.4/runtime/transport/symbols.c:34: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 module[STP13_MODULE_NAME_LEN];
data/systemtap-4.4/runtime/transport/symbols.c:35: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 reloc[STP13_SYMBOL_NAME_LEN];
data/systemtap-4.4/runtime/transport/transport.c:36:8: [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.
static char _stp_remote_uri[MAXSTRINGLEN];
data/systemtap-4.4/runtime/transport/transport.c:688:8: [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.
static char tz_name[MAXSTRINGLEN];
data/systemtap-4.4/runtime/transport/transport_msgs.h:125: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 cmd[128];
data/systemtap-4.4/runtime/transport/transport_msgs.h:132: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 name[STP_MODULE_NAME_LEN];
data/systemtap-4.4/runtime/transport/transport_msgs.h:155: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 module[STP_MODULE_NAME_LEN];
data/systemtap-4.4/runtime/transport/transport_msgs.h:156: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 reloc[STP_SYMBOL_NAME_LEN];
data/systemtap-4.4/runtime/transport/transport_msgs.h:163: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 tz_name[STP_TZ_NAME_LEN];
data/systemtap-4.4/runtime/transport/transport_msgs.h:174: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 remote_uri[STP_REMOTE_URI_LEN];
data/systemtap-4.4/runtime/unwind.c:437:6: [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(®_STATE.regs[value], &state->cie_regs[value], sizeof(struct unwind_item));
data/systemtap-4.4/runtime/unwind.c:653:5: [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(®_STATE.regs[value], &state->cie_regs[value], sizeof(struct unwind_item));
data/systemtap-4.4/runtime/unwind.c:688: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.
static char buf[64];
data/systemtap-4.4/runtime/unwind.c:1300:2: [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(&state->cie_regs, ®_STATE.regs, sizeof (REG_STATE.regs));
data/systemtap-4.4/runtime/unwind/i386.h:135:3: [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(&info->regs, regs, offsetof(struct pt_regs, sp));
data/systemtap-4.4/runtime/unwind/i386.h:139:3: [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(&info->regs, regs, offsetof(struct pt_regs, esp));
data/systemtap-4.4/runtime/vsprintf.c:32: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 c,sign,tmp[66];
data/systemtap-4.4/runtime/vsprintf.c:130: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 c,sign,tmp[66];
data/systemtap-4.4/runtime/vsprintf.c:477:3: [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(str, &num, precision); //to prevent unaligned access
data/systemtap-4.4/session.cxx:1171:16: [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).
else if(atoi(optarg) > 0)
data/systemtap-4.4/session.cxx:1172:21: [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).
download_dbinfo = atoi(optarg); //Enable, Set timeout to optarg
data/systemtap-4.4/session.cxx:1965: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 cwd[PATH_MAX];
data/systemtap-4.4/session.cxx:2092: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).
system_map.open(system_map_path.c_str(), ifstream::in);
data/systemtap-4.4/session.cxx:2101:18: [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).
system_map.open(system_map_path.c_str(), ifstream::in);
data/systemtap-4.4/session.cxx:2224: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 line[1024];
data/systemtap-4.4/setupdwfl.cxx:165:6: [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).
in.open(modulesdep.c_str());
data/systemtap-4.4/setupdwfl.cxx:746: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).
buildIDfile.open(kernel_buildID_path.c_str());
data/systemtap-4.4/setupdwfl.cxx:775:18: [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.
unsigned char data[8192];
data/systemtap-4.4/stap-serverd.cxx:143: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).
errfile.open (stapstderr.c_str (), ios_base::app);
data/systemtap-4.4/stap-serverd.cxx:864: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 host[HOST_NAME_MAX + 1];
data/systemtap-4.4/stap-serverd.cxx:1045: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 buffer[READ_BUFFER_SIZE];
data/systemtap-4.4/stap-serverd.cxx:1339:12: [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).
langfile.open(staplang.c_str());
data/systemtap-4.4/stap-serverd.cxx:1447: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.c_str());
data/systemtap-4.4/stap-serverd.cxx:1571:22: [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 ** argv = new char *[argc + 1];
data/systemtap-4.4/stap-serverd.cxx:1573:16: [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.
argv[i] = (char *)stapargv[i].c_str();
data/systemtap-4.4/stap-serverd.cxx:1622: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 tmpdir[PATH_MAX] = { '\0' };
data/systemtap-4.4/stap-serverd.cxx:1638:21: [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).
config_stream.open (config_path.c_str ());
data/systemtap-4.4/stap-serverd.cxx:1735:7: [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).
f = fopen (stapversion.c_str (), "w");
data/systemtap-4.4/stap-serverd.cxx:1804: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 stapargfile[PATH_MAX];
data/systemtap-4.4/stap-serverd.cxx:1826:17: [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).
argfile = fopen(stapargfile, "r");
data/systemtap-4.4/stap-serverd.cxx:1919: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 pattern[PATH_MAX];
data/systemtap-4.4/stap-serverd.cxx:2101: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).
dotfd = open (".", O_RDONLY);
data/systemtap-4.4/stap-serverd.cxx:2175:22: [2] (integer) atol:
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).
long uncomp_size = atol(toks[2].c_str());
data/systemtap-4.4/stap-serverd.cxx:2201: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 tmpdir[PATH_MAX];
data/systemtap-4.4/stap-serverd.cxx:2202: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 requestFileName[PATH_MAX];
data/systemtap-4.4/stap-serverd.cxx:2203: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 requestDirName[PATH_MAX];
data/systemtap-4.4/stap-serverd.cxx:2204: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 responseDirName[PATH_MAX];
data/systemtap-4.4/stap-serverd.cxx:2205: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 responseFileName[PATH_MAX];
data/systemtap-4.4/stap-serverd.cxx:2401: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[1024];
data/systemtap-4.4/stap-serverd.cxx:2469: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 buf[1024];
data/systemtap-4.4/stap-serverd.cxx:2732: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[1024];
data/systemtap-4.4/stapbpf/bpfinterp.cxx:172: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 _k[BPF_MAXSTRINGLEN_PLUS], _n[BPF_MAXSTRINGLEN_PLUS];
data/systemtap-4.4/stapbpf/bpfinterp.cxx:189:11: [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 _v[BPF_MAXSTRINGLEN_PLUS];
data/systemtap-4.4/stapbpf/bpfinterp.cxx:199:7: [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(kp, np, key_size);
data/systemtap-4.4/stapbpf/bpfinterp.cxx:298: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 _n[BPF_MAXSTRINGLEN_PLUS];
data/systemtap-4.4/stapbpf/bpfinterp.cxx:387: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 s[256]; // TODO: configure maximum length setting e.g. BPF_MAXSPRINTFLEN
data/systemtap-4.4/stapbpf/bpfinterp.cxx:720:7: [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(arg, msg_content, msg_size);
data/systemtap-4.4/stapbpf/libbpf.c:95:1: [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 bpf_log_buf[LOG_BUF_SIZE];
data/systemtap-4.4/stapbpf/libbpf.c:201:25: [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(*copy_mem, copy_start, len_first);
data/systemtap-4.4/stapbpf/libbpf.c:202:25: [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(*copy_mem + len_first, base, len_secnd);
data/systemtap-4.4/stapbpf/libbpf.h:22:8: [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.
extern char bpf_log_buf[LOG_BUF_SIZE];
data/systemtap-4.4/stapbpf/stapbpf.cxx:636: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 fifoname[PATH_MAX];
data/systemtap-4.4/stapbpf/stapbpf.cxx:669: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 path[PATH_MAX];
data/systemtap-4.4/stapbpf/stapbpf.cxx:729: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 tp_system[512];
data/systemtap-4.4/stapbpf/stapbpf.cxx:730: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 tp_name[512];
data/systemtap-4.4/stapbpf/stapbpf.cxx:746: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 tp_system[512];
data/systemtap-4.4/stapbpf/stapbpf.cxx:747: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 tp_name[512];
data/systemtap-4.4/stapbpf/stapbpf.cxx:787:12: [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 fd = open(DEBUGFS "uprobe_events", O_WRONLY);
data/systemtap-4.4/stapbpf/stapbpf.cxx:797: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 msgbuf[128];
data/systemtap-4.4/stapbpf/stapbpf.cxx:815:12: [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 fd = open(UPROBE_EVENTS, O_WRONLY);
data/systemtap-4.4/stapbpf/stapbpf.cxx:824: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 msgbuf[PATH_MAX];
data/systemtap-4.4/stapbpf/stapbpf.cxx:855: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 fnbuf[PATH_MAX];
data/systemtap-4.4/stapbpf/stapbpf.cxx:864:12: [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).
fd = open(fnbuf, O_RDONLY);
data/systemtap-4.4/stapbpf/stapbpf.cxx:872: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 msgbuf[128];
data/systemtap-4.4/stapbpf/stapbpf.cxx:883:29: [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).
uprobes[i].event_id = atoi(msgbuf);
data/systemtap-4.4/stapbpf/stapbpf.cxx:934:12: [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 fd = open(KPROBE_EVENTS, O_WRONLY);
data/systemtap-4.4/stapbpf/stapbpf.cxx:943: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 msgbuf[128];
data/systemtap-4.4/stapbpf/stapbpf.cxx:974: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 fnbuf[PATH_MAX];
data/systemtap-4.4/stapbpf/stapbpf.cxx:983:12: [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).
fd = open(fnbuf, O_RDONLY);
data/systemtap-4.4/stapbpf/stapbpf.cxx:991: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 msgbuf[128];
data/systemtap-4.4/stapbpf/stapbpf.cxx:1002:29: [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).
kprobes[i].event_id = atoi(msgbuf);
data/systemtap-4.4/stapbpf/stapbpf.cxx:1052:12: [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 fd = open(DEBUGFS "kprobe_events", O_WRONLY);
data/systemtap-4.4/stapbpf/stapbpf.cxx:1062: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 msgbuf[128];
data/systemtap-4.4/stapbpf/stapbpf.cxx:1097: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 fnbuf[PATH_MAX];
data/systemtap-4.4/stapbpf/stapbpf.cxx:1107:16: [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 fd = open(fnbuf, O_RDONLY);
data/systemtap-4.4/stapbpf/stapbpf.cxx:1120: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 msgbuf[128];
data/systemtap-4.4/stapbpf/stapbpf.cxx:1132:20: [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).
t.event_id = atoi(msgbuf);
data/systemtap-4.4/stapbpf/stapbpf.cxx:1416:12: [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 fd = open(module, O_RDONLY);
data/systemtap-4.4/stapbpf/stapbpf.cxx:1559:7: [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(&kernel_version, sh_data[version_idx]->d_buf, 4);
data/systemtap-4.4/stapbpf/stapbpf.cxx:1885:16: [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 fd = open(path, O_WRONLY);
data/systemtap-4.4/stapbpf/stapbpf.cxx:1927: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).
fd = open(path, O_WRONLY | O_NONBLOCK);
data/systemtap-4.4/stapbpf/stapbpf.cxx:1946:16: [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 fd = open(path, O_RDONLY);
data/systemtap-4.4/stapbpf/stapbpf.cxx:1965: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 buffer_feed[read_size];
data/systemtap-4.4/stapbpf/stapbpf.cxx:2112:15: [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).
target_pid = atoi(optarg);
data/systemtap-4.4/stapbpf/stapbpf.cxx:2116:13: [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).
output_f = fopen(optarg, "w");
data/systemtap-4.4/stapbpf/stapbpf.cxx:2146:10: [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).
kmsg = fopen("/dev/kmsg", "w");
data/systemtap-4.4/stapdyn/dynsdt.cxx:70:18: [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 size = atoi(size_str.c_str());
data/systemtap-4.4/stapdyn/dynsdt.cxx:95: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).
fd = open(file.c_str(), O_RDONLY);
data/systemtap-4.4/stapdyn/stapdyn.cxx:86:17: [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).
pid = atoi(optarg);
data/systemtap-4.4/staplog.c:338:9: [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).
filp = fopen(output_file, "w");
data/systemtap-4.4/staplog.c:355: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 *source, fname[MAX_FNAME + 1];
data/systemtap-4.4/stapregex-parse.cxx:509:10: [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).
return atoi (digits.c_str ());
data/systemtap-4.4/staprun/common.c:60:1: [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 *modoptions[MAXMODOPTIONS];
data/systemtap-4.4/staprun/common.c:64:8: [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.
static char path_buf[PATH_MAX];
data/systemtap-4.4/staprun/common.c:96:3: [2] (buffer) strcpy:
Does not check for buffer overflows when copying to destination [MS-banned]
(CWE-120). Consider using snprintf, strcpy_s, or strlcpy (warning: strncpy
easily misused). Risk is low because the source is a constant string.
strcpy(buf, "/dev/null");
data/systemtap-4.4/staprun/common.c:161:28: [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).
buffer_size = (unsigned)atoi(optarg);
data/systemtap-4.4/staprun/common.c:169:17: [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).
target_pid = atoi(optarg);
data/systemtap-4.4/staprun/common.c:172:31: [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).
target_namespaces_pid = atoi(optarg);
data/systemtap-4.4/staprun/common.c:205:23: [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).
relay_basedir_fd = atoi(optarg);
data/systemtap-4.4/staprun/common.c:246:55: [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).
reader_timeout_ms = (unsigned)atoi(optarg);
data/systemtap-4.4/staprun/common.c:270:23: [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).
monitor_interval = atoi(optarg);
data/systemtap-4.4/staprun/common.c:280: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 tmp[PATH_MAX];
data/systemtap-4.4/staprun/common.c:598: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).
return open(pathname, flags | O_CLOEXEC, mode);
data/systemtap-4.4/staprun/common.c:600:11: [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 fd = open(pathname, flags, mode);
data/systemtap-4.4/staprun/common.c:661: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 buf[1024];
data/systemtap-4.4/staprun/common.c:670:2: [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(buf, &type, sizeof (type));
data/systemtap-4.4/staprun/common.c:671:2: [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(&buf[sizeof (type)], data, len);
data/systemtap-4.4/staprun/ctl.c:19: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 buf[PATH_MAX] = ""; // the .ctl file name
data/systemtap-4.4/staprun/ctl.c:20: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 buf2[PATH_MAX] = ""; // other tmp stuff
data/systemtap-4.4/staprun/ctl.c:67:44: [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).
relay_basedir_fd = open (buf2, O_DIRECTORY | O_RDONLY);
data/systemtap-4.4/staprun/ctl.c:82:44: [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).
relay_basedir_fd = open (buf2, O_DIRECTORY | O_RDONLY);
data/systemtap-4.4/staprun/mainloop.c:265: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 *sh_c_argv[4] = { NULL, NULL, NULL, NULL };
data/systemtap-4.4/staprun/mainloop.c:498:11: [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).
ret = open("/dev/null", O_RDWR);
data/systemtap-4.4/staprun/mainloop.c:634: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 data[8192];
data/systemtap-4.4/staprun/monitor.c:26: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 *lines[MAX_HISTORY]; /* each malloc/strdup'd(). */
data/systemtap-4.4/staprun/monitor.c:53:8: [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.
static char probe[MAX_INDEX_LEN];
data/systemtap-4.4/staprun/monitor.c:168: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 path[PATH_MAX];
data/systemtap-4.4/staprun/monitor.c:174:14: [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).
if (!(fp = fopen(path, "w")))
data/systemtap-4.4/staprun/monitor.c:302: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 path[PATH_MAX];
data/systemtap-4.4/staprun/monitor.c:338: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 json[MAX_DATA];
data/systemtap-4.4/staprun/monitor.c:344:16: [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).
monitor_fp = fopen(path, "r");
data/systemtap-4.4/staprun/monitor.c:362: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 monitor_str[MAX_COLS];
data/systemtap-4.4/staprun/monitor.c:363: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 monitor_out[MAX_COLS];
data/systemtap-4.4/staprun/monitor.c:673: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 path[PATH_MAX];
data/systemtap-4.4/staprun/monitor.c:679:22: [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).
while ((fd = open(path, O_WRONLY)) == -1) {
data/systemtap-4.4/staprun/relay.c:76: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 buf[PATH_MAX];
data/systemtap-4.4/staprun/relay.c:127: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 buf[131072];
data/systemtap-4.4/staprun/relay.c:304: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 rqbuf[128];
data/systemtap-4.4/staprun/relay.c:305: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 buf[PATH_MAX];
data/systemtap-4.4/staprun/relay.c:387:6: [2] (buffer) strcpy:
Does not check for buffer overflows when copying to destination [MS-banned]
(CWE-120). Consider using snprintf, strcpy_s, or strlcpy (warning: strncpy
easily misused). Risk is low because the source is a constant string.
strcpy(buf, "/dev/null");
data/systemtap-4.4/staprun/relay_old.c:20:8: [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.
static char *relay_buffer[NR_CPUS];
data/systemtap-4.4/staprun/relay_old.c:84: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 buf[PATH_MAX];
data/systemtap-4.4/staprun/relay_old.c:110:28: [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).
if((percpu_tmpfile[cpu] = fopen(buf, "w+")) == NULL) {
data/systemtap-4.4/staprun/relay_old.c:128: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 tmp[PATH_MAX];
data/systemtap-4.4/staprun/relay_old.c:164:4: [2] (buffer) strcpy:
Does not check for buffer overflows when copying to destination [MS-banned]
(CWE-120). Consider using snprintf, strcpy_s, or strlcpy (warning: strncpy
easily misused). Risk is low because the source is a constant string.
strcpy(tmp, "/dev/null");
data/systemtap-4.4/staprun/relay_old.c:180:28: [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).
if((percpu_tmpfile[cpu] = fopen(tmp, "w+")) == NULL) {
data/systemtap-4.4/staprun/relay_old.c:401: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 relay_filebase[PATH_MAX], proc_filebase[PATH_MAX];
data/systemtap-4.4/staprun/relay_old.c:417: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 tmp[PATH_MAX];
data/systemtap-4.4/staprun/stap_merge.c:70:11: [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).
fp[i] = fopen(argv[optind++], "r");
data/systemtap-4.4/staprun/stap_merge.c:86:9: [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).
ofp = fopen(outfile_name, "w");
data/systemtap-4.4/staprun/staprun.c:147: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 *argv[10];
data/systemtap-4.4/staprun/staprun.c:148: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 runtimeko[2048];
data/systemtap-4.4/staprun/staprun.c:181: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 special_options[128];
data/systemtap-4.4/staprun/staprun.c:191:24: [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).
fips_mode_fd = open("/proc/sys/crypto/fips_enabled", O_RDONLY);
data/systemtap-4.4/staprun/staprun.c:318: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).
fd = open (proc_kprobes, O_RDONLY);
data/systemtap-4.4/staprun/staprun.c:326: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).
fd = open (proc_kprobes, O_WRONLY);
data/systemtap-4.4/staprun/staprun.c:365: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).
fd = open (proc_kptr, O_RDONLY);
data/systemtap-4.4/staprun/staprun.c:373: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).
fd = open (proc_kptr, O_WRONLY);
data/systemtap-4.4/staprun/staprun.c:511: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 verbose_level[33];
data/systemtap-4.4/staprun/staprun.c:512:2: [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(verbose_level, "%d", verbose);
data/systemtap-4.4/staprun/staprun.c:613:14: [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).
kallsyms = fopen ("/proc/kallsyms", "r");
data/systemtap-4.4/staprun/staprun.c:738:17: [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).
secfile = fopen (module_section_file, "r");
data/systemtap-4.4/staprun/staprun.h:257:8: [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.
extern char *modoptions[MAXMODOPTIONS];
data/systemtap-4.4/staprun/staprun_funcs.c:66: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 module_realpath[PATH_MAX];
data/systemtap-4.4/staprun/staprun_funcs.c:114: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).
module_fd = open(module_realpath, O_RDONLY);
data/systemtap-4.4/staprun/staprun_funcs.c:252: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 newname[MODULE_NAME_LEN];
data/systemtap-4.4/staprun/staprun_funcs.c:424: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 signature_realpath[PATH_MAX];
data/systemtap-4.4/staprun/staprun_funcs.c:457: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 staplib_dir_path[PATH_MAX];
data/systemtap-4.4/staprun/staprun_funcs.c:458: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 staplib_dir_realpath[PATH_MAX];
data/systemtap-4.4/staprun/staprun_funcs.c:777:26: [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).
if (env_id && setreuid(atoi(env_id), -1))
data/systemtap-4.4/staprun/staprun_funcs.c:783:26: [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).
if (env_id && setregid(atoi(env_id), -1))
data/systemtap-4.4/staprun/stapsh.c:113:8: [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.
static char tmpdir[FILENAME_MAX] = "";
data/systemtap-4.4/staprun/stapsh.c:422:12: [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).
size = atoi(arg);
data/systemtap-4.4/staprun/stapsh.c:440:13: [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* f = fopen(name, "w");
data/systemtap-4.4/staprun/stapsh.c:445: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 buf[1024];
data/systemtap-4.4/staprun/stapsh.c:654: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 command[4096];
data/systemtap-4.4/staprun/stapsh.c:693: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[4096];
data/systemtap-4.4/staprun/stapsh.c:727:27: [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).
listening_port_fd = open(listening_port, O_RDWR);
data/systemtap-4.4/stapvirt.c:725: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 uuid[VIR_UUID_STRING_BUFLEN];
data/systemtap-4.4/stapvirt.c:961: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 termbuf[1024]; /* term to st */
data/systemtap-4.4/stapvirt.c:963: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 stbuf[1024]; /* st to term */
data/systemtap-4.4/stringtable.cxx:81:8: [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.
static char chartable[256];
data/systemtap-4.4/tapset-mark.cxx:99:16: [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 argnum = atoi (argnum_s.c_str());
data/systemtap-4.4/tapset-mark.cxx:662:22: [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).
module_markers.open(module_markers_path.c_str(), ifstream::in);
data/systemtap-4.4/tapsets.cxx:4976:24: [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 fd = open(cached_module.c_str(), O_RDONLY);
data/systemtap-4.4/testsuite/systemtap.base/atcast-index_1.c:2: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 arr[3];
data/systemtap-4.4/testsuite/systemtap.base/atcast-index_2.c:2: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 arr[5];
data/systemtap-4.4/testsuite/systemtap.base/gtod.c:11:22: [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).
if (argc == 2) us = atoi(argv[1]);
data/systemtap-4.4/testsuite/systemtap.base/plt.c:39:19: [2] (buffer) memcpy:
Does not check for buffer overflows when copying to destination (CWE-120).
Make sure destination can always hold the source data.
return (char *) memcpy (value, ptr, len);
data/systemtap-4.4/testsuite/systemtap.base/plt.c:48:10: [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).
return open (name, flags) && end == name;
data/systemtap-4.4/testsuite/systemtap.base/plt.c:60:10: [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).
desc = open (name, flags);
data/systemtap-4.4/testsuite/systemtap.base/plt.c:227: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 buffer[SIZE];
data/systemtap-4.4/testsuite/systemtap.base/pthread_stacks.c:50:18: [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).
numthreads = atoi(argv[1]);
data/systemtap-4.4/testsuite/systemtap.base/pthread_stacks.c:54:17: [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).
stacksize = atoi(argv[2]);
data/systemtap-4.4/testsuite/systemtap.base/set_user.c:8: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 cbuf[64];
data/systemtap-4.4/testsuite/systemtap.base/tlserrno.c:11:12: [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).
infile = fopen (input_file, "r");
data/systemtap-4.4/testsuite/systemtap.base/utrace_p5_multi.c:41:11: [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 fd = open("/dev/null", O_RDONLY);
data/systemtap-4.4/testsuite/systemtap.base/utrace_syscall_args.c:16:7: [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).
fd = open("foobar", O_WRONLY|O_CREAT|O_TRUNC, 0600);
data/systemtap-4.4/testsuite/systemtap.base/utrace_syscall_args.c:21:7: [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).
fd = open("foobar", O_RDONLY);
data/systemtap-4.4/testsuite/systemtap.clone/dtrace_vfork_parent.c:40:11: [2] (race) vfork:
On some old systems, vfork() permits race conditions, and it's very
difficult to use correctly (CWE-362). Use fork() instead.
pid = vfork();
data/systemtap-4.4/testsuite/systemtap.context/fib.c:22:7: [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).
x = atoi(argv[1]);
data/systemtap-4.4/testsuite/systemtap.printf/memory1_module.c:26:8: [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.
static char buffer[100] = "";
data/systemtap-4.4/testsuite/systemtap.printf/memory1_module.c:31:2: [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, string, bytes);
data/systemtap-4.4/testsuite/systemtap.printf/memory1_module.c:46: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 tmp[100];
data/systemtap-4.4/testsuite/systemtap.printf/print_user_buffer.c:5:4: [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[7] = "foobar\n";
data/systemtap-4.4/testsuite/systemtap.printf/print_user_buffer.c:8:4: [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 buffer2[2] = {'\0','\n'};
data/systemtap-4.4/testsuite/systemtap.speculate/speculate.c:13:8: [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.
static char buf1[MAXSIZE];
data/systemtap-4.4/testsuite/systemtap.speculate/speculate.c:14:8: [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.
static char buf2[MAXSIZE];
data/systemtap-4.4/testsuite/systemtap.speculate/speculate.c:18:13: [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 fbad = open("/tmp/junky_bad", O_CREAT|O_RDWR, 0660);
data/systemtap-4.4/testsuite/systemtap.speculate/speculate.c:19: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).
int fokay = open("/tmp/junky_good", O_CREAT|O_RDWR, 0660);
data/systemtap-4.4/testsuite/systemtap.syscall/accept.c:31: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).
fd_null = open("/dev/null", O_WRONLY);
data/systemtap-4.4/testsuite/systemtap.syscall/accept4.c:35: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).
fd_null = open("/dev/null", O_WRONLY);
data/systemtap-4.4/testsuite/systemtap.syscall/aio.c:42: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 data[9];
data/systemtap-4.4/testsuite/systemtap.syscall/aio.c:47:7: [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).
fd = open("testfile", O_RDWR | O_CREAT, 0644);
data/systemtap-4.4/testsuite/systemtap.syscall/aio.c:59:2: [2] (buffer) strcpy:
Does not check for buffer overflows when copying to destination [MS-banned]
(CWE-120). Consider using snprintf, strcpy_s, or strlcpy (warning: strncpy
easily misused). Risk is low because the source is a constant string.
strcpy(data, "testdata");
data/systemtap-4.4/testsuite/systemtap.syscall/arg_write/dcookie.c:56: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[LENGTH];
data/systemtap-4.4/testsuite/systemtap.syscall/arg_write/dir.c:17:9: [2] (buffer) strcpy:
Does not check for buffer overflows when copying to destination [MS-banned]
(CWE-120). Consider using snprintf, strcpy_s, or strlcpy (warning: strncpy
easily misused). Risk is low because the source is a constant string.
strcpy(s, "STAPTEST");
data/systemtap-4.4/testsuite/systemtap.syscall/arg_write/dir.c:38:9: [2] (buffer) strcpy:
Does not check for buffer overflows when copying to destination [MS-banned]
(CWE-120). Consider using snprintf, strcpy_s, or strlcpy (warning: strncpy
easily misused). Risk is low because the source is a constant string.
strcpy(s, "STAPTEST");
data/systemtap-4.4/testsuite/systemtap.syscall/arg_write/dir.c:39:12: [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 ret = open(s, flags + 1);
data/systemtap-4.4/testsuite/systemtap.syscall/bind.c:14: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[1024];
data/systemtap-4.4/testsuite/systemtap.syscall/bind.c:44:13: [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).
fd_null = open("/dev/null", O_WRONLY);
data/systemtap-4.4/testsuite/systemtap.syscall/chmod.c:25: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).
fd = open("foobar",O_WRONLY|O_CREAT, 0666);
data/systemtap-4.4/testsuite/systemtap.syscall/connect.c:108: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).
fd_null = open("/dev/null", O_WRONLY);
data/systemtap-4.4/testsuite/systemtap.syscall/copy_file_range.c:35:13: [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).
fd_in = open("foobar", O_WRONLY|O_CREAT, 0666);
data/systemtap-4.4/testsuite/systemtap.syscall/copy_file_range.c:40:13: [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).
fd_in = open("foobar", O_RDONLY);
data/systemtap-4.4/testsuite/systemtap.syscall/copy_file_range.c:41: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).
fd_out = open("foobar2", O_WRONLY|O_CREAT, 0666);
data/systemtap-4.4/testsuite/systemtap.syscall/dcookie.c:47: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[LENGTH];
data/systemtap-4.4/testsuite/systemtap.syscall/dir.c:39: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).
fd = open("foobar", O_RDONLY);
data/systemtap-4.4/testsuite/systemtap.syscall/dir.c:64: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).
fd = open(".", O_RDONLY);
data/systemtap-4.4/testsuite/systemtap.syscall/domainname.c:8:8: [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.
static char domain_name[MAX_NAME_LEN];
data/systemtap-4.4/testsuite/systemtap.syscall/fadvise64.c:49:10: [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).
fd = open("foobar", O_WRONLY|O_CREAT, S_IRWXU);
data/systemtap-4.4/testsuite/systemtap.syscall/fallocate.c:42:10: [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).
fd = open("foo", O_RDWR | O_CREAT, 0700);
data/systemtap-4.4/testsuite/systemtap.syscall/fanotify.c:27:8: [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.
static char fname[BUF_SIZE] = "testfile";
data/systemtap-4.4/testsuite/systemtap.syscall/fanotify.c:30:8: [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.
static char event_buf[EVENT_BUF_LEN];
data/systemtap-4.4/testsuite/systemtap.syscall/fanotify.c:48:10: [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).
fd = open(fname, O_WRONLY);
data/systemtap-4.4/testsuite/systemtap.syscall/flock.c:10:1: [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 filename[100];
data/systemtap-4.4/testsuite/systemtap.syscall/flock.c:14:5: [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(filename, "flock-tst.%d", getpid());
data/systemtap-4.4/testsuite/systemtap.syscall/fxattr.c:18: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[1024];
data/systemtap-4.4/testsuite/systemtap.syscall/getcpu.c:18: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[1024 * 1024];
data/systemtap-4.4/testsuite/systemtap.syscall/getdents.c:32:10: [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).
fd = open(".", O_RDONLY);
data/systemtap-4.4/testsuite/systemtap.syscall/getpeername.c:29: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).
fd_null = open("/dev/null", O_WRONLY);
data/systemtap-4.4/testsuite/systemtap.syscall/getrandom.c:27: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 i[5] = {0};
data/systemtap-4.4/testsuite/systemtap.syscall/getrandom.c:28: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 k[5] = {0};
data/systemtap-4.4/testsuite/systemtap.syscall/getsockname.c:30: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).
fd_null = open("/dev/null", O_WRONLY);
data/systemtap-4.4/testsuite/systemtap.syscall/getsockopt.c:33: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).
fd_null = open("/dev/null", O_WRONLY);
data/systemtap-4.4/testsuite/systemtap.syscall/hostname.c:15: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 orig_hname[HLEN];
data/systemtap-4.4/testsuite/systemtap.syscall/ioctl.c:14:10: [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).
fd = open(fname, O_RDWR);
data/systemtap-4.4/testsuite/systemtap.syscall/kcmp.c:33:24: [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).
unsigned long fd = open("kcmp_testfile", O_CREAT);
data/systemtap-4.4/testsuite/systemtap.syscall/kexec_load.c:112:10: [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).
fd = open("/dev/null", O_RDONLY);
data/systemtap-4.4/testsuite/systemtap.syscall/link.c:22: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[128];
data/systemtap-4.4/testsuite/systemtap.syscall/link.c:24: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).
fd = open("foobar",O_WRONLY|O_CREAT, S_IRWXU);
data/systemtap-4.4/testsuite/systemtap.syscall/listen.c:22:13: [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).
fd_null = open("/dev/null", O_WRONLY);
data/systemtap-4.4/testsuite/systemtap.syscall/lseek.c:20: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], buf1[32], buf2[32], buf3[32];
data/systemtap-4.4/testsuite/systemtap.syscall/lseek.c:24: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).
fd = open("foobar1", O_WRONLY|O_CREAT, 0666);
data/systemtap-4.4/testsuite/systemtap.syscall/lxattr.c:18: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[1024];
data/systemtap-4.4/testsuite/systemtap.syscall/madvise.c:15: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 filename[PATH_MAX];
data/systemtap-4.4/testsuite/systemtap.syscall/madvise.c:22:10: [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).
fd = open(filename, O_RDWR | O_CREAT, 0664);
data/systemtap-4.4/testsuite/systemtap.syscall/mmap.c:31:7: [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).
fd = open("foobar",O_WRONLY|O_CREAT|O_TRUNC, 0600);
data/systemtap-4.4/testsuite/systemtap.syscall/mmap.c:43:7: [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).
fd = open("foobar", O_RDONLY);
data/systemtap-4.4/testsuite/systemtap.syscall/module.c:53: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).
fd_null = open("/dev/null", O_RDONLY);
data/systemtap-4.4/testsuite/systemtap.syscall/mq.c:47: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[MSG_LEN + 1];
data/systemtap-4.4/testsuite/systemtap.syscall/msg_queue.c:13: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 mtext[MSGTXTLEN];
data/systemtap-4.4/testsuite/systemtap.syscall/msg_queue.c:29:5: [2] (buffer) strcpy:
Does not check for buffer overflows when copying to destination [MS-banned]
(CWE-120). Consider using snprintf, strcpy_s, or strlcpy (warning: strncpy
easily misused). Risk is low because the source is a constant string.
strcpy(msg.mtext, "a text msg...\n");
data/systemtap-4.4/testsuite/systemtap.syscall/openclose.c:46: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).
fd1 = open("foobar2",O_WRONLY|O_CREAT, S_IRWXU);
data/systemtap-4.4/testsuite/systemtap.syscall/openclose.c:58: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).
fd1 = open("foobar2",O_RDONLY);
data/systemtap-4.4/testsuite/systemtap.syscall/openclose.c:70: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).
fd1 = open("foobar2",O_RDWR);
data/systemtap-4.4/testsuite/systemtap.syscall/openclose.c:82: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).
fd1 = open("foobar2",O_APPEND|O_WRONLY);
data/systemtap-4.4/testsuite/systemtap.syscall/openclose.c:94: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).
fd1 = open("foobar2",O_DIRECT|O_RDWR);
data/systemtap-4.4/testsuite/systemtap.syscall/openclose.c:106: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).
fd1 = open("foobar2",O_NOATIME|O_SYNC|O_RDWR);
data/systemtap-4.4/testsuite/systemtap.syscall/openclose.c:119: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).
fd1 = open("/",O_WRONLY);
data/systemtap-4.4/testsuite/systemtap.syscall/openclose.c:131: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).
fd1 = open("foobar2",O_WRONLY|O_CREAT|O_EXCL, S_IRWXU);
data/systemtap-4.4/testsuite/systemtap.syscall/openclose.c:139:3: [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).
open((char *)-1, O_WRONLY|O_CREAT|O_EXCL, S_IRWXU);
data/systemtap-4.4/testsuite/systemtap.syscall/openclose.c:158:3: [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).
open("foobarX", -1, S_IRWXU);
data/systemtap-4.4/testsuite/systemtap.syscall/openclose.c:161: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).
fd1 = open("foobarY", O_WRONLY|O_CREAT, -1);
data/systemtap-4.4/testsuite/systemtap.syscall/prctl.c:18: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[1024];
data/systemtap-4.4/testsuite/systemtap.syscall/pread.c:25: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], buf1[32], buf2[32], buf3[32];
data/systemtap-4.4/testsuite/systemtap.syscall/pread.c:27: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).
fd = open("foobar1", O_WRONLY|O_CREAT, 0666);
data/systemtap-4.4/testsuite/systemtap.syscall/pread.c: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).
fd = open("foobar1", O_RDONLY);
data/systemtap-4.4/testsuite/systemtap.syscall/preadv.c:40: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/systemtap-4.4/testsuite/systemtap.syscall/preadv.c:42: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).
fd = open("foobar1", O_WRONLY|O_CREAT, 0666);
data/systemtap-4.4/testsuite/systemtap.syscall/preadv.c:51: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).
fd = open("foobar1", O_RDONLY);
data/systemtap-4.4/testsuite/systemtap.syscall/preadv.c:97: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).
fd = open("dir1", O_RDONLY);
data/systemtap-4.4/testsuite/systemtap.syscall/preadv.c:116: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).
fd = open("foobar1", O_WRONLY|O_CREAT, 0666);
data/systemtap-4.4/testsuite/systemtap.syscall/preadv.c:124: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).
fd = open("foobar1", O_RDONLY);
data/systemtap-4.4/testsuite/systemtap.syscall/process_vm.c:12:1: [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 child_buffer[1024];
data/systemtap-4.4/testsuite/systemtap.syscall/process_vm.c:16:5: [2] (buffer) strcpy:
Does not check for buffer overflows when copying to destination [MS-banned]
(CWE-120). Consider using snprintf, strcpy_s, or strlcpy (warning: strncpy
easily misused). Risk is low because the source is a constant string.
strcpy(child_buffer, "Hello there, we're in the child.");
data/systemtap-4.4/testsuite/systemtap.syscall/process_vm.c:28: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[1024];
data/systemtap-4.4/testsuite/systemtap.syscall/process_vm.c:52:5: [2] (buffer) strcpy:
Does not check for buffer overflows when copying to destination [MS-banned]
(CWE-120). Consider using snprintf, strcpy_s, or strlcpy (warning: strncpy
easily misused). Risk is low because the source is a constant string.
strcpy(buffer, "From parent");
data/systemtap-4.4/testsuite/systemtap.syscall/ptrace.c:90:14: [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.
unsigned char regbuf[8192];
data/systemtap-4.4/testsuite/systemtap.syscall/pwrite.c:25: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], buf1[32], buf2[32], buf3[32];
data/systemtap-4.4/testsuite/systemtap.syscall/pwrite.c:27: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).
fd = open("foobar1", O_WRONLY|O_CREAT, 0666);
data/systemtap-4.4/testsuite/systemtap.syscall/pwritev.c:40: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/systemtap-4.4/testsuite/systemtap.syscall/pwritev.c:42: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).
fd = open("foobar1", O_WRONLY|O_CREAT, 0666);
data/systemtap-4.4/testsuite/systemtap.syscall/pwritev.c:89: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).
fd = open("foobar1", O_WRONLY|O_CREAT, 0666);
data/systemtap-4.4/testsuite/systemtap.syscall/readahead.c:11: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 tempname[17] = "readahead_XXXXXX";
data/systemtap-4.4/testsuite/systemtap.syscall/readahead.c:13: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(tempname);
data/systemtap-4.4/testsuite/systemtap.syscall/readdir.c:26:10: [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).
fd = open(".", O_RDONLY);
data/systemtap-4.4/testsuite/systemtap.syscall/readv.c:17: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/systemtap-4.4/testsuite/systemtap.syscall/readv.c:19: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).
fd = open("foobar1", O_WRONLY|O_CREAT, 0666);
data/systemtap-4.4/testsuite/systemtap.syscall/readv.c:28: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).
fd = open("foobar1", O_RDONLY);
data/systemtap-4.4/testsuite/systemtap.syscall/readv.c:70: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).
fd = open("dir1", O_RDONLY);
data/systemtap-4.4/testsuite/systemtap.syscall/readwrite.c:20: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], buf1[32], buf2[32], buf3[32];
data/systemtap-4.4/testsuite/systemtap.syscall/readwrite.c:22: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).
fd = open("foobar1", O_WRONLY|O_CREAT, 0666);
data/systemtap-4.4/testsuite/systemtap.syscall/readwrite.c:52: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).
fd = open("foobar1", O_RDONLY);
data/systemtap-4.4/testsuite/systemtap.syscall/recv.c:95: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[1024];
data/systemtap-4.4/testsuite/systemtap.syscall/recv.c:119: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).
fd_null = open("/dev/null", O_WRONLY);
data/systemtap-4.4/testsuite/systemtap.syscall/recvfrom.c:96: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[1024];
data/systemtap-4.4/testsuite/systemtap.syscall/recvfrom.c:117: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).
fd_null = open("/dev/null", O_WRONLY);
data/systemtap-4.4/testsuite/systemtap.syscall/recvmmsg.c:88: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 rbuf[1024];
data/systemtap-4.4/testsuite/systemtap.syscall/recvmmsg.c:142: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[2][1024];
data/systemtap-4.4/testsuite/systemtap.syscall/recvmmsg.c:149: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 tmpsunpath[1024];
data/systemtap-4.4/testsuite/systemtap.syscall/recvmmsg.c:157:11: [2] (buffer) strcpy:
Does not check for buffer overflows when copying to destination [MS-banned]
(CWE-120). Consider using snprintf, strcpy_s, or strlcpy (warning: strncpy
easily misused). Risk is low because the source is a constant string.
(void)strcpy(tmpsunpath, "udsockXXXXXX");
data/systemtap-4.4/testsuite/systemtap.syscall/recvmmsg.c:158:9: [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).
s = mkstemp(tmpsunpath);
data/systemtap-4.4/testsuite/systemtap.syscall/recvmmsg.c:186: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).
fd_null = open("/dev/null", O_WRONLY);
data/systemtap-4.4/testsuite/systemtap.syscall/recvmsg.c:87: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 rbuf[1024];
data/systemtap-4.4/testsuite/systemtap.syscall/recvmsg.c:141: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[1024];
data/systemtap-4.4/testsuite/systemtap.syscall/recvmsg.c:148: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 tmpsunpath[1024];
data/systemtap-4.4/testsuite/systemtap.syscall/recvmsg.c:155:11: [2] (buffer) strcpy:
Does not check for buffer overflows when copying to destination [MS-banned]
(CWE-120). Consider using snprintf, strcpy_s, or strlcpy (warning: strncpy
easily misused). Risk is low because the source is a constant string.
(void)strcpy(tmpsunpath, "udsockXXXXXX");
data/systemtap-4.4/testsuite/systemtap.syscall/recvmsg.c:156:9: [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).
s = mkstemp(tmpsunpath);
data/systemtap-4.4/testsuite/systemtap.syscall/recvmsg.c:184: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).
fd_null = open("/dev/null", O_WRONLY);
data/systemtap-4.4/testsuite/systemtap.syscall/remap_file_pages.c:18:10: [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).
fd = open(f, O_RDWR|O_CREAT, 0777);
data/systemtap-4.4/testsuite/systemtap.syscall/send.c:24: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[1024];
data/systemtap-4.4/testsuite/systemtap.syscall/send.c:94: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[1024];
data/systemtap-4.4/testsuite/systemtap.syscall/send.c:111: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).
fd_null = open("/dev/null", O_WRONLY);
data/systemtap-4.4/testsuite/systemtap.syscall/sendfile.c:17: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 buff[22]; // Note below 22 == EINVAL
data/systemtap-4.4/testsuite/systemtap.syscall/sendfile.c:27:12: [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).
read_fd = open ("foobar", O_RDONLY);
data/systemtap-4.4/testsuite/systemtap.syscall/sendmmsg.c:36: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[1024];
data/systemtap-4.4/testsuite/systemtap.syscall/sendmmsg.c:107: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[2][1024];
data/systemtap-4.4/testsuite/systemtap.syscall/sendmmsg.c:132: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).
fd_null = open("/dev/null", O_WRONLY);
data/systemtap-4.4/testsuite/systemtap.syscall/sendmsg.c:24: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[1024];
data/systemtap-4.4/testsuite/systemtap.syscall/sendmsg.c:94: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[1024];
data/systemtap-4.4/testsuite/systemtap.syscall/sendmsg.c:118: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).
fd_null = open("/dev/null", O_WRONLY);
data/systemtap-4.4/testsuite/systemtap.syscall/sendto.c:24: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[1024];
data/systemtap-4.4/testsuite/systemtap.syscall/sendto.c:94: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[1024];
data/systemtap-4.4/testsuite/systemtap.syscall/sendto.c:107: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).
fd_null = open("/dev/null", O_WRONLY);
data/systemtap-4.4/testsuite/systemtap.syscall/setns.c:24:5: [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(fn, "/proc/%d/ns/pid\0", getpid());
data/systemtap-4.4/testsuite/systemtap.syscall/setns.c:25:10: [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).
fd = open(fn, O_RDONLY);
data/systemtap-4.4/testsuite/systemtap.syscall/setsockopt.c:33: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).
fd_null = open("/dev/null", O_WRONLY);
data/systemtap-4.4/testsuite/systemtap.syscall/shutdown.c:15: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[1024];
data/systemtap-4.4/testsuite/systemtap.syscall/shutdown.c:25:13: [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).
fd_null = open("/dev/null", O_WRONLY);
data/systemtap-4.4/testsuite/systemtap.syscall/stat.c:50: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 cwd[128];
data/systemtap-4.4/testsuite/systemtap.syscall/statfs.c:64:10: [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).
fd = open("abc", O_WRONLY|O_CREAT, S_IRWXU);
data/systemtap-4.4/testsuite/systemtap.syscall/sysfs.c:10: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[1024];
data/systemtap-4.4/testsuite/systemtap.syscall/syslog.c:8: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[1024];
data/systemtap-4.4/testsuite/systemtap.syscall/tee.c:15:12: [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.
static char buffer[TEST_BLOCK_SIZE];
data/systemtap-4.4/testsuite/systemtap.syscall/vforkwait.c:14:10: [2] (race) vfork:
On some old systems, vfork() permits race conditions, and it's very
difficult to use correctly (CWE-362). Use fork() instead.
child = vfork();
data/systemtap-4.4/testsuite/systemtap.syscall/wait4.c:15:16: [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 *fp = fopen("/proc/sys/kernel/pid_max", "r");
data/systemtap-4.4/testsuite/systemtap.syscall/writev.c:17: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/systemtap-4.4/testsuite/systemtap.syscall/writev.c:19: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).
fd = open("foobar1", O_WRONLY|O_CREAT, 0666);
data/systemtap-4.4/testsuite/systemtap.syscall/xattr.c:18: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[1024];
data/systemtap-4.4/util.cxx:131: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[10240];
data/systemtap-4.4/util.cxx:141: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).
fd1 = open(src.c_str(), O_RDONLY);
data/systemtap-4.4/util.cxx:148:9: [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).
fd2 = mkstemp(tmp_name);
data/systemtap-4.4/util.cxx:886: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 const * argv[args.size() + 1];
data/systemtap-4.4/util.cxx:1271:4: [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 b[32];
data/systemtap-4.4/util.cxx:1272:4: [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 (b, "_%x_", (unsigned int) this_char);
data/systemtap-4.4/util.cxx:1458: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[1024]; // This really should be enough for anybody...
data/systemtap-4.4/util.cxx:1813: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("/etc/os-release");
data/systemtap-4.4/bpf-translate.cxx:4180:28: [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 script_name_len = strlen(script_name.c_str());
data/systemtap-4.4/client-http.cxx:593:15: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
ssize_t n = read (fd, buf.data, sizeof buf);
data/systemtap-4.4/doc/SystemTap_Tapset_Reference/docproc.c:100:4: [1] (buffer) strncat:
Easily used incorrectly (e.g., incorrectly computing the correct maximum
size to add) [MS-banned] (CWE-120). Consider strcat_s, strlcat, snprintf,
or automatically resizing strings.
strncat(real_filename, KERNELDOCPATH KERNELDOC,
data/systemtap-4.4/doc/SystemTap_Tapset_Reference/docproc.c:101:17: [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).
PATH_MAX - strlen(real_filename) - 1);
data/systemtap-4.4/doc/SystemTap_Tapset_Reference/docproc.c:181:3: [1] (buffer) strncat:
Easily used incorrectly (e.g., incorrectly computing the correct maximum
size to add) [MS-banned] (CWE-120). Consider strcat_s, strlcat, snprintf,
or automatically resizing strings.
strncat(real_filename, filename,
data/systemtap-4.4/doc/SystemTap_Tapset_Reference/docproc.c:182:16: [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).
PATH_MAX - strlen(real_filename) - 1);
data/systemtap-4.4/dwflpp.cxx:1390:20: [1] (buffer) sscanf:
It's unclear if the %s limit in the format string is small enough
(CWE-120). Check that the limit is sufficiently small, or use a different
input function.
int nf = sscanf (line, "%255s => %255s (0x%lx)",
data/systemtap-4.4/dwflpp.cxx:1395:20: [1] (buffer) sscanf:
It's unclear if the %s limit in the format string is small enough
(CWE-120). Check that the limit is sufficiently small, or use a different
input function.
nf = sscanf (line, " %255s (0x%lx)", shlib, &addr);
data/systemtap-4.4/elaborate.cxx:1592:26: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
if (! vcv_cond.read.empty()) { // insert only if nonempty
data/systemtap-4.4/elaborate.cxx:1593:50: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
vars_read_in_cond[p].insert(vcv_cond.read.begin(),
data/systemtap-4.4/elaborate.cxx:1594:50: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
vcv_cond.read.end());
data/systemtap-4.4/elaborate.cxx:2077:16: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
if ((vut.read.find (l) != vut.read.end()
data/systemtap-4.4/elaborate.cxx:2077:37: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
if ((vut.read.find (l) != vut.read.end()
data/systemtap-4.4/elaborate.cxx:2220:11: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
vut.read.insert (l);
data/systemtap-4.4/elaborate.cxx:2820: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).
pos += strlen("/* pragma:read:");
data/systemtap-4.4/elaborate.cxx:2840: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).
pos += strlen("/* pragma:write:");
data/systemtap-4.4/elaborate.cxx:2874: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).
pos += strlen("/* pragma:read:");
data/systemtap-4.4/elaborate.cxx:2894: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).
pos += strlen("/* pragma:write:");
data/systemtap-4.4/elaborate.cxx:3381:17: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
if (vut.read.find (l) == vut.read.end() &&
data/systemtap-4.4/elaborate.cxx:3381:38: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
if (vut.read.find (l) == vut.read.end() &&
data/systemtap-4.4/elaborate.cxx:3428:19: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
if (vut.read.find (l) == vut.read.end() &&
data/systemtap-4.4/elaborate.cxx:3428:40: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
if (vut.read.find (l) == vut.read.end() &&
data/systemtap-4.4/elaborate.cxx:3473:15: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
if (vut.read.find (l) == vut.read.end() &&
data/systemtap-4.4/elaborate.cxx:3473:36: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
if (vut.read.find (l) == vut.read.end() &&
data/systemtap-4.4/elaborate.cxx:3617:15: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
if (vut.read.find(leftvar) == vut.read.end()) // var never read?
data/systemtap-4.4/elaborate.cxx:3617:41: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
if (vut.read.find(leftvar) == vut.read.end()) // var never read?
data/systemtap-4.4/elaborate.cxx:3667:15: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
if (vut.read.find(errvar) == vut.read.end()) // never read?
data/systemtap-4.4/elaborate.cxx:3667:40: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
if (vut.read.find(errvar) == vut.read.end()) // never read?
data/systemtap-4.4/elaborate.cxx:4646:14: [1] (buffer) mismatch:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
ti.mismatch(e);
data/systemtap-4.4/elaborate.cxx:4683:14: [1] (buffer) mismatch:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
ti.mismatch(e);
data/systemtap-4.4/elaborate.cxx:6207:3: [1] (buffer) mismatch:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
mismatch (e->tok, t, e->type);
data/systemtap-4.4/elaborate.cxx:6218:3: [1] (buffer) mismatch:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
mismatch (e->tok, t, e->type);
data/systemtap-4.4/elaborate.cxx:6281:5: [1] (buffer) mismatch:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
mismatch (e);
data/systemtap-4.4/elaborate.cxx:6402:9: [1] (buffer) mismatch:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
mismatch (e);
data/systemtap-4.4/elaborate.cxx:6454:5: [1] (buffer) mismatch:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
mismatch (e);
data/systemtap-4.4/elaborate.cxx:6530:5: [1] (buffer) mismatch:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
mismatch (e->tok, sub_type, e->type);
data/systemtap-4.4/elaborate.cxx:6554:8: [1] (buffer) mismatch:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
r->mismatch (re_tok, re_type, referent); // referrer-referent
data/systemtap-4.4/elaborate.cxx:6556:8: [1] (buffer) mismatch:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
r->mismatch (re_tok, t, referent); // referrer-t
data/systemtap-4.4/elaborate.cxx:6558:8: [1] (buffer) mismatch:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
r->mismatch (re_tok, t, referent); // referent-t
data/systemtap-4.4/elaborate.cxx:7220:5: [1] (buffer) mismatch:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
mismatch (e->tok, t1, pe_long);
data/systemtap-4.4/elaborate.cxx:7245:9: [1] (buffer) mismatch:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
mismatch (e->tok, pe_unknown, current_function);
data/systemtap-4.4/elaborate.cxx:7253:5: [1] (buffer) mismatch:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
mismatch (e->value->tok, e->value->type, current_function);
data/systemtap-4.4/elaborate.cxx:7412:5: [1] (buffer) mismatch:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
mismatch (e->tok, pe_long, e->type);
data/systemtap-4.4/elaborate.cxx:7436:7: [1] (buffer) mismatch:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
mismatch (arg->tok, wanted, arg->type);
data/systemtap-4.4/elaborate.cxx:7497:22: [1] (buffer) mismatch:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
typeresolution_info::mismatch (const binary_expression* e)
data/systemtap-4.4/elaborate.cxx:7517:22: [1] (buffer) mismatch:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
typeresolution_info::mismatch (const token* tok, exp_type t1, exp_type t2)
data/systemtap-4.4/elaborate.h:111:8: [1] (buffer) mismatch:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
void mismatch (const binary_expression* e);
data/systemtap-4.4/elaborate.h:112:8: [1] (buffer) mismatch:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
void mismatch (const token* tok, exp_type t1, exp_type t2);
data/systemtap-4.4/hash.cxx:53:104: [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).
void add(const std::string& d, const char *s) { add((const std::string&)d, (const unsigned char *)s, strlen(s)); }
data/systemtap-4.4/httpd/api.cxx:738:10: [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 (strlen(optarg) > 0 && strlen(optarg) <= 5) {
data/systemtap-4.4/httpd/api.cxx:738:32: [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 (strlen(optarg) > 0 && strlen(optarg) <= 5) {
data/systemtap-4.4/httpd/api.cxx:739:28: [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).
for (unsigned i = 0; i < strlen(optarg); i++) {
data/systemtap-4.4/httpd/main.cxx:36:6: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
s = read(signal_fd, &si, sizeof(si));
data/systemtap-4.4/interactive.cxx:900:15: [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 = strlen(line);
data/systemtap-4.4/interactive.cxx:1373:11: [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 = strlen(text);
data/systemtap-4.4/interactive.cxx:1403:11: [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 = strlen(text);
data/systemtap-4.4/loc2stap.cxx:170: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).
loc->byte_size = strlen(string) + 1;
data/systemtap-4.4/nsscommon.cxx:436:24: [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).
memset (pw2, 0, strlen (pw2));
data/systemtap-4.4/nsscommon.cxx:441:20: [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).
memset (pw1, 0, strlen (pw1));
data/systemtap-4.4/nsscommon.cxx:450:23: [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).
memset (pw1, 0, strlen (pw1));
data/systemtap-4.4/nsscommon.cxx:631:30: [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).
current->name.other.len = strlen (tbuf);
data/systemtap-4.4/nsscommon.cxx:833:7: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
if (read != certDER.len)
data/systemtap-4.4/nsscommon.cxx:1728:10: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
size_t read;
data/systemtap-4.4/nsscommon.cxx:1731:7: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
if (read != derCert.len)
data/systemtap-4.4/rpm_finder.cxx:94:24: [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 rpminfolen = strlen(rpm_type);
data/systemtap-4.4/rpm_finder.cxx:139:6: [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).
strlen (s + srcrpmlen + rpminfolen) + 1);
data/systemtap-4.4/runtime/dyninst/arith.c:62:11: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
count = read(fd, &seed, sizeof(seed));
data/systemtap-4.4/runtime/dyninst/linux_defs.h:102:15: [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 ret = strlen(src);
data/systemtap-4.4/runtime/dyninst/linux_defs.h:114:17: [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 dsize = strlen(dest);
data/systemtap-4.4/runtime/dyninst/linux_defs.h:115:15: [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 = strlen(src);
data/systemtap-4.4/runtime/dyninst/transport.c:338:6: [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 (strlen(stp_session_attributes()->outfile_name)) {
data/systemtap-4.4/runtime/linux/stp_tracepoint.c:124:25: [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).
u32 hash = jhash(name, strlen(name), 0);
data/systemtap-4.4/runtime/linux/stp_tracepoint.c:143:20: [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 name_len = strlen(name) + 1;
data/systemtap-4.4/runtime/linux/task_finder.c:228:22: [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).
new_tgt->pathlen = strlen(new_tgt->procname);
data/systemtap-4.4/runtime/linux/task_finder.c:890:12: [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).
filelen = strlen(filename);
data/systemtap-4.4/runtime/linux/task_finder.c:1712:15: [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).
mmpathlen = strlen(mmpath);
data/systemtap-4.4/runtime/linux/task_finder2.c:286:22: [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).
new_tgt->pathlen = strlen(new_tgt->procname);
data/systemtap-4.4/runtime/linux/task_finder2.c:910:12: [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).
filelen = strlen(filename);
data/systemtap-4.4/runtime/linux/task_finder2.c:1824:15: [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).
mmpathlen = strlen(mmpath);
data/systemtap-4.4/runtime/map-gen.c:100: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).
uint32_t mylen = strlen(v); \
data/systemtap-4.4/runtime/procfs.c:92:6: [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 (strlen(path) == 0)
data/systemtap-4.4/runtime/softfloat.c:602:15: [1] (buffer) strcat:
Does not check for buffer overflows when concatenating to destination
[MS-banned] (CWE-120). Consider using strcat_s, strncat, strlcat, or
snprintf (warning: strncat is easily misused). Risk is low because the
source is a constant character.
if (sign) strcat(result, "-");
data/systemtap-4.4/runtime/softfloat.c:605:5: [1] (buffer) strcat:
Does not check for buffer overflows when concatenating to destination
[MS-banned] (CWE-120). Consider using strcat_s, strncat, strlcat, or
snprintf (warning: strncat is easily misused). Risk is low because the
source is a constant character.
strcat(result, ".");
data/systemtap-4.4/runtime/task_finder_vma.c:219:13: [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).
path_len = strlen(path);
data/systemtap-4.4/runtime/transport/control.c:324:8: [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 = strlen(msg) + 1;
data/systemtap-4.4/runtime/transport/control.c:335:8: [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 = strlen(msg) + 1;
data/systemtap-4.4/runtime/transport/control.c:346:8: [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 = strlen(msg) + 1;
data/systemtap-4.4/runtime/transport/control.c:357:8: [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 = strlen(msg) + 1;
data/systemtap-4.4/runtime/transport/debugfs.c:190:56: [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).
strlen(name));
data/systemtap-4.4/runtime/transport/procfs.c:235:61: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
relay_procfs_operations.proc_read = relay_file_operations.read;
data/systemtap-4.4/session.cxx:819:17: [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 (strlen (optarg) == 0)
data/systemtap-4.4/session.cxx:1077:10: [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 (strlen(optarg) < 1 || strlen(optarg) > 5)
data/systemtap-4.4/session.cxx:1077:32: [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 (strlen(optarg) < 1 || strlen(optarg) > 5)
data/systemtap-4.4/session.cxx:1081:24: [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).
for (unsigned i=0; i<strlen(optarg); i++)
data/systemtap-4.4/session.cxx:1390:8: [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 (strlen(optarg) == 0) {
data/systemtap-4.4/session.cxx:1415:8: [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 (strlen(optarg) == 0) {
data/systemtap-4.4/session.cxx:1436:8: [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 (strlen(optarg) == 0) {
data/systemtap-4.4/session.cxx:1457:8: [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 (strlen(optarg) == 0) {
data/systemtap-4.4/session.cxx:1482:8: [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 (strlen(optarg) == 0) {
data/systemtap-4.4/setupdwfl.cxx:778:19: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
ssize_t n = read (fd, buf.data, sizeof buf);
data/systemtap-4.4/stap-serverd.cxx:813:10: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
rc = read (fd, in_events, sizeof (in_events));
data/systemtap-4.4/stap-serverd.cxx:876:13: [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).
assert (strlen (initial_service_name) >= AVAHI_LABEL_MAX);
data/systemtap-4.4/stap-serverd.cxx:1630:15: [1] (access) umask:
Ensure that umask is given most restrictive possible setting (e.g., 066 or
077) (CWE-732).
old_umask = umask(077);
data/systemtap-4.4/stap-serverd.cxx:1701:3: [1] (access) umask:
Ensure that umask is given most restrictive possible setting (e.g., 066 or
077) (CWE-732).
umask(old_umask);
data/systemtap-4.4/stap-serverd.cxx:1714:3: [1] (access) umask:
Ensure that umask is given most restrictive possible setting (e.g., 066 or
077) (CWE-732).
umask(old_umask);
data/systemtap-4.4/stapbpf/bpfinterp.cxx:82:28: [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).
const char *end = fstr + strlen(fstr);
data/systemtap-4.4/stapbpf/stapbpf.cxx:153:12: [1] (access) umask:
Ensure that umask is given most restrictive possible setting (e.g., 066 or
077) (CWE-732).
uint64_t umask;
data/systemtap-4.4/stapbpf/stapbpf.cxx:160:42: [1] (access) umask:
Ensure that umask is given most restrictive possible setting (e.g., 066 or
077) (CWE-732).
procfsprobe_data(string path, uint64_t umask, char type, uint64_t maxsize_val, Elf_Data* prog)
data/systemtap-4.4/stapbpf/stapbpf.cxx:161:19: [1] (access) umask:
Ensure that umask is given most restrictive possible setting (e.g., 066 or
077) (CWE-732).
: path(path), umask(umask), type(type), maxsize_val(maxsize_val), read_prog(prog)
data/systemtap-4.4/stapbpf/stapbpf.cxx:161:25: [1] (access) umask:
Ensure that umask is given most restrictive possible setting (e.g., 066 or
077) (CWE-732).
: path(path), umask(umask), type(type), maxsize_val(maxsize_val), read_prog(prog)
data/systemtap-4.4/stapbpf/stapbpf.cxx:165:42: [1] (access) umask:
Ensure that umask is given most restrictive possible setting (e.g., 066 or
077) (CWE-732).
procfsprobe_data(string path, uint64_t umask, char type, uint64_t maxsize_val, std::vector<Elf_Data*> prog)
data/systemtap-4.4/stapbpf/stapbpf.cxx:166:19: [1] (access) umask:
Ensure that umask is given most restrictive possible setting (e.g., 066 or
077) (CWE-732).
: path(path), umask(umask), type(type), maxsize_val(maxsize_val), write_prog(prog)
data/systemtap-4.4/stapbpf/stapbpf.cxx:166:25: [1] (access) umask:
Ensure that umask is given most restrictive possible setting (e.g., 066 or
077) (CWE-732).
: path(path), umask(umask), type(type), maxsize_val(maxsize_val), write_prog(prog)
data/systemtap-4.4/stapbpf/stapbpf.cxx:633:17: [1] (access) umask:
Ensure that umask is given most restrictive possible setting (e.g., 066 or
077) (CWE-732).
unsigned long umask;
data/systemtap-4.4/stapbpf/stapbpf.cxx:638:56: [1] (access) umask:
Ensure that umask is given most restrictive possible setting (e.g., 066 or
077) (CWE-732).
int res = sscanf(name, "procfsprobe/%lu/%c/%lu/%s", &umask, &type, &maxsize_val, fifoname);
data/systemtap-4.4/stapbpf/stapbpf.cxx:646:51: [1] (access) umask:
Ensure that umask is given most restrictive possible setting (e.g., 066 or
077) (CWE-732).
procfsprobes.push_back(procfsprobe_data(path, umask, type, maxsize_val, prog));
data/systemtap-4.4/stapbpf/stapbpf.cxx:659:53: [1] (access) umask:
Ensure that umask is given most restrictive possible setting (e.g., 066 or
077) (CWE-732).
procfsprobes.push_back(procfsprobe_data(path, umask, type, maxsize_val, progs));
data/systemtap-4.4/stapbpf/stapbpf.cxx:733: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).
if (res != 2 || strlen(name) > 512)
data/systemtap-4.4/stapbpf/stapbpf.cxx:750: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).
if (res != 2 || strlen(name) > 512)
data/systemtap-4.4/stapbpf/stapbpf.cxx:873:13: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
len = read(fd, msgbuf, sizeof(msgbuf) - 1);
data/systemtap-4.4/stapbpf/stapbpf.cxx:992:13: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
len = read(fd, msgbuf, sizeof(msgbuf) - 1);
data/systemtap-4.4/stapbpf/stapbpf.cxx:1121:13: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
len = read(fd, msgbuf, sizeof(msgbuf) - 1);
data/systemtap-4.4/stapbpf/stapbpf.cxx:1537:42: [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).
else if (strncmp(shname, "procfs", strlen("procfs")) == 0) {
data/systemtap-4.4/stapbpf/stapbpf.cxx:1966:22: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
bytes_read = read(fd, buffer_feed, read_size);
data/systemtap-4.4/stapbpf/stapbpf.cxx:2031:24: [1] (access) umask:
Ensure that umask is given most restrictive possible setting (e.g., 066 or
077) (CWE-732).
uint64_t cmask = umask(data->umask);
data/systemtap-4.4/stapbpf/stapbpf.cxx:2031:36: [1] (access) umask:
Ensure that umask is given most restrictive possible setting (e.g., 066 or
077) (CWE-732).
uint64_t cmask = umask(data->umask);
data/systemtap-4.4/staplog.c:328:39: [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).
output_file = GETBUF(sizeof(char) * (strlen(dname) + strlen(fname) + 2));
data/systemtap-4.4/staplog.c:328:55: [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).
output_file = GETBUF(sizeof(char) * (strlen(dname) + strlen(fname) + 2));
data/systemtap-4.4/staprun/common.c:71:8: [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 = strlen(getcwd(path_buf, PATH_MAX));
data/systemtap-4.4/staprun/common.c:72:16: [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 (len + 2 + strlen(path) >= PATH_MAX)
data/systemtap-4.4/staprun/common.c:434:17: [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 plen = strlen(inpath);
data/systemtap-4.4/staprun/common.c:465:57: [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 = sizeof(MODULE_PATH) + sizeof(utsbuf.release) + strlen(inpath);
data/systemtap-4.4/staprun/common.c:506:6: [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 (strlen(modname) > MODULE_NAME_LEN) {
data/systemtap-4.4/staprun/common.c:518:41: [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).
rc = write (STDERR_FILENO, str, strlen(str));
data/systemtap-4.4/staprun/common.c:732:10: [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).
int n = strlen(type);
data/systemtap-4.4/staprun/ctl.c:32:17: [1] (buffer) strncpy:
Easily used incorrectly; doesn't always \0-terminate or check for invalid
pointers [MS-banned] (CWE-120).
strncpy(buf, CTL_CHANNEL_NAME, PATH_MAX - 1);
data/systemtap-4.4/staprun/mainloop.c:298:48: [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).
char *buf = malloc(sizeof(char) * (strlen(target_cmd) + 13));
data/systemtap-4.4/staprun/mainloop.c:730:10: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
nb = read(control_channel, &recvbuf, sizeof(recvbuf));
data/systemtap-4.4/staprun/mainloop.c:744:2: [1] (obsolete) usleep:
This C routine is considered obsolete (as opposed to the shell command by
the same name). The interaction of this function with SIGALRM and other
timer functions such as sleep(), alarm(), setitimer(), and nanosleep() is
unspecified (CWE-676). Use nanosleep(2) or setitimer(2) instead.
usleep (250*1000); /* sleep 250ms between polls */
data/systemtap-4.4/staprun/mainloop.c:801:52: [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).
warn("%.*s", strlen(dupstr)-9, dupstr+9);
data/systemtap-4.4/staprun/modverify.c:191:26: [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).
fileName = PORT_Alloc (strlen (cert_db_path) + 11);
data/systemtap-4.4/staprun/monitor.c:170:16: [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 = strlen(msg);
data/systemtap-4.4/staprun/monitor.c:261:3: [1] (obsolete) usleep:
This C routine is considered obsolete (as opposed to the shell command by
the same name). The interaction of this function with SIGALRM and other
timer functions such as sleep(), alarm(), setitimer(), and nanosleep() is
unspecified (CWE-676). Use nanosleep(2) or setitimer(2) instead.
usleep (500*1000); /* prevent too many allocations */
data/systemtap-4.4/staprun/monitor.c:431:48: [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).
width[p_index] = MAX(width[p_index], strlen(json_object_get_string(field)));
data/systemtap-4.4/staprun/monitor.c:433:48: [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).
width[p_state] = MAX(width[p_state], strlen(json_object_get_string(field)));
data/systemtap-4.4/staprun/monitor.c:435:46: [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).
width[p_hits] = MAX(width[p_hits], strlen(json_object_get_string(field)));
data/systemtap-4.4/staprun/monitor.c:437:44: [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).
width[p_min] = MAX(width[p_min], strlen(json_object_get_string(field)));
data/systemtap-4.4/staprun/monitor.c:439:44: [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).
width[p_avg] = MAX(width[p_avg], strlen(json_object_get_string(field)));
data/systemtap-4.4/staprun/monitor.c:441:44: [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).
width[p_max] = MAX(width[p_max], strlen(json_object_get_string(field)));
data/systemtap-4.4/staprun/monitor.c:443:46: [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).
width[p_name] = MAX(width[p_name], strlen(json_object_get_string(field)));
data/systemtap-4.4/staprun/monitor.c:684:17: [1] (obsolete) usleep:
This C routine is considered obsolete (as opposed to the shell command by
the same name). The interaction of this function with SIGALRM and other
timer functions such as sleep(), alarm(), setitimer(), and nanosleep() is
unspecified (CWE-676). Use nanosleep(2) or setitimer(2) instead.
usleep(2000);
data/systemtap-4.4/staprun/monitor.c:686:21: [1] (buffer) getchar:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
while ((c = getchar()) != EOF) {
data/systemtap-4.4/staprun/relay.c:193:16: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
while ((rc = read(relay_fd[cpu], buf, sizeof(buf))) > 0) {
data/systemtap-4.4/staprun/relay_old.c:330:8: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
rc = read(proc_fd[cpu], &status[cpu].info, sizeof(struct _stp_buf_info));
data/systemtap-4.4/staprun/staprun.c:194:22: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
rc = read(fips_mode_fd, &c, 1);
data/systemtap-4.4/staprun/staprun.c:321:14: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
rc = read (fd, &prev, sizeof(prev));
data/systemtap-4.4/staprun/staprun.c:368:14: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
rc = read (fd, &prev, sizeof(prev));
data/systemtap-4.4/staprun/staprun.c:586:7: [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 (strlen(module) >= STP_MODULE_NAME_LEN-1) {
data/systemtap-4.4/staprun/staprun.c:590:3: [1] (buffer) strncpy:
Easily used incorrectly; doesn't always \0-terminate or check for invalid
pointers [MS-banned] (CWE-120).
strncpy (msg.module, module, STP_MODULE_NAME_LEN - 1);
data/systemtap-4.4/staprun/staprun.c:592:7: [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 (strlen(reloc) >= STP_SYMBOL_NAME_LEN-1) {
data/systemtap-4.4/staprun/staprun.c:596:3: [1] (buffer) strncpy:
Easily used incorrectly; doesn't always \0-terminate or check for invalid
pointers [MS-banned] (CWE-120).
strncpy (msg.reloc, reloc, STP_MODULE_NAME_LEN - 1);
data/systemtap-4.4/staprun/staprun.c:806:3: [1] (buffer) strncpy:
Easily used incorrectly; doesn't always \0-terminate or check for invalid
pointers [MS-banned] (CWE-120).
strncpy (tzi.tz_name, tzname[0], STP_TZ_NAME_LEN - 1);
data/systemtap-4.4/staprun/staprun.c:812:3: [1] (buffer) strncpy:
Easily used incorrectly; doesn't always \0-terminate or check for invalid
pointers [MS-banned] (CWE-120).
strncpy (tzi.tz_name, now->tm_zone, STP_TZ_NAME_LEN - 1);
data/systemtap-4.4/staprun/staprun.c:839:3: [1] (buffer) strncpy:
Easily used incorrectly; doesn't always \0-terminate or check for invalid
pointers [MS-banned] (CWE-120).
strncpy (rem.remote_uri, remote_uri, STP_REMOTE_URI_LEN - 1);
data/systemtap-4.4/staprun/staprun_funcs.c:87:24: [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).
opts = realloc(opts, strlen(opts) + strlen(options[i]) + 2);
data/systemtap-4.4/staprun/staprun_funcs.c:87:39: [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).
opts = realloc(opts, strlen(opts) + strlen(options[i]) + 2);
data/systemtap-4.4/staprun/staprun_funcs.c:94:3: [1] (buffer) strcat:
Does not check for buffer overflows when concatenating to destination
[MS-banned] (CWE-120). Consider using strcat_s, strncat, strlcat, or
snprintf (warning: strncat is easily misused). Risk is low because the
source is a constant character.
strcat(opts, " ");
data/systemtap-4.4/staprun/staprun_funcs.c:143:23: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
ret = read(module_fd, module_file + module_read,
data/systemtap-4.4/staprun/staprun_funcs.c:272:8: [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 (strlen(modname) >= MODULE_NAME_LEN) {
data/systemtap-4.4/staprun/staprun_funcs.c:277:29: [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).
length_to_replace = (int)strlen(modname)-((int)log10(pid)+1) - 1;
data/systemtap-4.4/staprun/staprun_funcs.c:278:57: [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(length_to_replace < 0 || length_to_replace > (int)strlen(modname)) {
data/systemtap-4.4/staprun/staprun_funcs.c:296:65: [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).
for (p = data->d_buf; p < (char *)data->d_buf + data->d_size - strlen(modname); p++) {
data/systemtap-4.4/staprun/staprun_funcs.c:297:26: [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 (memcmp(p, modname, strlen(modname)) == 0) {
data/systemtap-4.4/staprun/staprun_funcs.c:298:4: [1] (buffer) strncpy:
Easily used incorrectly; doesn't always \0-terminate or check for invalid
pointers [MS-banned] (CWE-120).
strncpy(p, newname, strlen(p)); /* Actually replace the oldname in memory with the newname */
data/systemtap-4.4/staprun/staprun_funcs.c:298:24: [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).
strncpy(p, newname, strlen(p)); /* Actually replace the oldname in memory with the newname */
data/systemtap-4.4/staprun/staprun_funcs.c:361:15: [1] (access) umask:
Ensure that umask is given most restrictive possible setting (e.g., 066 or
077) (CWE-732).
old_umask = umask(0002);
data/systemtap-4.4/staprun/staprun_funcs.c:390:3: [1] (access) umask:
Ensure that umask is given most restrictive possible setting (e.g., 066 or
077) (CWE-732).
umask(old_umask);
data/systemtap-4.4/staprun/staprun_funcs.c:431:7: [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 (strlen (path) >= PATH_MAX - 5) {
data/systemtap-4.4/staprun/staprun_funcs.c:483:6: [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 (strlen(staplib_dir_realpath) < (PATH_MAX - 1))
data/systemtap-4.4/staprun/staprun_funcs.c:486:3: [1] (buffer) strcat:
Does not check for buffer overflows when concatenating to destination
[MS-banned] (CWE-120). Consider using strcat_s, strncat, strlcat, or
snprintf (warning: strncat is easily misused). Risk is low because the
source is a constant character.
strcat(staplib_dir_realpath, "/");
data/systemtap-4.4/staprun/staprun_funcs.c:530:7: [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).
strlen(staplib_dir_realpath)) != 0) {
data/systemtap-4.4/staprun/stapsh.c:694:15: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
ssize_t n = read(pfds[i].fd, buf, sizeof buf);
data/systemtap-4.4/staprun/stapsh.c:756:3: [1] (access) umask:
Ensure that umask is given most restrictive possible setting (e.g., 066 or
077) (CWE-732).
umask(0077);
data/systemtap-4.4/staptree.cxx:2683:3: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
read.insert(s->read_referents.begin(), s->read_referents.end());
data/systemtap-4.4/staptree.cxx:2729:3: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
read.insert(e->read_referents.begin(), e->read_referents.end());
data/systemtap-4.4/staptree.cxx:2945:7: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
read.insert (e->referent);
data/systemtap-4.4/staptree.h:1165:22: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
std::set<vardecl*> read;
data/systemtap-4.4/stapvirt.c:90:32: [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).
const char *end = domStr + strlen(domStr);
data/systemtap-4.4/stapvirt.c:396:54: [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 (lastdot == NULL || (size_t)(lastdot-name) != strlen(basename))
data/systemtap-4.4/stapvirt.c:400:30: [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).
const char *end = name + strlen(name);
data/systemtap-4.4/stapvirt.c:727:9: [1] (buffer) strncpy:
Easily used incorrectly; doesn't always \0-terminate or check for invalid
pointers [MS-banned] (CWE-120). Risk is low because the source is a
constant string.
strncpy(uuid, "INVALID_UUID", VIR_UUID_STRING_BUFLEN - 1);
data/systemtap-4.4/stapvirt.c:978:26: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
int bytes_read = read(fd, ctxt->termbuf + ctxt->termbuf_off,
data/systemtap-4.4/stringtable.cxx:167:46: [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).
f, strlen(f));
data/systemtap-4.4/stringtable.h:150:35: [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).
return (this->compare(0, std::strlen(value), value) == 0);
data/systemtap-4.4/tapset-procfs.cxx:41:11: [1] (access) umask:
Ensure that umask is given most restrictive possible setting (e.g., 066 or
077) (CWE-732).
int64_t umask;
data/systemtap-4.4/tapset-procfs.cxx:44:110: [1] (access) umask:
Ensure that umask is given most restrictive possible setting (e.g., 066 or
077) (CWE-732).
procfs_derived_probe (systemtap_session &, probe* p, probe_point* l, string ps, bool w, int64_t m, int64_t umask);
data/systemtap-4.4/tapset-procfs.cxx:101:46: [1] (access) umask:
Ensure that umask is given most restrictive possible setting (e.g., 066 or
077) (CWE-732).
s << "procfsprobe/" << read_probe->umask << "/r/" << read_probe->maxsize_val << "/" << i->first;
data/systemtap-4.4/tapset-procfs.cxx:110:40: [1] (access) umask:
Ensure that umask is given most restrictive possible setting (e.g., 066 or
077) (CWE-732).
s << "procfsprobe/" << (*j)->umask << "/w/" << (*j)->maxsize_val << "/" << i->first;
data/systemtap-4.4/tapset-procfs.cxx:133:29: [1] (access) umask:
Ensure that umask is given most restrictive possible setting (e.g., 066 or
077) (CWE-732).
int64_t m, int64_t umask):
data/systemtap-4.4/tapset-procfs.cxx:135:21: [1] (access) umask:
Ensure that umask is given most restrictive possible setting (e.g., 066 or
077) (CWE-732).
maxsize_val(m), umask(umask)
data/systemtap-4.4/tapset-procfs.cxx:135:27: [1] (access) umask:
Ensure that umask is given most restrictive possible setting (e.g., 066 or
077) (CWE-732).
maxsize_val(m), umask(umask)
data/systemtap-4.4/tapset-procfs.cxx:351:46: [1] (access) umask:
Ensure that umask is given most restrictive possible setting (e.g., 066 or
077) (CWE-732).
((pset->read_probe ? pset->read_probe->umask : 0)
data/systemtap-4.4/tapset-procfs.cxx:352:66: [1] (access) umask:
Ensure that umask is given most restrictive possible setting (e.g., 066 or
077) (CWE-732).
| (pset->write_probes.size() > 0 ? pset->write_probes[0]->umask : 0)))
data/systemtap-4.4/testsuite/systemtap.base/cast-scope.cxx:16:7: [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).
_l = strlen(_str);
data/systemtap-4.4/testsuite/systemtap.base/gtod.c:16:11: [1] (obsolete) usleep:
This C routine is considered obsolete (as opposed to the shell command by
the same name). The interaction of this function with SIGALRM and other
timer functions such as sleep(), alarm(), setitimer(), and nanosleep() is
unspecified (CWE-676). Use nanosleep(2) or setitimer(2) instead.
if (us) usleep(us);
data/systemtap-4.4/testsuite/systemtap.base/plt.c:46: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).
char *name = (char *) alloca (strlen (str1) + strlen (str2) + 1);
data/systemtap-4.4/testsuite/systemtap.base/plt.c:46:49: [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).
char *name = (char *) alloca (strlen (str1) + strlen (str2) + 1);
data/systemtap-4.4/testsuite/systemtap.base/plt.c:55: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).
char *name = (char *) malloc (strlen (str1) + strlen (str2) + 1);
data/systemtap-4.4/testsuite/systemtap.base/plt.c:55:49: [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).
char *name = (char *) malloc (strlen (str1) + strlen (str2) + 1);
data/systemtap-4.4/testsuite/systemtap.clone/dtrace_clone.c:72:17: [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).
write(2, msg2, strlen(msg2));
data/systemtap-4.4/testsuite/systemtap.printf/memory1_module.c:63:17: [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 bytes = strlen(data);
data/systemtap-4.4/testsuite/systemtap.syscall/alarm.c:64:3: [1] (obsolete) usleep:
This C routine is considered obsolete (as opposed to the shell command by
the same name). The interaction of this function with SIGALRM and other
timer functions such as sleep(), alarm(), setitimer(), and nanosleep() is
unspecified (CWE-676). Use nanosleep(2) or setitimer(2) instead.
usleep(1234);
data/systemtap-4.4/testsuite/systemtap.syscall/bind.c:36:3: [1] (buffer) strncpy:
Easily used incorrectly; doesn't always \0-terminate or check for invalid
pointers [MS-banned] (CWE-120). Risk is low because the source is a
constant character.
strncpy(sun1.sun_path, ".", sizeof(sun1.sun_path) - 1);
data/systemtap-4.4/testsuite/systemtap.syscall/connect.c:51:13: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
if ((cc = read(fd, &c, 1)) == 0) {
data/systemtap-4.4/testsuite/systemtap.syscall/fanotify.c:51:22: [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).
write(fd, fname, strlen(fname));
data/systemtap-4.4/testsuite/systemtap.syscall/fanotify.c:58:5: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
read(fd_notify, event_buf, EVENT_BUF_LEN);
data/systemtap-4.4/testsuite/systemtap.syscall/kexec_load.c:115: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).
__kexec_file_load(fd, fd, strlen(cmdline), cmdline, KEXEC_FILE_ON_CRASH);
data/systemtap-4.4/testsuite/systemtap.syscall/kexec_load.c:119: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).
__kexec_file_load(-1, fd, strlen(cmdline), cmdline, KEXEC_FILE_UNLOAD);
data/systemtap-4.4/testsuite/systemtap.syscall/kexec_load.c:122: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).
__kexec_file_load(fd, -1, strlen(cmdline), cmdline, KEXEC_FILE_NO_INITRAMFS);
data/systemtap-4.4/testsuite/systemtap.syscall/kexec_load.c:132: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).
__kexec_file_load(fd, fd, strlen(cmdline), (char *)-1, KEXEC_FILE_ON_CRASH);
data/systemtap-4.4/testsuite/systemtap.syscall/kexec_load.c:135: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).
__kexec_file_load(fd, fd, strlen(cmdline), cmdline, -1);
data/systemtap-4.4/testsuite/systemtap.syscall/keyctl.c:43:55: [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).
key_id = __add_key("user", "testkey", "somedata", strlen("somedata"), ring_id);
data/systemtap-4.4/testsuite/systemtap.syscall/keyctl.c:68:59: [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).
key_id_2 = __add_key("user", "testkey2", "somedata2", strlen("somedata2"), ring_id);
data/systemtap-4.4/testsuite/systemtap.syscall/keyctl.c:127:59: [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).
key_id_2 = __add_key("user", "testkey2", "somedata2", strlen("somedata2"), ring_id);
data/systemtap-4.4/testsuite/systemtap.syscall/keyctl.c:132:69: [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).
syscall(__NR_keyctl, KEYCTL_INSTANTIATE, key_id_2, "somedata2", strlen("somedata2"), ring_id);
data/systemtap-4.4/testsuite/systemtap.syscall/keyctl.c:156:59: [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).
key_id_2 = __add_key("user", "testkey2", "somedata2", strlen("somedata2"), ring_id);
data/systemtap-4.4/testsuite/systemtap.syscall/madvise.c:26:26: [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).
write(fd, str_for_file, strlen(str_for_file));
data/systemtap-4.4/testsuite/systemtap.syscall/nfsservctl.c:34:5: [1] (buffer) strncpy:
Easily used incorrectly; doesn't always \0-terminate or check for invalid
pointers [MS-banned] (CWE-120). Risk is low because the source is a
constant string.
strncpy(arg.u.u_export.ex_path, "/__fAkE_pAtH__/__nO_eXiSt__",
data/systemtap-4.4/testsuite/systemtap.syscall/perf_event.c:47:5: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
read(fd, &count, sizeof(count));
data/systemtap-4.4/testsuite/systemtap.syscall/readwrite.c:55:3: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
read(fd, buf, 11);
data/systemtap-4.4/testsuite/systemtap.syscall/readwrite.c:58:3: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
read(fd, buf, 50);
data/systemtap-4.4/testsuite/systemtap.syscall/readwrite.c:61:3: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
read(-1, buf, 50);
data/systemtap-4.4/testsuite/systemtap.syscall/readwrite.c:64:3: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
read(fd, (void *)-1, 50);
data/systemtap-4.4/testsuite/systemtap.syscall/readwrite.c:72:3: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
read(-1, NULL, -1);
data/systemtap-4.4/testsuite/systemtap.syscall/recv.c:54:13: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
if ((cc = read(fd, &c, 1)) == 0) {
data/systemtap-4.4/testsuite/systemtap.syscall/recvfrom.c:55:13: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
if ((cc = read(fd, &c, 1)) == 0) {
data/systemtap-4.4/testsuite/systemtap.syscall/recvmmsg.c:90:8: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
cc = read(fd, rbuf, sizeof(rbuf));
data/systemtap-4.4/testsuite/systemtap.syscall/recvmsg.c:89:8: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
cc = read(fd, rbuf, sizeof(rbuf));
data/systemtap-4.4/testsuite/systemtap.syscall/sched_attr.c:33:16: [1] (free) memalign:
On some systems (though not Linux-based systems) an attempt to free()
results from memalign() may fail. This may, on a few systems, be
exploitable. Also note that memalign() may not check that the boundary
parameter is correct (CWE-676). Use posix_memalign instead (defined in
POSIX's 1003.1d). Don't switch to valloc(); it is marked as obsolete in BSD
4.3, as legacy in SUSv2, and is no longer defined in SUSv3. In some cases,
malloc()'s alignment may be sufficient.
void *sa = memalign(sal, sas);
data/systemtap-4.4/testsuite/systemtap.syscall/send.c:52:8: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
cc = read(fd, buf, sizeof(buf));
data/systemtap-4.4/testsuite/systemtap.syscall/sendmmsg.c:64:8: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
cc = read(fd, buf, sizeof(buf));
data/systemtap-4.4/testsuite/systemtap.syscall/sendmsg.c:52:8: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
cc = read(fd, buf, sizeof(buf));
data/systemtap-4.4/testsuite/systemtap.syscall/sendto.c:52:8: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
cc = read(fd, buf, sizeof(buf));
data/systemtap-4.4/testsuite/systemtap.syscall/umask.c:7:3: [1] (access) umask:
Ensure that umask is given most restrictive possible setting (e.g., 066 or
077) (CWE-732).
umask (0);
data/systemtap-4.4/testsuite/systemtap.syscall/umask.c:9:3: [1] (access) umask:
Ensure that umask is given most restrictive possible setting (e.g., 066 or
077) (CWE-732).
umask (7);
data/systemtap-4.4/testsuite/systemtap.syscall/umask.c:11:3: [1] (access) umask:
Ensure that umask is given most restrictive possible setting (e.g., 066 or
077) (CWE-732).
umask (077);
data/systemtap-4.4/testsuite/systemtap.syscall/umask.c:13:3: [1] (access) umask:
Ensure that umask is given most restrictive possible setting (e.g., 066 or
077) (CWE-732).
umask (0666);
data/systemtap-4.4/testsuite/systemtap.syscall/umask.c:15:3: [1] (access) umask:
Ensure that umask is given most restrictive possible setting (e.g., 066 or
077) (CWE-732).
umask (0777);
data/systemtap-4.4/testsuite/systemtap.syscall/umask.c:17:3: [1] (access) umask:
Ensure that umask is given most restrictive possible setting (e.g., 066 or
077) (CWE-732).
umask (01777);
data/systemtap-4.4/testsuite/systemtap.syscall/umask.c:22:3: [1] (access) umask:
Ensure that umask is given most restrictive possible setting (e.g., 066 or
077) (CWE-732).
umask (-1);
data/systemtap-4.4/testsuite/systemtap.unprivileged/loop.c:51:5: [1] (obsolete) usleep:
This C routine is considered obsolete (as opposed to the shell command by
the same name). The interaction of this function with SIGALRM and other
timer functions such as sleep(), alarm(), setitimer(), and nanosleep() is
unspecified (CWE-676). Use nanosleep(2) or setitimer(2) instead.
usleep (250000); /* 1/4 second pause. */
data/systemtap-4.4/translate.cxx:3048:25: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
bool read_p = vut.read.count(v) > 0;
data/systemtap-4.4/translate.cxx:3062:46: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
written_p = vcv_needs_global_locks.read.count(v) > 0;
data/systemtap-4.4/translate.cxx:3170:25: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
bool read_p = vut.read.count(v) > 0;
data/systemtap-4.4/util.cxx:156:15: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
while ((n = read(fd1, buf, sizeof(buf))) > 0)
data/systemtap-4.4/util.cxx:169:10: [1] (access) umask:
Ensure that umask is given most restrictive possible setting (e.g., 066 or
077) (CWE-732).
mask = umask(0);
data/systemtap-4.4/util.cxx:171:3: [1] (access) umask:
Ensure that umask is given most restrictive possible setting (e.g., 066 or
077) (CWE-732).
umask(mask);
data/systemtap-4.4/util.h:321:29: [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).
return (s.compare(0, std::strlen(prefix), prefix) == 0);
data/systemtap-4.4/util.h:334:46: [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 s_len = s.size(), suffix_len = std::strlen(suffix);
ANALYSIS SUMMARY:
Hits = 972
Lines analyzed = 196411 in approximately 4.44 seconds (44235 lines/second)
Physical Source Lines of Code (SLOC) = 139023
Hits@level = [0] 326 [1] 259 [2] 508 [3] 81 [4] 105 [5] 19
Hits@level+ = [0+] 1298 [1+] 972 [2+] 713 [3+] 205 [4+] 124 [5+] 19
Hits/KSLOC@level+ = [0+] 9.33658 [1+] 6.99165 [2+] 5.12865 [3+] 1.47458 [4+] 0.891939 [5+] 0.136668
Symlinks skipped = 2 (--allowlink overrides but see doc for security issue)
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.