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/blcr-0.8.6~b3/blcr_imports/module.c
Examining data/blcr-0.8.6~b3/include/blcr_ioctl.h
Examining data/blcr-0.8.6~b3/include/blcr_vmadump.h
Examining data/blcr-0.8.6~b3/include/libcr.h
Examining data/blcr-0.8.6~b3/include/blcr_ksyms.h
Examining data/blcr-0.8.6~b3/include/blcr_proc.h
Examining data/blcr-0.8.6~b3/include/blcr_errcodes.h
Examining data/blcr-0.8.6~b3/tests/atomics_stress.c
Examining data/blcr-0.8.6~b3/tests/child.c
Examining data/blcr-0.8.6~b3/tests/stage0002.c
Examining data/blcr-0.8.6~b3/tests/bug2003_aux.c
Examining data/blcr-0.8.6~b3/tests/forward.c
Examining data/blcr-0.8.6~b3/tests/edeadlk.c
Examining data/blcr-0.8.6~b3/tests/hugetlbfs2.c
Examining data/blcr-0.8.6~b3/tests/crut_util.c
Examining data/blcr-0.8.6~b3/tests/hello.c
Examining data/blcr-0.8.6~b3/tests/cr_signal.c
Examining data/blcr-0.8.6~b3/tests/bug2524.c
Examining data/blcr-0.8.6~b3/tests/get_info.c
Examining data/blcr-0.8.6~b3/tests/named_fifo.c
Examining data/blcr-0.8.6~b3/tests/dev_null.c
Examining data/blcr-0.8.6~b3/tests/dpipe.c
Examining data/blcr-0.8.6~b3/tests/orphan.c
Examining data/blcr-0.8.6~b3/tests/simple.c
Examining data/blcr-0.8.6~b3/tests/failed_cb2.c
Examining data/blcr-0.8.6~b3/tests/dlopen_aux.c
Examining data/blcr-0.8.6~b3/tests/dup.c
Examining data/blcr-0.8.6~b3/tests/atomics.c
Examining data/blcr-0.8.6~b3/tests/stopped.c
Examining data/blcr-0.8.6~b3/tests/cs_enter_leave2.c
Examining data/blcr-0.8.6~b3/tests/crut_util_pth.c
Examining data/blcr-0.8.6~b3/tests/crut_util.h
Examining data/blcr-0.8.6~b3/tests/cr_tryenter_cs.c
Examining data/blcr-0.8.6~b3/tests/crut.c
Examining data/blcr-0.8.6~b3/tests/simple_pthread.c
Examining data/blcr-0.8.6~b3/tests/replace_cb.c
Examining data/blcr-0.8.6~b3/tests/crut_util_libcr.c
Examining data/blcr-0.8.6~b3/tests/stage0004.c
Examining data/blcr-0.8.6~b3/tests/cwd.c
Examining data/blcr-0.8.6~b3/tests/filedescriptors.c
Examining data/blcr-0.8.6~b3/tests/cloexec.c
Examining data/blcr-0.8.6~b3/tests/pause.c
Examining data/blcr-0.8.6~b3/tests/crut.h
Examining data/blcr-0.8.6~b3/tests/cs_enter_leave.c
Examining data/blcr-0.8.6~b3/tests/lam.c
Examining data/blcr-0.8.6~b3/tests/stage0003.c
Examining data/blcr-0.8.6~b3/tests/sigpending.c
Examining data/blcr-0.8.6~b3/tests/prctl.c
Examining data/blcr-0.8.6~b3/tests/testcxx.cc
Examining data/blcr-0.8.6~b3/tests/linked_fifo.c
Examining data/blcr-0.8.6~b3/tests/overlap.c
Examining data/blcr-0.8.6~b3/tests/stage0001.c
Examining data/blcr-0.8.6~b3/tests/save_aux.c
Examining data/blcr-0.8.6~b3/tests/hooks.c
Examining data/blcr-0.8.6~b3/tests/sigaltstack.c
Examining data/blcr-0.8.6~b3/tests/mmaps.c
Examining data/blcr-0.8.6~b3/tests/crut_wrapper.c
Examining data/blcr-0.8.6~b3/tests/readdir.c
Examining data/blcr-0.8.6~b3/tests/failed_cb.c
Examining data/blcr-0.8.6~b3/tests/pid_restore.c
Examining data/blcr-0.8.6~b3/tests/pipe.c
Examining data/blcr-0.8.6~b3/tests/pid_in_use.c
Examining data/blcr-0.8.6~b3/tests/critical_sections.c
Examining data/blcr-0.8.6~b3/tests/ptrace.c
Examining data/blcr-0.8.6~b3/tests/nscd.c
Examining data/blcr-0.8.6~b3/tests/math.c
Examining data/blcr-0.8.6~b3/tests/reloc_aux.c
Examining data/blcr-0.8.6~b3/tests/seq_wrapper.c
Examining data/blcr-0.8.6~b3/tests/cb_exit.c
Examining data/blcr-0.8.6~b3/tests/hugetlbfs.c
Examining data/blcr-0.8.6~b3/util/cr_checkpoint/cr_checkpoint.c
Examining data/blcr-0.8.6~b3/util/cr_restart/cr_restart.c
Examining data/blcr-0.8.6~b3/examples/pipe_counting/pipe_counting.c
Examining data/blcr-0.8.6~b3/examples/pthread_misc/pthread_misc.c
Examining data/blcr-0.8.6~b3/examples/io_bench/io_bench.c
Examining data/blcr-0.8.6~b3/examples/file_counting/file_counting.c
Examining data/blcr-0.8.6~b3/examples/pthread_counting/pthread_counting.c
Examining data/blcr-0.8.6~b3/examples/counting/counting.c
Examining data/blcr-0.8.6~b3/cr_module/cr_io.c
Examining data/blcr-0.8.6~b3/cr_module/cr_vmadump.c
Examining data/blcr-0.8.6~b3/cr_module/cr_module.c
Examining data/blcr-0.8.6~b3/cr_module/cr_dest_file.c
Examining data/blcr-0.8.6~b3/cr_module/cr_fops.c
Examining data/blcr-0.8.6~b3/cr_module/cr_sync.c
Examining data/blcr-0.8.6~b3/cr_module/cr_barrier.h
Examining data/blcr-0.8.6~b3/cr_module/cr_compat.c
Examining data/blcr-0.8.6~b3/cr_module/cr_relocate.c
Examining data/blcr-0.8.6~b3/cr_module/cr_task.c
Examining data/blcr-0.8.6~b3/cr_module/cr_watchdog.c
Examining data/blcr-0.8.6~b3/cr_module/cr_ktrace.h
Examining data/blcr-0.8.6~b3/cr_module/cr_pipes.c
Examining data/blcr-0.8.6~b3/cr_module/cr_trigger.c
Examining data/blcr-0.8.6~b3/cr_module/cr_proc.c
Examining data/blcr-0.8.6~b3/cr_module/arch/i386/cr_arch.h
Examining data/blcr-0.8.6~b3/cr_module/arch/sparc/cr_arch.h
Examining data/blcr-0.8.6~b3/cr_module/arch/arm/cr_arch.h
Examining data/blcr-0.8.6~b3/cr_module/arch/sparc64/cr_arch.h
Examining data/blcr-0.8.6~b3/cr_module/arch/x86_64/cr_arch.h
Examining data/blcr-0.8.6~b3/cr_module/arch/ppc/cr_arch.h
Examining data/blcr-0.8.6~b3/cr_module/arch/ppc64/cr_arch.h
Examining data/blcr-0.8.6~b3/cr_module/cr_kcompat.h
Examining data/blcr-0.8.6~b3/cr_module/cr_barrier.c
Examining data/blcr-0.8.6~b3/cr_module/cr_module.h
Examining data/blcr-0.8.6~b3/cr_module/cr_dump_self.c
Examining data/blcr-0.8.6~b3/cr_module/cr_objects.c
Examining data/blcr-0.8.6~b3/cr_module/cr_mmaps.c
Examining data/blcr-0.8.6~b3/cr_module/cr_context.h
Examining data/blcr-0.8.6~b3/cr_module/cr_ktrace.c
Examining data/blcr-0.8.6~b3/cr_module/cr_creds.c
Examining data/blcr-0.8.6~b3/cr_module/cr_rstrt_req.c
Examining data/blcr-0.8.6~b3/cr_module/cr_timers.c
Examining data/blcr-0.8.6~b3/cr_module/cr_async.c
Examining data/blcr-0.8.6~b3/cr_module/cr_chkpt_req.c
Examining data/blcr-0.8.6~b3/libcr/cr_syscall.h
Examining data/blcr-0.8.6~b3/libcr/cr_rb_lock.h
Examining data/blcr-0.8.6~b3/libcr/cr_libinit.c
Examining data/blcr-0.8.6~b3/libcr/cr_omit.c
Examining data/blcr-0.8.6~b3/libcr/cr_trace.c
Examining data/blcr-0.8.6~b3/libcr/cr_private.h
Examining data/blcr-0.8.6~b3/libcr/cr_syscall.c
Examining data/blcr-0.8.6~b3/libcr/cr_yield.h
Examining data/blcr-0.8.6~b3/libcr/cr_cs.c
Examining data/blcr-0.8.6~b3/libcr/cr_ftb.c
Examining data/blcr-0.8.6~b3/libcr/arch/i386/cr_arch.h
Examining data/blcr-0.8.6~b3/libcr/arch/i386/cr_atomic.h
Examining data/blcr-0.8.6~b3/libcr/arch/sparc/cr_arch.h
Examining data/blcr-0.8.6~b3/libcr/arch/sparc/cr_atomic.h
Examining data/blcr-0.8.6~b3/libcr/arch/arm/cr_arch.h
Examining data/blcr-0.8.6~b3/libcr/arch/arm/cr_atomic.h
Examining data/blcr-0.8.6~b3/libcr/arch/sparc64/cr_arch.h
Examining data/blcr-0.8.6~b3/libcr/arch/sparc64/cr_atomic.h
Examining data/blcr-0.8.6~b3/libcr/arch/x86_64/cr_arch.h
Examining data/blcr-0.8.6~b3/libcr/arch/x86_64/cr_atomic.h
Examining data/blcr-0.8.6~b3/libcr/arch/ppc/cr_arch.h
Examining data/blcr-0.8.6~b3/libcr/arch/ppc/cr_atomic.h
Examining data/blcr-0.8.6~b3/libcr/arch/ppc64/cr_arch.h
Examining data/blcr-0.8.6~b3/libcr/arch/ppc64/cr_atomic.h
Examining data/blcr-0.8.6~b3/libcr/cr_core.c
Examining data/blcr-0.8.6~b3/libcr/cr_trace.h
Examining data/blcr-0.8.6~b3/libcr/cr_run.c
Examining data/blcr-0.8.6~b3/libcr/cr_request.c
Examining data/blcr-0.8.6~b3/libcr/cr_sig_sync.c
Examining data/blcr-0.8.6~b3/libcr/cr_strerror.c
Examining data/blcr-0.8.6~b3/libcr/cr_pthread.c
Examining data/blcr-0.8.6~b3/libcr/cr_async.c
Examining data/blcr-0.8.6~b3/config/cross_helper.c
Examining data/blcr-0.8.6~b3/vmadump4/vmadump_ppc.c
Examining data/blcr-0.8.6~b3/vmadump4/vmadstress.c
Examining data/blcr-0.8.6~b3/vmadump4/vmadump_x86_64.c
Examining data/blcr-0.8.6~b3/vmadump4/vmadlib.c
Examining data/blcr-0.8.6~b3/vmadump4/vmadtest.c
Examining data/blcr-0.8.6~b3/vmadump4/vmadump_ppc64.c
Examining data/blcr-0.8.6~b3/vmadump4/vmadump_i386.c
Examining data/blcr-0.8.6~b3/vmadump4/vmadump_sparc.c
Examining data/blcr-0.8.6~b3/vmadump4/vmadump_sparc64.c
Examining data/blcr-0.8.6~b3/vmadump4/vmadump_arm.c
Examining data/blcr-0.8.6~b3/vmadump4/vmadump_alpha.c
Examining data/blcr-0.8.6~b3/vmadump4/vmadump_common.c
Examining data/blcr-0.8.6~b3/vmadump4/vmadcheck.c
Examining data/blcr-0.8.6~b3/vmadump4/vmadump_x86.h
Examining data/blcr-0.8.6~b3/vmadump4/vmadump.h
FINAL RESULTS:
data/blcr-0.8.6~b3/config/cross_helper.c:196:2: [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, msg);
data/blcr-0.8.6~b3/cr_module/cr_dest_file.c:222:3: [4] (format) sprintf:
Potential format string problem (CWE-134). Make format string constant.
sprintf(filename, CR_FILE_PATT, current->pid);
data/blcr-0.8.6~b3/cr_module/cr_ktrace.c:51:2: [4] (format) vsprintf:
Potential format string problem (CWE-134). Make format string constant.
vsprintf(cr_trace_buf, fmt, args);
data/blcr-0.8.6~b3/cr_module/cr_ktrace.c:100:2: [4] (format) vsprintf:
Potential format string problem (CWE-134). Make format string constant.
vsprintf(cr_trace_buf, fmt, args);
data/blcr-0.8.6~b3/cr_module/cr_ktrace.c:110:11: [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.
len = vsnprintf(p, eb->remain, fmt, args);
data/blcr-0.8.6~b3/cr_module/cr_ktrace.h:98:26: [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, 3, 4)));
data/blcr-0.8.6~b3/cr_module/cr_ktrace.h:175:26: [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, 5)));
data/blcr-0.8.6~b3/libcr/cr_trace.c:73:5: [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.
vsnprintf(libcr_trace_buf1, LIBCR_TRACE_MAX, format, args);
data/blcr-0.8.6~b3/libcr/cr_trace.h:41:26: [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, 5)));
data/blcr-0.8.6~b3/libcr/cr_trace.h:48:2: [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, args)
data/blcr-0.8.6~b3/tests/cb_exit.c:84:5: [4] (shell) execl:
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.
execl("/bin/bash", "sh", "-c", crut_aprintf("exit %d", code), NULL);
data/blcr-0.8.6~b3/tests/cb_exit.c:291: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.
rc = system(cmd);
data/blcr-0.8.6~b3/tests/cb_exit.c:309: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.
rc = system(cmd);
data/blcr-0.8.6~b3/tests/cb_exit.c:328: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.
rc = system(cmd);
data/blcr-0.8.6~b3/tests/cb_exit.c:346: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.
rc = system(cmd);
data/blcr-0.8.6~b3/tests/cb_exit.c:356: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.
rc = system(cmd);
data/blcr-0.8.6~b3/tests/cb_exit.c:371: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.
rc = system(cmd);
data/blcr-0.8.6~b3/tests/cb_exit.c:381: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.
rc = system(cmd);
data/blcr-0.8.6~b3/tests/cb_exit.c:396: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.
rc = system(cmd);
data/blcr-0.8.6~b3/tests/cb_exit.c:406: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.
rc = system(cmd);
data/blcr-0.8.6~b3/tests/cb_exit.c:422: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.
rc = system(cmd);
data/blcr-0.8.6~b3/tests/cb_exit.c:432: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.
rc = system(cmd);
data/blcr-0.8.6~b3/tests/cb_exit.c:448: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.
rc = system(cmd);
data/blcr-0.8.6~b3/tests/cb_exit.c:458: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.
rc = system(cmd);
data/blcr-0.8.6~b3/tests/cb_exit.c:473: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.
rc = system(cmd);
data/blcr-0.8.6~b3/tests/cb_exit.c:483: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.
rc = system(cmd);
data/blcr-0.8.6~b3/tests/cb_exit.c:498: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.
rc = system(cmd);
data/blcr-0.8.6~b3/tests/cb_exit.c:516: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.
rc = system(cmd);
data/blcr-0.8.6~b3/tests/cb_exit.c:526: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.
rc = system(cmd);
data/blcr-0.8.6~b3/tests/crut_util.c:57:5: [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.
vsnprintf(buf, sizeof(buf), fmt, args);
data/blcr-0.8.6~b3/tests/crut_util.c:384: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.
if (0 == access(result, R_OK)) return result;
data/blcr-0.8.6~b3/tests/crut_util.c:397: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 (0 == access(result, X_OK)) return strdup(result);
data/blcr-0.8.6~b3/tests/crut_util.c:405: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 (0 == access(result, X_OK)) return result;
data/blcr-0.8.6~b3/tests/crut_util.c:525:13: [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.
add_len = vsnprintf(NULL, 0, fmt, args);
data/blcr-0.8.6~b3/tests/crut_util.c:537:3: [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.
vsnprintf((s + old_len), (old_len + add_len + 1), fmt, args2);
data/blcr-0.8.6~b3/tests/crut_util.h:47:41: [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, 5)));
data/blcr-0.8.6~b3/tests/crut_wrapper.c:71: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(stderr, format, args);
data/blcr-0.8.6~b3/tests/crut_wrapper.c:84: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(stdout, format, args);
data/blcr-0.8.6~b3/tests/crut_wrapper.c:96: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(stdout, format, args);
data/blcr-0.8.6~b3/tests/crut_wrapper.c:108: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(stdout, format, args);
data/blcr-0.8.6~b3/tests/crut_wrapper.c:263:2: [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.
execv(cmd[0], cmd);
data/blcr-0.8.6~b3/tests/crut_wrapper.c:283:12: [4] (shell) popen:
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.
pipe = popen(cmd, "r");
data/blcr-0.8.6~b3/tests/hugetlbfs.c:112: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(t->addr, MSG3);
data/blcr-0.8.6~b3/tests/hugetlbfs.c:143: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(t->addr, MSG1);
data/blcr-0.8.6~b3/tests/hugetlbfs.c:195: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(t->addr, MSG2);
data/blcr-0.8.6~b3/tests/hugetlbfs.c:208: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(t->addr, MSG1);
data/blcr-0.8.6~b3/tests/hugetlbfs.c:322: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(filename, mntpnt);
data/blcr-0.8.6~b3/tests/hugetlbfs.c:323: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(filename, FILESTEM);
data/blcr-0.8.6~b3/tests/hugetlbfs2.c:77: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(t->addr, MSG);
data/blcr-0.8.6~b3/tests/hugetlbfs2.c:222: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(filename, mntpnt);
data/blcr-0.8.6~b3/tests/hugetlbfs2.c:223: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(filename, FILESTEM);
data/blcr-0.8.6~b3/tests/lam.c:46:9: [4] (shell) execl:
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.
execl("/bin/true", "true", NULL);
data/blcr-0.8.6~b3/tests/linked_fifo.c:107: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(fifo->filename2, fifo->filename);
data/blcr-0.8.6~b3/tests/mmaps.c:123:6: [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(t->addr, MSG3);
data/blcr-0.8.6~b3/tests/mmaps.c:177: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(t->addr, MSG1);
data/blcr-0.8.6~b3/tests/mmaps.c:315: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(t->addr, MSG2);
data/blcr-0.8.6~b3/tests/mmaps.c:328: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(t->addr, MSG1);
data/blcr-0.8.6~b3/tests/overlap.c:46:18: [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.
int status = system(cmd);
data/blcr-0.8.6~b3/tests/pid_in_use.c:101: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.
rc = system(cmd);
data/blcr-0.8.6~b3/tests/pid_in_use.c:124: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.
rc = system(cmd);
data/blcr-0.8.6~b3/tests/pid_restore.c:104: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.
rc = system(cmd);
data/blcr-0.8.6~b3/tests/ptrace.c:128: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.
rc = system(cmd);
data/blcr-0.8.6~b3/tests/reloc_aux.c:57:11: [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.
ret = system(cmd);
data/blcr-0.8.6~b3/tests/save_aux.c:49:11: [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.
ret = system(cmd);
data/blcr-0.8.6~b3/tests/seq_wrapper.c:85:66: [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 verbose(const char *fmt, ...) __attribute__((format (printf, 1, 2)));
data/blcr-0.8.6~b3/tests/seq_wrapper.c:90:6: [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/blcr-0.8.6~b3/tests/seq_wrapper.c:122:9: [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(cmd, X_OK)) {
data/blcr-0.8.6~b3/tests/seq_wrapper.c:151:7: [4] (shell) execl:
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.
rc = execl(cmd, cmd, NULL);
data/blcr-0.8.6~b3/tests/stage0002.c:146: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.
rc = system(buf);
data/blcr-0.8.6~b3/tests/stage0003.c:159:2: [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(cmd, cmd, arg1, arg2, NULL);
data/blcr-0.8.6~b3/tests/stopped.c:205: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.
rc = system(cmd);
data/blcr-0.8.6~b3/tests/stopped.c:223:12: [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.
(void)execlp(rstrt_cmd, "cr_restart", sigarg, filename, NULL);
data/blcr-0.8.6~b3/tests/stopped.c:225:12: [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.
(void)execlp(rstrt_cmd, "cr_restart", filename, NULL);
data/blcr-0.8.6~b3/util/cr_checkpoint/cr_checkpoint.c:70:37: [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__ ((noreturn, format (printf, 2, 3)));
data/blcr-0.8.6~b3/util/cr_checkpoint/cr_checkpoint.c:72:27: [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/blcr-0.8.6~b3/util/cr_checkpoint/cr_checkpoint.c:186:5: [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(MY_NAME " version %s\n", CR_RELEASE_VERSION);
data/blcr-0.8.6~b3/util/cr_checkpoint/cr_checkpoint.c:224:7: [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, format, args);
data/blcr-0.8.6~b3/util/cr_checkpoint/cr_checkpoint.c:248:7: [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, format, args);
data/blcr-0.8.6~b3/util/cr_checkpoint/cr_checkpoint.c:745:6: [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(chkpt_to, parent_dir);
data/blcr-0.8.6~b3/util/cr_checkpoint/cr_checkpoint.c:747:6: [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(chkpt_to, basename(base));
data/blcr-0.8.6~b3/util/cr_checkpoint/cr_checkpoint.c:764: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.
err = access(chkpt_to, W_OK);
data/blcr-0.8.6~b3/util/cr_restart/cr_restart.c:75:15: [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.
int status = system(cmd);
data/blcr-0.8.6~b3/util/cr_restart/cr_restart.c:231:37: [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__ ((noreturn, format (printf, 3, 4)));
data/blcr-0.8.6~b3/util/cr_restart/cr_restart.c:249:7: [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, format, args);
data/blcr-0.8.6~b3/util/cr_restart/cr_restart.c:257:27: [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/blcr-0.8.6~b3/util/cr_restart/cr_restart.c:269:7: [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, format, args);
data/blcr-0.8.6~b3/util/cr_restart/cr_restart.c:276:5: [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(MY_NAME " version %s\n", CR_RELEASE_VERSION);
data/blcr-0.8.6~b3/vmadump4/vmadump_common.c:201: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(entry->libname, filename);
data/blcr-0.8.6~b3/libcr/cr_libinit.c:197:20: [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 *val = getenv("LIBCR_DISABLE_NSCD");
data/blcr-0.8.6~b3/libcr/cr_trace.c:53: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 *mask = getenv("LIBCR_TRACE_MASK");
data/blcr-0.8.6~b3/libcr/cr_trace.c:84:31: [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.
libcr_trace_to_syslog = (getenv("LIBCR_TRACE_TO_SYSLOG") != NULL);
data/blcr-0.8.6~b3/libcr/cr_trace.c:86:23: [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 *file = getenv("LIBCR_TRACE_FILE");
data/blcr-0.8.6~b3/tests/crut.c:477: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 opt = getopt_long(argc, argv, shortflags, longflags, &longindex);
data/blcr-0.8.6~b3/tests/crut_util.c:368: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.
const char *p = getenv("PATH");
data/blcr-0.8.6~b3/tests/crut_util.c:396: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.
if (NULL != (result = getenv(prog))) {
data/blcr-0.8.6~b3/tests/crut_wrapper.c:125:11: [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.
val = getenv("CRUT_TIMEOUT");
data/blcr-0.8.6~b3/tests/seq_wrapper.c:196:23: [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 *str = getenv("SEQ_STDERR_LIMIT");
data/blcr-0.8.6~b3/util/cr_checkpoint/cr_checkpoint.c:497: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 opt = getopt_long(argc, argv, shortflags, longflags, &longindex);
data/blcr-0.8.6~b3/util/cr_restart/cr_restart.c:609: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 opt = getopt_long(argc, argv, shortflags, longflags, &longindex);
data/blcr-0.8.6~b3/vmadump4/vmadlib.c:112: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, "hvclad")) != EOF) {
data/blcr-0.8.6~b3/vmadump4/vmadstress.c:125: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, "hvf:elo")) != EOF) {
data/blcr-0.8.6~b3/vmadump4/vmadtest.c:164: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, "hvf:Fduelox")) != EOF) {
data/blcr-0.8.6~b3/cr_module/cr_dest_file.c:218: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 filename[CR_FILE_MAX];
data/blcr-0.8.6~b3/cr_module/cr_fops.c:312:2: [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: ctrl_open,
data/blcr-0.8.6~b3/cr_module/cr_fops.c:376: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).
open: cr_open_EIO,
data/blcr-0.8.6~b3/cr_module/cr_io.c:842: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(out_buf, in_buf, len+1);
data/blcr-0.8.6~b3/cr_module/cr_io.c:857: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(p, ".blcr_%04x.%08lx", (unsigned int)current->pid, id);
data/blcr-0.8.6~b3/cr_module/cr_io.c:863: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(p, ".blcr_%04x.%016lx", (unsigned int)current->pid, id);
data/blcr-0.8.6~b3/cr_module/cr_kcompat.h:251: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(result, src, len);
data/blcr-0.8.6~b3/cr_module/cr_ktrace.c:35: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 cr_trace_buf[4096];
data/blcr-0.8.6~b3/cr_module/cr_ktrace.c:77: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[0]; // GNU (not ISO C99) variable length array
data/blcr-0.8.6~b3/cr_module/cr_pipes.c:358: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((void *)PIPE_BASE(*p_inode), buf, buf_len);
data/blcr-0.8.6~b3/cr_module/cr_pipes.c:390: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(kmap(page), p, count);
data/blcr-0.8.6~b3/cr_module/cr_pipes.c:789: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(buf, (void*)PIPE_BASE(*inode)+PIPE_START(*inode), cf_fifo.fifo_len);
data/blcr-0.8.6~b3/cr_module/cr_pipes.c:819: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.
memcpy(p, addr + pbuf->offset, pbuf->len);
data/blcr-0.8.6~b3/cr_module/cr_pipes.c:824: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.
memcpy(p, addr + pbuf->offset, pbuf->len);
data/blcr-0.8.6~b3/cr_module/cr_pipes.c:829: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.
memcpy(p, addr + pbuf->offset, pbuf->len);
data/blcr-0.8.6~b3/cr_module/cr_pipes.c:833: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.
memcpy(p, addr + pbuf->offset, pbuf->len);
data/blcr-0.8.6~b3/cr_module/cr_relocate.c:77: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(reloc_path, record->newpath, record->new_len);
data/blcr-0.8.6~b3/cr_module/cr_relocate.c:78: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(reloc_path+record->new_len, suffix, suff_len+1);
data/blcr-0.8.6~b3/examples/counting/counting.c:42: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).
limit = (i = atoi(argv[1])) > 0 ? i : limit;
data/blcr-0.8.6~b3/examples/file_counting/file_counting.c:42: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).
fp = fopen(filename, "w");
data/blcr-0.8.6~b3/examples/file_counting/file_counting.c:45: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).
limit = (i = atoi(argv[1])) > 0 ? i : limit;
data/blcr-0.8.6~b3/examples/io_bench/io_bench.c:115: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).
mb = atoi(argv[1]);
data/blcr-0.8.6~b3/examples/io_bench/io_bench.c:147: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[40];
data/blcr-0.8.6~b3/examples/io_bench/io_bench.c: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 = open(filename, O_WRONLY|O_CREAT|O_NOCTTY|O_NONBLOCK|O_TRUNC, 0400);
data/blcr-0.8.6~b3/examples/pipe_counting/pipe_counting.c:61: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).
limit = (i = atoi(argv[1])) > 0 ? i : limit;
data/blcr-0.8.6~b3/examples/pthread_counting/pthread_counting.c:94: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).
limit = (i = atoi(argv[1])) > 0 ? i : limit;
data/blcr-0.8.6~b3/examples/pthread_misc/pthread_misc.c:50: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[64];
data/blcr-0.8.6~b3/examples/pthread_misc/pthread_misc.c:59: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(filename, O_WRONLY | O_CREAT | O_TRUNC | O_LARGEFILE, 0600);
data/blcr-0.8.6~b3/examples/pthread_misc/pthread_misc.c:112: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 date[DATELEN];
data/blcr-0.8.6~b3/libcr/cr_ftb.c:109: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(prop.event_payload, data, len);
data/blcr-0.8.6~b3/libcr/cr_ftb.c:124: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(prop.event_payload, orig_handle, sizeof(FTB_event_handle_t));
data/blcr-0.8.6~b3/libcr/cr_ftb.c:126: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(prop.event_payload + sizeof(FTB_event_handle_t), data, len);
data/blcr-0.8.6~b3/libcr/cr_libinit.c:72: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(&ksa.ksa_mask, &act->sa_mask, sizeof (sigset_t));
data/blcr-0.8.6~b3/libcr/cr_libinit.c:82: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(&oact->sa_mask, &oksa.ksa_mask, sizeof (sigset_t));
data/blcr-0.8.6~b3/libcr/cr_private.h:127: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 path[PATH_MAX];
data/blcr-0.8.6~b3/libcr/cr_request.c:582: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 prev_name[PATH_MAX];
data/blcr-0.8.6~b3/libcr/cr_request.c:716: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[CONTEXT_NAMELEN];
data/blcr-0.8.6~b3/libcr/cr_trace.c:39: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 libcr_trace_buf1[LIBCR_TRACE_MAX];
data/blcr-0.8.6~b3/libcr/cr_trace.c:40: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 libcr_trace_buf2[LIBCR_TRACE_MAX];
data/blcr-0.8.6~b3/libcr/cr_trace.c:88:31: [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).
libcr_trace_fd = open(file, O_WRONLY|O_APPEND|O_CREAT, 0644);
data/blcr-0.8.6~b3/tests/cloexec.c:58: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).
p->fd0 = open(TEST_FILE, O_RDWR | O_CREAT | O_EXCL, 0600);
data/blcr-0.8.6~b3/tests/crut.c:153:5: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char cwd[PATH_MAX+1];
data/blcr-0.8.6~b3/tests/crut.c:361:13: [2] (buffer) memcpy:
Does not check for buffer overflows when copying to destination (CWE-120).
Make sure destination can always hold the source data.
memcpy(&crut_tests[i], test_ops, sizeof(*test_ops));
data/blcr-0.8.6~b3/tests/crut.c:403: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(filename, O_WRONLY | O_CREAT | O_TRUNC | O_LARGEFILE, 0600);
data/blcr-0.8.6~b3/tests/crut.h: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 test_name[CRUT_TESTNAME_MAX+1];
data/blcr-0.8.6~b3/tests/crut.h:57: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 test_description[CRUT_TESTDESC_MAX+1];
data/blcr-0.8.6~b3/tests/crut_util.c:54: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[4096];
data/blcr-0.8.6~b3/tests/crut_util.c:455: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[5];
data/blcr-0.8.6~b3/tests/crut_util_libcr.c:52: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).
rc = open(filename, O_WRONLY | O_CREAT | O_TRUNC | O_LARGEFILE, 0600);
data/blcr-0.8.6~b3/tests/crut_util_libcr.c:55: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).
rc = open("/dev/null", O_WRONLY | O_LARGEFILE);
data/blcr-0.8.6~b3/tests/crut_wrapper.c:54: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.
static const char *crut_cmd[6]; /* Max is PROG, -v, -d, -F, subtest, NULL */
data/blcr-0.8.6~b3/tests/crut_wrapper.c:126: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).
if (val && (atoi(val) > 0)) {
data/blcr-0.8.6~b3/tests/crut_wrapper.c:127: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).
test_timeout = atoi(val);
data/blcr-0.8.6~b3/tests/crut_wrapper.c:328: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(context_filename, O_RDONLY|O_LARGEFILE);
data/blcr-0.8.6~b3/tests/cwd.c:48: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 checkpoint_cwd[PATH_MAX+1];
data/blcr-0.8.6~b3/tests/cwd.c:103:5: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char new_cwd[PATH_MAX+1];
data/blcr-0.8.6~b3/tests/dev_null.c:57: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).
td->null = fd = open("/dev/null", O_RDWR);
data/blcr-0.8.6~b3/tests/dev_null.c:62: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).
td->zero = fd = open("/dev/zero", O_RDWR);
data/blcr-0.8.6~b3/tests/dev_null.c:67: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).
td->full = fd = open("/dev/full", O_WRONLY);
data/blcr-0.8.6~b3/tests/dpipe.c:56: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.
const char msg1[4] = { MSG_CHILD_READY, 'a', 'b', 'c' };
data/blcr-0.8.6~b3/tests/dpipe.c:57: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.
const char msg2[4] = { MSG_PARENT_READY, 'A', 'B', 'C' };
data/blcr-0.8.6~b3/tests/dup.c:214: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).
dupfds->fd1 = open(dupfds->filename,
data/blcr-0.8.6~b3/tests/edeadlk.c:100: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(filename, O_WRONLY | O_CREAT | O_TRUNC | O_LARGEFILE, 0600);
data/blcr-0.8.6~b3/tests/filedescriptors.c:86:5: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char filename[MAX_TEST_FILENAME+1];
data/blcr-0.8.6~b3/tests/filedescriptors.c:289: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_WRONLY | O_CREAT, TEST_FILE_MODE);
data/blcr-0.8.6~b3/tests/filedescriptors.c:357: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).
f->fd = open(f->filename, flags, TEST_FILE_MODE);
data/blcr-0.8.6~b3/tests/filedescriptors.c:750: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[BUF_SIZE];
data/blcr-0.8.6~b3/tests/forward.c:601: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(filename, O_WRONLY | O_CREAT | O_TRUNC | O_LARGEFILE, 0600);
data/blcr-0.8.6~b3/tests/forward.c:707: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(&the_forwardrequest, &myreq, sizeof(myreq));
data/blcr-0.8.6~b3/tests/hugetlbfs.c:90: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(filename, err&O_ACCMODE, 0);
data/blcr-0.8.6~b3/tests/hugetlbfs.c:152: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_CREAT|O_RDWR|O_TRUNC, S_IREAD|S_IWRITE);
data/blcr-0.8.6~b3/tests/hugetlbfs.c:259: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).
fp = fopen("/proc/meminfo", "r");
data/blcr-0.8.6~b3/tests/hugetlbfs.c:287: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).
fp = fopen("/proc/mounts", "r");
data/blcr-0.8.6~b3/tests/hugetlbfs.c:328: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_CREAT|O_RDWR|O_TRUNC, S_IREAD|S_IWRITE);
data/blcr-0.8.6~b3/tests/hugetlbfs2.c:86: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_CREAT|O_RDWR|O_TRUNC, S_IREAD|S_IWRITE);
data/blcr-0.8.6~b3/tests/hugetlbfs2.c:159: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).
fp = fopen("/proc/meminfo", "r");
data/blcr-0.8.6~b3/tests/hugetlbfs2.c:187: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).
fp = fopen("/proc/mounts", "r");
data/blcr-0.8.6~b3/tests/hugetlbfs2.c:228: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_CREAT|O_RDWR|O_TRUNC, S_IREAD|S_IWRITE);
data/blcr-0.8.6~b3/tests/linked_fifo.c:125: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).
fifo->rdwr_fd = open(fifo->filename, O_RDWR);
data/blcr-0.8.6~b3/tests/linked_fifo.c:131:23: [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).
fifo->client_fd = open(fifo->filename2, flags);
data/blcr-0.8.6~b3/tests/linked_fifo.c:179: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[BUFLEN];
data/blcr-0.8.6~b3/tests/linked_fifo.c:214: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[BUFLEN];
data/blcr-0.8.6~b3/tests/mmaps.c:91: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(FILENAME, err&O_ACCMODE, 0);
data/blcr-0.8.6~b3/tests/mmaps.c:142: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).
fd = open(FILENAME, O_RDONLY);
data/blcr-0.8.6~b3/tests/mmaps.c:192: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_CREAT|O_RDWR|O_TRUNC, S_IREAD|S_IWRITE);
data/blcr-0.8.6~b3/tests/named_fifo.c:109: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).
fifo->rdwr_fd = open(fifo->filename, O_RDWR);
data/blcr-0.8.6~b3/tests/named_fifo.c:115:23: [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).
fifo->client_fd = open(fifo->filename, flags);
data/blcr-0.8.6~b3/tests/named_fifo.c:161: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[BUFLEN];
data/blcr-0.8.6~b3/tests/named_fifo.c:196: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[BUFLEN];
data/blcr-0.8.6~b3/tests/pid_restore.c:127: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_RDONLY|O_LARGEFILE);
data/blcr-0.8.6~b3/tests/pipe.c:302: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[SMALL_BUF_SIZE];
data/blcr-0.8.6~b3/tests/pipe.c:365: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[SMALL_BUF_SIZE];
data/blcr-0.8.6~b3/tests/pipe.c:521: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[bufsize];
data/blcr-0.8.6~b3/tests/prctl.c:68: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 my_comm[32] = "testing\0";
data/blcr-0.8.6~b3/tests/prctl.c:158: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 tmp[32];
data/blcr-0.8.6~b3/tests/prctl.c:213: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 tmp[32];
data/blcr-0.8.6~b3/tests/reloc_aux.c:68: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(name, O_CREAT|O_RDWR|O_TRUNC, S_IREAD|S_IWRITE);
data/blcr-0.8.6~b3/tests/reloc_aux.c:82:5: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char buf[1024];
data/blcr-0.8.6~b3/tests/reloc_aux.c:105: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(name, O_RDWR);
data/blcr-0.8.6~b3/tests/reloc_aux.c:115: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/blcr-0.8.6~b3/tests/save_aux.c:109: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(filename, O_CREAT|O_RDWR|O_TRUNC, S_IREAD|S_IWRITE);
data/blcr-0.8.6~b3/tests/seq_wrapper.c:316: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).
exit_signal = atoi(line+11);
data/blcr-0.8.6~b3/tests/seq_wrapper.c:321: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).
exit_status = atoi(line+11);
data/blcr-0.8.6~b3/tests/seq_wrapper.c:326: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).
alarm(atoi(line+10));
data/blcr-0.8.6~b3/tests/seq_wrapper.c:327:34: [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).
verbose("@ set alarm %d\n", atoi(line+10));
data/blcr-0.8.6~b3/tests/simple.c:54: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(p, msg, sizeof(msg)+1);
data/blcr-0.8.6~b3/tests/stopped.c:118: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).
fp = fopen(procfile, "r");
data/blcr-0.8.6~b3/util/cr_checkpoint/cr_checkpoint.c:286: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).
if ((fd = open(filename, flags, 0400)) < 0) {
data/blcr-0.8.6~b3/util/cr_checkpoint/cr_checkpoint.c:316: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).
if ( (fd = open(dirname, O_NOCTTY|O_NONBLOCK)) == -1) {
data/blcr-0.8.6~b3/util/cr_checkpoint/cr_checkpoint.c:701: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[NAMELEN];
data/blcr-0.8.6~b3/util/cr_checkpoint/cr_checkpoint.c:707: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[NAMELEN];
data/blcr-0.8.6~b3/util/cr_checkpoint/cr_checkpoint.c:746:6: [2] (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 string.
strcat(chkpt_to, "/.");
data/blcr-0.8.6~b3/util/cr_checkpoint/cr_checkpoint.c:748:6: [2] (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 string.
strcat(chkpt_to, ".tmp");
data/blcr-0.8.6~b3/util/cr_restart/cr_restart.c:68: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_hooks[NUMHOOKS];
data/blcr-0.8.6~b3/util/cr_restart/cr_restart.c:799: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).
context_fd = open(context_filename, O_RDONLY | O_LARGEFILE);
data/blcr-0.8.6~b3/vmadump4/vmadcheck.c:83: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[PAGE_SIZE];
data/blcr-0.8.6~b3/vmadump4/vmadcheck.c:96: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 vmad_magic[4] = VMAD_MAGIC;
data/blcr-0.8.6~b3/vmadump4/vmadcheck.c:99: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[PAGE_SIZE];
data/blcr-0.8.6~b3/vmadump4/vmadcheck.c:114: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(argv[1], O_RDONLY);
data/blcr-0.8.6~b3/vmadump4/vmadlib.c:109: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[PATH_MAX];
data/blcr-0.8.6~b3/vmadump4/vmadstress.c:81: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_WRONLY|O_CREAT|O_TRUNC, DUMPMODE);
data/blcr-0.8.6~b3/vmadump4/vmadstress.c:94: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_RDONLY);
data/blcr-0.8.6~b3/vmadump4/vmadtest.c:95: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_WRONLY|O_CREAT|O_TRUNC, DUMPMODE);
data/blcr-0.8.6~b3/vmadump4/vmadtest.c:123: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_WRONLY|O_CREAT|O_TRUNC, DUMPMODE);
data/blcr-0.8.6~b3/vmadump4/vmadtest.c:196: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(filename, O_RDONLY);
data/blcr-0.8.6~b3/vmadump4/vmadump.h:29: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 magic[3];
data/blcr-0.8.6~b3/vmadump4/vmadump.h:73: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 tag[VMAD_HOOK_TAG_LEN];
data/blcr-0.8.6~b3/vmadump4/vmadump_alpha.c:101: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(regs, ®tmp, sizeof(regtmp));
data/blcr-0.8.6~b3/vmadump4/vmadump_alpha.c:102: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(ss, &sstmp, sizeof(sstmp)); /* Restores FP regs + saved regs */
data/blcr-0.8.6~b3/vmadump4/vmadump_arm.c:121: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(regs, ®tmp, sizeof(regtmp));
data/blcr-0.8.6~b3/vmadump4/vmadump_common.c:54: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 vmad_magic[3] = VMAD_MAGIC;
data/blcr-0.8.6~b3/vmadump4/vmadump_common.c:162: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 libname[0];
data/blcr-0.8.6~b3/vmadump4/vmadump_common.c:1072: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 value[TASK_COMM_LEN];
data/blcr-0.8.6~b3/vmadump4/vmadump_common.c:1207: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(¤t->blocked, &sig_blocked, sizeof(sig_blocked));
data/blcr-0.8.6~b3/vmadump4/vmadump_common.c:2018: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 value[TASK_COMM_LEN];
data/blcr-0.8.6~b3/vmadump4/vmadump_i386.c:185: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(regs, regtmp, sizeof(*regtmp));
data/blcr-0.8.6~b3/vmadump4/vmadump_ppc.c:134: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(regs, ®tmp, sizeof(regtmp));
data/blcr-0.8.6~b3/vmadump4/vmadump_ppc64.c:141: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(regs, ®tmp, sizeof(regtmp));
data/blcr-0.8.6~b3/vmadump4/vmadump_sparc.c:72: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(regs, ®tmp, sizeof(regtmp));
data/blcr-0.8.6~b3/vmadump4/vmadump_x86.h:203: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(vmad_task_i387(current), i387tmp, xstate_size);
data/blcr-0.8.6~b3/vmadump4/vmadump_x86_64.c:206: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(regs, regtmp, sizeof(*regtmp));
data/blcr-0.8.6~b3/cr_module/cr_chkpt_req.c:1480:40: [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 (copy_to_user(ubuf, path, 1+strlen(path))) {
data/blcr-0.8.6~b3/cr_module/cr_dump_self.c:161:9: [1] (access) umask:
Ensure that umask is given most restrictive possible setting (e.g., 066 or
077) (CWE-732).
int umask;
data/blcr-0.8.6~b3/cr_module/cr_dump_self.c:171:26: [1] (access) umask:
Ensure that umask is given most restrictive possible setting (e.g., 066 or
077) (CWE-732).
umask = current->fs->umask;
data/blcr-0.8.6~b3/cr_module/cr_dump_self.c:177:38: [1] (access) umask:
Ensure that umask is given most restrictive possible setting (e.g., 066 or
077) (CWE-732).
retval = cr_kwrite(eb, cf_filp, &umask, sizeof(umask));
data/blcr-0.8.6~b3/cr_module/cr_dump_self.c:177:52: [1] (access) umask:
Ensure that umask is given most restrictive possible setting (e.g., 066 or
077) (CWE-732).
retval = cr_kwrite(eb, cf_filp, &umask, sizeof(umask));
data/blcr-0.8.6~b3/cr_module/cr_dump_self.c:178:26: [1] (access) umask:
Ensure that umask is given most restrictive possible setting (e.g., 066 or
077) (CWE-732).
if (retval != sizeof(umask)) {
data/blcr-0.8.6~b3/cr_module/cr_fops.c:371:9: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
read: cr_read_EIO,
data/blcr-0.8.6~b3/cr_module/cr_io.c:250: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).
len = strlen(buf)+1;
data/blcr-0.8.6~b3/cr_module/cr_io.c:714: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).
int len = strlen(buf);
data/blcr-0.8.6~b3/cr_module/cr_io.c:831: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(in_buf);
data/blcr-0.8.6~b3/cr_module/cr_relocate.c:67: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).
suff_len = strlen(suffix);
data/blcr-0.8.6~b3/cr_module/cr_rstrt_req.c:2024:9: [1] (access) umask:
Ensure that umask is given most restrictive possible setting (e.g., 066 or
077) (CWE-732).
int umask;
data/blcr-0.8.6~b3/cr_module/cr_rstrt_req.c:2030:37: [1] (access) umask:
Ensure that umask is given most restrictive possible setting (e.g., 066 or
077) (CWE-732).
retval = cr_kread(eb, cf_filp, &umask, sizeof(umask));
data/blcr-0.8.6~b3/cr_module/cr_rstrt_req.c:2030:51: [1] (access) umask:
Ensure that umask is given most restrictive possible setting (e.g., 066 or
077) (CWE-732).
retval = cr_kread(eb, cf_filp, &umask, sizeof(umask));
data/blcr-0.8.6~b3/cr_module/cr_rstrt_req.c:2031:25: [1] (access) umask:
Ensure that umask is given most restrictive possible setting (e.g., 066 or
077) (CWE-732).
if (retval < sizeof(umask)) {
data/blcr-0.8.6~b3/cr_module/cr_rstrt_req.c:2750:43: [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 (copy_to_user(ubuf, path, 1+strlen(path))) {
data/blcr-0.8.6~b3/examples/pipe_counting/pipe_counting.c:42:11: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
rc = read(fd, p ,len);
data/blcr-0.8.6~b3/examples/pthread_misc/pthread_misc.c:128:2: [1] (buffer) strncpy:
Easily used incorrectly; doesn't always \0-terminate or check for invalid
pointers [MS-banned] (CWE-120).
strncpy(date, now(), DATELEN);
data/blcr-0.8.6~b3/libcr/cr_ftb.c:68:9: [1] (buffer) strncpy:
Easily used incorrectly; doesn't always \0-terminate or check for invalid
pointers [MS-banned] (CWE-120).
strncpy(cr_ftb_client_info.client_name, client_name, FTB_MAX_CLIENT_NAME);
data/blcr-0.8.6~b3/libcr/cr_ftb.c:71:9: [1] (buffer) strncpy:
Easily used incorrectly; doesn't always \0-terminate or check for invalid
pointers [MS-banned] (CWE-120).
strncpy(cr_ftb_client_info.client_jobid, client_jobid, FTB_MAX_CLIENT_JOBID);
data/blcr-0.8.6~b3/libcr/cr_request.c:659:6: [1] (buffer) strncpy:
Easily used incorrectly; doesn't always \0-terminate or check for invalid
pointers [MS-banned] (CWE-120).
strncpy(prev_name, filename, PATH_MAX);
data/blcr-0.8.6~b3/tests/crut.c:357:68: [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 (!strncmp(crut_tests[i].test_name, test_ops->test_name, strlen(test_ops->test_name))) {
data/blcr-0.8.6~b3/tests/crut.c:363:17: [1] (buffer) strncpy:
Easily used incorrectly; doesn't always \0-terminate or check for invalid
pointers [MS-banned] (CWE-120).
strncpy(crut_tests[i].test_name, noname, sizeof(noname));
data/blcr-0.8.6~b3/tests/crut_util.c:252:19: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
do { retval = read(pipes->inpipe, &c, 1); } while ((retval < 0) && (errno == EINTR));
data/blcr-0.8.6~b3/tests/crut_util.c:375: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).
dirlen = strlen(dir);
data/blcr-0.8.6~b3/tests/crut_util.c:476: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).
char *p = line + strlen(line) - 1;
data/blcr-0.8.6~b3/tests/crut_util.c:498: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).
have = strlen(line);
data/blcr-0.8.6~b3/tests/crut_util.c:508:9: [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).
have = strlen(line);
data/blcr-0.8.6~b3/tests/crut_util.c:529: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).
old_len = strlen(s);
data/blcr-0.8.6~b3/tests/crut_wrapper.c:135: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 ((val[0] != '-') || (strlen(val) != 2)) break;
data/blcr-0.8.6~b3/tests/dev_null.c:86:10: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
rc = read(td->null, &i, sizeof(i));
data/blcr-0.8.6~b3/tests/dev_null.c:105:10: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
rc = read(td->zero, &i, sizeof(i));
data/blcr-0.8.6~b3/tests/filedescriptors.c:181:14: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
retval = read(fd, buf, length);
data/blcr-0.8.6~b3/tests/filedescriptors.c:350:5: [1] (buffer) strncpy:
Easily used incorrectly; doesn't always \0-terminate or check for invalid
pointers [MS-banned] (CWE-120).
strncpy(f->filename, filename, MAX_TEST_FILENAME);
data/blcr-0.8.6~b3/tests/filedescriptors.c:781:14: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
retval = read(f->fd, buf, sizeof(*f));
data/blcr-0.8.6~b3/tests/forward.c:323:11: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
ret = read(pipefds[0], &status, sizeof(status));
data/blcr-0.8.6~b3/tests/forward.c:425:11: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
ret = read(pipefds[0], &status, sizeof(status));
data/blcr-0.8.6~b3/tests/linked_fifo.c:102: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).
fifo->filename2 = malloc(strlen(filename) + 2);
data/blcr-0.8.6~b3/tests/linked_fifo.c:108: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(fifo->filename2, "2");
data/blcr-0.8.6~b3/tests/linked_fifo.c:182:11: [1] (buffer) strncpy:
Easily used incorrectly; doesn't always \0-terminate or check for invalid
pointers [MS-banned] (CWE-120).
(void)strncpy(buf, PIPEDATA, sizeof(PIPEDATA));
data/blcr-0.8.6~b3/tests/linked_fifo.c:218:14: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
retval = read(fd, buf, BUFLEN);
data/blcr-0.8.6~b3/tests/named_fifo.c:164:11: [1] (buffer) strncpy:
Easily used incorrectly; doesn't always \0-terminate or check for invalid
pointers [MS-banned] (CWE-120).
(void)strncpy(buf, PIPEDATA, sizeof(PIPEDATA));
data/blcr-0.8.6~b3/tests/named_fifo.c:200:14: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
retval = read(fd, buf, BUFLEN);
data/blcr-0.8.6~b3/tests/pipe.c:305:5: [1] (buffer) strncpy:
Easily used incorrectly; doesn't always \0-terminate or check for invalid
pointers [MS-banned] (CWE-120).
strncpy(buf, PIPEDATA, sizeof(PIPEDATA));
data/blcr-0.8.6~b3/tests/pipe.c:389:14: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
retval = read(new_read_pipe_s.pipe_fd, buf, SMALL_BUF_SIZE);
data/blcr-0.8.6~b3/tests/pipe.c:481:14: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
retval = read(fd, &size, sizeof(size));
data/blcr-0.8.6~b3/tests/pipe.c:501:18: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
retval = read(fd, ((char *)buf) + bytes_read, size - bytes_read);
data/blcr-0.8.6~b3/tests/prctl.c:58:9: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
int read; // Value of 1st argument to read a value
data/blcr-0.8.6~b3/tests/prctl.c:125:28: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
result = prctl(elem->read, (unsigned long)&tmp);
data/blcr-0.8.6~b3/tests/prctl.c:131:28: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
result = prctl(elem->read, (unsigned long)&val); /* Read back */
data/blcr-0.8.6~b3/tests/prctl.c:142:28: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
result = prctl(elem->read, 0UL);
data/blcr-0.8.6~b3/tests/prctl.c:149:25: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
val = prctl(elem->read, 0UL); /* Read back again */
data/blcr-0.8.6~b3/tests/prctl.c:160:28: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
result = prctl(elem->read, tmp);
data/blcr-0.8.6~b3/tests/prctl.c:189:28: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
result = prctl(elem->read, (unsigned long)&tmp);
data/blcr-0.8.6~b3/tests/prctl.c:202:28: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
result = prctl(elem->read, 0UL);
data/blcr-0.8.6~b3/tests/prctl.c:215:28: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
result = prctl(elem->read, tmp);
data/blcr-0.8.6~b3/tests/reloc_aux.c:87:10: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
rc = read(fd, buf, sizeof(msg));
data/blcr-0.8.6~b3/tests/reloc_aux.c:121:10: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
rc = read(fd, buf, sizeof(msg));
data/blcr-0.8.6~b3/tests/replace_cb.c:46: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(1, s, strlen(s));
data/blcr-0.8.6~b3/util/cr_checkpoint/cr_checkpoint.c:742: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).
chkpt_to = (char *)malloc(strlen(chkpt_to) + 10);
data/blcr-0.8.6~b3/util/cr_checkpoint/cr_checkpoint.c:889: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).
int len = strlen(rename_to) + 10;
data/blcr-0.8.6~b3/util/cr_checkpoint/cr_checkpoint.c:905: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).
assert(rename_to && strlen(rename_to));
data/blcr-0.8.6~b3/util/cr_restart/cr_restart.c:298: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(path);
data/blcr-0.8.6~b3/util/cr_restart/cr_restart.c:344: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).
memmove(p, p+1, strlen(p+1) + 1/* for \0 */);
data/blcr-0.8.6~b3/vmadump4/vmadcheck.c:69:9: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
r = read(fd, p, bytes);
data/blcr-0.8.6~b3/vmadump4/vmadcheck.c:523:9: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
if (read(fd, &i, sizeof(i)) != 0) {
data/blcr-0.8.6~b3/vmadump4/vmadlib.c:101: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(line);
data/blcr-0.8.6~b3/vmadump4/vmadlib.c:171: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).
for (p = listbuf; *p; p += strlen(p)+1)
data/blcr-0.8.6~b3/vmadump4/vmadump_common.c:199:36: [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).
entry = kmalloc(sizeof(*entry)+strlen(filename)+1, GFP_KERNEL);
data/blcr-0.8.6~b3/vmadump4/vmadump_common.c:229:9: [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(entry->libname)+1;
data/blcr-0.8.6~b3/vmadump4/vmadump_common.c:276: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).
len = strlen(entry->libname);
data/blcr-0.8.6~b3/vmadump4/vmadump_common.c:1821: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).
head.namelen = strlen(filename);
ANALYSIS SUMMARY:
Hits = 315
Lines analyzed = 48446 in approximately 1.24 seconds (39130 lines/second)
Physical Source Lines of Code (SLOC) = 32347
Hits@level = [0] 738 [1] 72 [2] 141 [3] 14 [4] 88 [5] 0
Hits@level+ = [0+] 1053 [1+] 315 [2+] 243 [3+] 102 [4+] 88 [5+] 0
Hits/KSLOC@level+ = [0+] 32.5533 [1+] 9.73815 [2+] 7.51229 [3+] 3.15331 [4+] 2.7205 [5+] 0
Dot directories skipped = 1 (--followdotdir overrides)
Minimum risk level = 1
Not every hit is necessarily a security vulnerability.
There may be other security vulnerabilities; review your code!
See 'Secure Programming HOWTO'
(https://dwheeler.com/secure-programs) for more information.