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/vmem-1.8/src/common/alloc.c
Examining data/vmem-1.8/src/common/alloc.h
Examining data/vmem-1.8/src/common/ctl_fallocate.c
Examining data/vmem-1.8/src/common/dlsym.h
Examining data/vmem-1.8/src/common/errno_freebsd.h
Examining data/vmem-1.8/src/common/fault_injection.h
Examining data/vmem-1.8/src/common/file.c
Examining data/vmem-1.8/src/common/file.h
Examining data/vmem-1.8/src/common/file_posix.c
Examining data/vmem-1.8/src/common/file_windows.c
Examining data/vmem-1.8/src/common/mmap.c
Examining data/vmem-1.8/src/common/mmap.h
Examining data/vmem-1.8/src/common/mmap_posix.c
Examining data/vmem-1.8/src/common/mmap_windows.c
Examining data/vmem-1.8/src/common/os.h
Examining data/vmem-1.8/src/common/os_auto_flush_none.c
Examining data/vmem-1.8/src/common/os_posix.c
Examining data/vmem-1.8/src/common/os_thread.h
Examining data/vmem-1.8/src/common/os_thread_posix.c
Examining data/vmem-1.8/src/common/os_thread_windows.c
Examining data/vmem-1.8/src/common/os_windows.c
Examining data/vmem-1.8/src/common/out.c
Examining data/vmem-1.8/src/common/out.h
Examining data/vmem-1.8/src/common/pmemcommon.h
Examining data/vmem-1.8/src/common/pmemcompat.h
Examining data/vmem-1.8/src/common/pool_hdr.c
Examining data/vmem-1.8/src/common/pool_hdr.h
Examining data/vmem-1.8/src/common/queue.h
Examining data/vmem-1.8/src/common/rand.c
Examining data/vmem-1.8/src/common/rand.h
Examining data/vmem-1.8/src/common/sys_util.h
Examining data/vmem-1.8/src/common/util.c
Examining data/vmem-1.8/src/common/util.h
Examining data/vmem-1.8/src/common/util_pmem.h
Examining data/vmem-1.8/src/common/util_posix.c
Examining data/vmem-1.8/src/common/util_windows.c
Examining data/vmem-1.8/src/common/uuid.h
Examining data/vmem-1.8/src/common/valgrind/drd.h
Examining data/vmem-1.8/src/common/valgrind/helgrind.h
Examining data/vmem-1.8/src/common/valgrind/memcheck.h
Examining data/vmem-1.8/src/common/valgrind/pmemcheck.h
Examining data/vmem-1.8/src/common/valgrind/valgrind.h
Examining data/vmem-1.8/src/common/valgrind_internal.h
Examining data/vmem-1.8/src/examples/ex_common.h
Examining data/vmem-1.8/src/examples/libvmem/libart/art.c
Examining data/vmem-1.8/src/examples/libvmem/libart/art.h
Examining data/vmem-1.8/src/examples/libvmem/libart/arttree.c
Examining data/vmem-1.8/src/examples/libvmem/libart/arttree.h
Examining data/vmem-1.8/src/examples/libvmem/manpage.c
Examining data/vmem-1.8/src/freebsd/include/endian.h
Examining data/vmem-1.8/src/freebsd/include/features.h
Examining data/vmem-1.8/src/freebsd/include/linux/kdev_t.h
Examining data/vmem-1.8/src/freebsd/include/linux/limits.h
Examining data/vmem-1.8/src/freebsd/include/sys/sysmacros.h
Examining data/vmem-1.8/src/include/libvmem.h
Examining data/vmem-1.8/src/include/libvmmalloc.h
Examining data/vmem-1.8/src/jemalloc/include/jemalloc/internal/arena.h
Examining data/vmem-1.8/src/jemalloc/include/jemalloc/internal/atomic.h
Examining data/vmem-1.8/src/jemalloc/include/jemalloc/internal/base.h
Examining data/vmem-1.8/src/jemalloc/include/jemalloc/internal/bitmap.h
Examining data/vmem-1.8/src/jemalloc/include/jemalloc/internal/chunk.h
Examining data/vmem-1.8/src/jemalloc/include/jemalloc/internal/chunk_dss.h
Examining data/vmem-1.8/src/jemalloc/include/jemalloc/internal/chunk_mmap.h
Examining data/vmem-1.8/src/jemalloc/include/jemalloc/internal/ckh.h
Examining data/vmem-1.8/src/jemalloc/include/jemalloc/internal/ctl.h
Examining data/vmem-1.8/src/jemalloc/include/jemalloc/internal/extent.h
Examining data/vmem-1.8/src/jemalloc/include/jemalloc/internal/hash.h
Examining data/vmem-1.8/src/jemalloc/include/jemalloc/internal/huge.h
Examining data/vmem-1.8/src/jemalloc/include/jemalloc/internal/jemalloc_internal_decls.h
Examining data/vmem-1.8/src/jemalloc/include/jemalloc/internal/jemalloc_internal_macros.h
Examining data/vmem-1.8/src/jemalloc/include/jemalloc/internal/mb.h
Examining data/vmem-1.8/src/jemalloc/include/jemalloc/internal/mutex.h
Examining data/vmem-1.8/src/jemalloc/include/jemalloc/internal/pool.h
Examining data/vmem-1.8/src/jemalloc/include/jemalloc/internal/prng.h
Examining data/vmem-1.8/src/jemalloc/include/jemalloc/internal/prof.h
Examining data/vmem-1.8/src/jemalloc/include/jemalloc/internal/ql.h
Examining data/vmem-1.8/src/jemalloc/include/jemalloc/internal/qr.h
Examining data/vmem-1.8/src/jemalloc/include/jemalloc/internal/quarantine.h
Examining data/vmem-1.8/src/jemalloc/include/jemalloc/internal/rb.h
Examining data/vmem-1.8/src/jemalloc/include/jemalloc/internal/rtree.h
Examining data/vmem-1.8/src/jemalloc/include/jemalloc/internal/stats.h
Examining data/vmem-1.8/src/jemalloc/include/jemalloc/internal/tcache.h
Examining data/vmem-1.8/src/jemalloc/include/jemalloc/internal/tsd.h
Examining data/vmem-1.8/src/jemalloc/include/jemalloc/internal/util.h
Examining data/vmem-1.8/src/jemalloc/include/jemalloc/internal/valgrind.h
Examining data/vmem-1.8/src/jemalloc/include/jemalloc/internal/vector.h
Examining data/vmem-1.8/src/jemalloc/include/msvc_compat/C99/inttypes.h
Examining data/vmem-1.8/src/jemalloc/include/msvc_compat/C99/stdbool.h
Examining data/vmem-1.8/src/jemalloc/include/msvc_compat/C99/stdint.h
Examining data/vmem-1.8/src/jemalloc/include/msvc_compat/inttypes.h
Examining data/vmem-1.8/src/jemalloc/include/msvc_compat/stdint.h
Examining data/vmem-1.8/src/jemalloc/include/msvc_compat/strings.h
Examining data/vmem-1.8/src/jemalloc/include/msvc_compat/windows_extra.h
Examining data/vmem-1.8/src/jemalloc/src/arena.c
Examining data/vmem-1.8/src/jemalloc/src/atomic.c
Examining data/vmem-1.8/src/jemalloc/src/base.c
Examining data/vmem-1.8/src/jemalloc/src/bitmap.c
Examining data/vmem-1.8/src/jemalloc/src/chunk.c
Examining data/vmem-1.8/src/jemalloc/src/chunk_dss.c
Examining data/vmem-1.8/src/jemalloc/src/chunk_mmap.c
Examining data/vmem-1.8/src/jemalloc/src/ckh.c
Examining data/vmem-1.8/src/jemalloc/src/ctl.c
Examining data/vmem-1.8/src/jemalloc/src/extent.c
Examining data/vmem-1.8/src/jemalloc/src/hash.c
Examining data/vmem-1.8/src/jemalloc/src/huge.c
Examining data/vmem-1.8/src/jemalloc/src/jemalloc.c
Examining data/vmem-1.8/src/jemalloc/src/mb.c
Examining data/vmem-1.8/src/jemalloc/src/mutex.c
Examining data/vmem-1.8/src/jemalloc/src/pool.c
Examining data/vmem-1.8/src/jemalloc/src/prof.c
Examining data/vmem-1.8/src/jemalloc/src/quarantine.c
Examining data/vmem-1.8/src/jemalloc/src/rtree.c
Examining data/vmem-1.8/src/jemalloc/src/stats.c
Examining data/vmem-1.8/src/jemalloc/src/tcache.c
Examining data/vmem-1.8/src/jemalloc/src/tsd.c
Examining data/vmem-1.8/src/jemalloc/src/util.c
Examining data/vmem-1.8/src/jemalloc/src/valgrind.c
Examining data/vmem-1.8/src/jemalloc/src/vector.c
Examining data/vmem-1.8/src/jemalloc/src/zone.c
Examining data/vmem-1.8/src/jemalloc/test/include/test/SFMT-alti.h
Examining data/vmem-1.8/src/jemalloc/test/include/test/SFMT-params.h
Examining data/vmem-1.8/src/jemalloc/test/include/test/SFMT-params11213.h
Examining data/vmem-1.8/src/jemalloc/test/include/test/SFMT-params1279.h
Examining data/vmem-1.8/src/jemalloc/test/include/test/SFMT-params132049.h
Examining data/vmem-1.8/src/jemalloc/test/include/test/SFMT-params19937.h
Examining data/vmem-1.8/src/jemalloc/test/include/test/SFMT-params216091.h
Examining data/vmem-1.8/src/jemalloc/test/include/test/SFMT-params2281.h
Examining data/vmem-1.8/src/jemalloc/test/include/test/SFMT-params4253.h
Examining data/vmem-1.8/src/jemalloc/test/include/test/SFMT-params44497.h
Examining data/vmem-1.8/src/jemalloc/test/include/test/SFMT-params607.h
Examining data/vmem-1.8/src/jemalloc/test/include/test/SFMT-params86243.h
Examining data/vmem-1.8/src/jemalloc/test/include/test/SFMT-sse2.h
Examining data/vmem-1.8/src/jemalloc/test/include/test/SFMT.h
Examining data/vmem-1.8/src/jemalloc/test/include/test/math.h
Examining data/vmem-1.8/src/jemalloc/test/include/test/mq.h
Examining data/vmem-1.8/src/jemalloc/test/include/test/mtx.h
Examining data/vmem-1.8/src/jemalloc/test/include/test/test.h
Examining data/vmem-1.8/src/jemalloc/test/include/test/thd.h
Examining data/vmem-1.8/src/jemalloc/test/integration/MALLOCX_ARENA.c
Examining data/vmem-1.8/src/jemalloc/test/integration/aligned_alloc.c
Examining data/vmem-1.8/src/jemalloc/test/integration/allocated.c
Examining data/vmem-1.8/src/jemalloc/test/integration/allocm.c
Examining data/vmem-1.8/src/jemalloc/test/integration/chunk.c
Examining data/vmem-1.8/src/jemalloc/test/integration/mallocx.c
Examining data/vmem-1.8/src/jemalloc/test/integration/mremap.c
Examining data/vmem-1.8/src/jemalloc/test/integration/posix_memalign.c
Examining data/vmem-1.8/src/jemalloc/test/integration/rallocm.c
Examining data/vmem-1.8/src/jemalloc/test/integration/rallocx.c
Examining data/vmem-1.8/src/jemalloc/test/integration/thread_arena.c
Examining data/vmem-1.8/src/jemalloc/test/integration/thread_tcache_enabled.c
Examining data/vmem-1.8/src/jemalloc/test/integration/xallocx.c
Examining data/vmem-1.8/src/jemalloc/test/src/SFMT.c
Examining data/vmem-1.8/src/jemalloc/test/src/math.c
Examining data/vmem-1.8/src/jemalloc/test/src/mtx.c
Examining data/vmem-1.8/src/jemalloc/test/src/test.c
Examining data/vmem-1.8/src/jemalloc/test/src/thd.c
Examining data/vmem-1.8/src/jemalloc/test/unit/SFMT.c
Examining data/vmem-1.8/src/jemalloc/test/unit/bitmap.c
Examining data/vmem-1.8/src/jemalloc/test/unit/ckh.c
Examining data/vmem-1.8/src/jemalloc/test/unit/hash.c
Examining data/vmem-1.8/src/jemalloc/test/unit/junk.c
Examining data/vmem-1.8/src/jemalloc/test/unit/mallctl.c
Examining data/vmem-1.8/src/jemalloc/test/unit/math.c
Examining data/vmem-1.8/src/jemalloc/test/unit/mq.c
Examining data/vmem-1.8/src/jemalloc/test/unit/mtx.c
Examining data/vmem-1.8/src/jemalloc/test/unit/pool.h
Examining data/vmem-1.8/src/jemalloc/test/unit/pool_base_alloc.c
Examining data/vmem-1.8/src/jemalloc/test/unit/pool_custom_alloc.c
Examining data/vmem-1.8/src/jemalloc/test/unit/pool_custom_alloc_internal.c
Examining data/vmem-1.8/src/jemalloc/test/unit/prof_accum.c
Examining data/vmem-1.8/src/jemalloc/test/unit/prof_accum.h
Examining data/vmem-1.8/src/jemalloc/test/unit/prof_accum_a.c
Examining data/vmem-1.8/src/jemalloc/test/unit/prof_accum_b.c
Examining data/vmem-1.8/src/jemalloc/test/unit/prof_gdump.c
Examining data/vmem-1.8/src/jemalloc/test/unit/prof_idump.c
Examining data/vmem-1.8/src/jemalloc/test/unit/ql.c
Examining data/vmem-1.8/src/jemalloc/test/unit/qr.c
Examining data/vmem-1.8/src/jemalloc/test/unit/quarantine.c
Examining data/vmem-1.8/src/jemalloc/test/unit/rb.c
Examining data/vmem-1.8/src/jemalloc/test/unit/rtree.c
Examining data/vmem-1.8/src/jemalloc/test/unit/stats.c
Examining data/vmem-1.8/src/jemalloc/test/unit/tsd.c
Examining data/vmem-1.8/src/jemalloc/test/unit/util.c
Examining data/vmem-1.8/src/jemalloc/test/unit/zero.c
Examining data/vmem-1.8/src/libvmem/libvmem.c
Examining data/vmem-1.8/src/libvmem/libvmem_main.c
Examining data/vmem-1.8/src/libvmem/vmem.c
Examining data/vmem-1.8/src/libvmem/vmem.h
Examining data/vmem-1.8/src/libvmmalloc/libvmmalloc.c
Examining data/vmem-1.8/src/libvmmalloc/vmmalloc.h
Examining data/vmem-1.8/src/test/out_err/out_err.c
Examining data/vmem-1.8/src/test/out_err_mt/out_err_mt.c
Examining data/vmem-1.8/src/test/out_err_mt_win/out_err_mt_win.c
Examining data/vmem-1.8/src/test/out_err_win/out_err_win.c
Examining data/vmem-1.8/src/test/set_funcs/set_funcs.c
Examining data/vmem-1.8/src/test/signal_handle/signal_handle.c
Examining data/vmem-1.8/src/test/tools/anonymous_mmap/anonymous_mmap.c
Examining data/vmem-1.8/src/test/tools/dllview/dllview.c
Examining data/vmem-1.8/src/test/tools/fallocate_detect/fallocate_detect.c
Examining data/vmem-1.8/src/test/tools/sparsefile/sparsefile.c
Examining data/vmem-1.8/src/test/tools/usc_permission_check/usc_permission_check.c
Examining data/vmem-1.8/src/test/traces/traces.c
Examining data/vmem-1.8/src/test/traces_custom_function/traces_custom_function.c
Examining data/vmem-1.8/src/test/unittest/unittest.h
Examining data/vmem-1.8/src/test/unittest/ut.c
Examining data/vmem-1.8/src/test/unittest/ut_alloc.c
Examining data/vmem-1.8/src/test/unittest/ut_backtrace.c
Examining data/vmem-1.8/src/test/unittest/ut_file.c
Examining data/vmem-1.8/src/test/unittest/ut_pthread.c
Examining data/vmem-1.8/src/test/unittest/ut_signal.c
Examining data/vmem-1.8/src/test/util_file_create/util_file_create.c
Examining data/vmem-1.8/src/test/util_file_open/util_file_open.c
Examining data/vmem-1.8/src/test/util_is_absolute/util_is_absolute.c
Examining data/vmem-1.8/src/test/util_is_zeroed/util_is_zeroed.c
Examining data/vmem-1.8/src/test/util_map_proc/util_map_proc.c
Examining data/vmem-1.8/src/test/util_parse_size/util_parse_size.c
Examining data/vmem-1.8/src/test/vmem_aligned_alloc/vmem_aligned_alloc.c
Examining data/vmem-1.8/src/test/vmem_calloc/vmem_calloc.c
Examining data/vmem-1.8/src/test/vmem_check/vmem_check.c
Examining data/vmem-1.8/src/test/vmem_check_allocations/vmem_check_allocations.c
Examining data/vmem-1.8/src/test/vmem_check_version/vmem_check_version.c
Examining data/vmem-1.8/src/test/vmem_create/vmem_create.c
Examining data/vmem-1.8/src/test/vmem_create_error/vmem_create_error.c
Examining data/vmem-1.8/src/test/vmem_create_in_region/vmem_create_in_region.c
Examining data/vmem-1.8/src/test/vmem_create_win/vmem_create_win.c
Examining data/vmem-1.8/src/test/vmem_custom_alloc/vmem_custom_alloc.c
Examining data/vmem-1.8/src/test/vmem_malloc/vmem_malloc.c
Examining data/vmem-1.8/src/test/vmem_malloc_usable_size/vmem_malloc_usable_size.c
Examining data/vmem-1.8/src/test/vmem_mix_allocations/vmem_mix_allocations.c
Examining data/vmem-1.8/src/test/vmem_multiple_pools/vmem_multiple_pools.c
Examining data/vmem-1.8/src/test/vmem_out_of_memory/vmem_out_of_memory.c
Examining data/vmem-1.8/src/test/vmem_pages_purging/vmem_pages_purging.c
Examining data/vmem-1.8/src/test/vmem_realloc/vmem_realloc.c
Examining data/vmem-1.8/src/test/vmem_realloc_inplace/vmem_realloc_inplace.c
Examining data/vmem-1.8/src/test/vmem_stats/vmem_stats.c
Examining data/vmem-1.8/src/test/vmem_strdup/vmem_strdup.c
Examining data/vmem-1.8/src/test/vmem_valgrind/vmem_valgrind.c
Examining data/vmem-1.8/src/test/vmem_valgrind_region/vmem_valgrind_region.c
Examining data/vmem-1.8/src/test/vmmalloc_calloc/vmmalloc_calloc.c
Examining data/vmem-1.8/src/test/vmmalloc_check_allocations/vmmalloc_check_allocations.c
Examining data/vmem-1.8/src/test/vmmalloc_dummy_funcs/vmmalloc_dummy_funcs.c
Examining data/vmem-1.8/src/test/vmmalloc_dummy_funcs/vmmalloc_dummy_funcs.h
Examining data/vmem-1.8/src/test/vmmalloc_fork/vmmalloc_fork.c
Examining data/vmem-1.8/src/test/vmmalloc_init/libtest.c
Examining data/vmem-1.8/src/test/vmmalloc_init/libtest.h
Examining data/vmem-1.8/src/test/vmmalloc_init/vmmalloc_init.c
Examining data/vmem-1.8/src/test/vmmalloc_malloc/vmmalloc_malloc.c
Examining data/vmem-1.8/src/test/vmmalloc_malloc_hooks/vmmalloc_malloc_hooks.c
Examining data/vmem-1.8/src/test/vmmalloc_malloc_usable_size/vmmalloc_malloc_usable_size.c
Examining data/vmem-1.8/src/test/vmmalloc_memalign/vmmalloc_memalign.c
Examining data/vmem-1.8/src/test/vmmalloc_out_of_memory/vmmalloc_out_of_memory.c
Examining data/vmem-1.8/src/test/vmmalloc_realloc/vmmalloc_realloc.c
Examining data/vmem-1.8/src/test/vmmalloc_valgrind/vmmalloc_valgrind.c
Examining data/vmem-1.8/src/test/vmmalloc_valloc/vmmalloc_valloc.c
Examining data/vmem-1.8/src/test/win_common/win_common.c
Examining data/vmem-1.8/src/test/win_lists/win_lists.c
Examining data/vmem-1.8/src/test/win_mmap_dtor/win_mmap_dtor.c
Examining data/vmem-1.8/src/test/win_signal/win_signal.c
Examining data/vmem-1.8/src/windows/getopt/getopt.c
Examining data/vmem-1.8/src/windows/getopt/getopt.h
Examining data/vmem-1.8/src/windows/include/dirent.h
Examining data/vmem-1.8/src/windows/include/endian.h
Examining data/vmem-1.8/src/windows/include/err.h
Examining data/vmem-1.8/src/windows/include/features.h
Examining data/vmem-1.8/src/windows/include/libgen.h
Examining data/vmem-1.8/src/windows/include/linux/limits.h
Examining data/vmem-1.8/src/windows/include/platform.h
Examining data/vmem-1.8/src/windows/include/sched.h
Examining data/vmem-1.8/src/windows/include/strings.h
Examining data/vmem-1.8/src/windows/include/sys/file.h
Examining data/vmem-1.8/src/windows/include/sys/mman.h
Examining data/vmem-1.8/src/windows/include/sys/mount.h
Examining data/vmem-1.8/src/windows/include/sys/param.h
Examining data/vmem-1.8/src/windows/include/sys/resource.h
Examining data/vmem-1.8/src/windows/include/sys/statvfs.h
Examining data/vmem-1.8/src/windows/include/sys/uio.h
Examining data/vmem-1.8/src/windows/include/sys/wait.h
Examining data/vmem-1.8/src/windows/include/unistd.h
Examining data/vmem-1.8/src/windows/include/win_mmap.h
Examining data/vmem-1.8/src/windows/jemalloc_gen/include/jemalloc/internal/jemalloc_internal.h
Examining data/vmem-1.8/src/windows/jemalloc_gen/include/jemalloc/internal/jemalloc_internal_defs.h
Examining data/vmem-1.8/src/windows/jemalloc_gen/include/jemalloc/internal/private_namespace.h
Examining data/vmem-1.8/src/windows/jemalloc_gen/include/jemalloc/internal/private_unnamespace.h
Examining data/vmem-1.8/src/windows/jemalloc_gen/include/jemalloc/internal/public_namespace.h
Examining data/vmem-1.8/src/windows/jemalloc_gen/include/jemalloc/internal/public_unnamespace.h
Examining data/vmem-1.8/src/windows/jemalloc_gen/include/jemalloc/internal/size_classes.h
Examining data/vmem-1.8/src/windows/jemalloc_gen/include/jemalloc/jemalloc.h
Examining data/vmem-1.8/src/windows/jemalloc_gen/include/jemalloc/jemalloc_defs.h
Examining data/vmem-1.8/src/windows/jemalloc_gen/include/jemalloc/jemalloc_macros.h
Examining data/vmem-1.8/src/windows/jemalloc_gen/include/jemalloc/jemalloc_mangle.h
Examining data/vmem-1.8/src/windows/jemalloc_gen/include/jemalloc/jemalloc_mangle_jet.h
Examining data/vmem-1.8/src/windows/jemalloc_gen/include/jemalloc/jemalloc_protos.h
Examining data/vmem-1.8/src/windows/jemalloc_gen/include/jemalloc/jemalloc_protos_jet.h
Examining data/vmem-1.8/src/windows/jemalloc_gen/include/jemalloc/jemalloc_rename.h
Examining data/vmem-1.8/src/windows/jemalloc_gen/include/jemalloc/jemalloc_typedefs.h
Examining data/vmem-1.8/src/windows/win_mmap.c
Examining data/vmem-1.8/utils/check_license/check-license.c

FINAL RESULTS:

data/vmem-1.8/src/common/os_posix.c:158:9:  [5] (race) chmod:
  This accepts filename arguments; if an attacker can move those files, a
  race condition results. (CWE-362). Use fchmod( ) instead.
	return chmod(pathname, mode);
data/vmem-1.8/src/common/util_posix.c:136:7:  [5] (race) readlink:
  This accepts filename arguments; if an attacker can move those files or
  change the link content, a race condition results. Also, it does not
  terminate with ASCII NUL. (CWE-362, CWE-20). Reconsider approach.
	cc = readlink("/proc/self/exe", path, pathlen);
data/vmem-1.8/src/jemalloc/src/jemalloc.c:592:14:  [5] (race) readlink:
  This accepts filename arguments; if an attacker can move those files or
  change the link content, a race condition results. Also, it does not
  terminate with ASCII NUL. (CWE-362, CWE-20). Reconsider approach.
			linklen = readlink(linkname, buf, sizeof(buf) - 1);
data/vmem-1.8/src/common/file_posix.c:72: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).
	(void) strcpy(fullname, dir);
data/vmem-1.8/src/common/file_posix.c:73:9:  [4] (buffer) strcat:
  Does not check for buffer overflows when concatenating to destination
  [MS-banned] (CWE-120). Consider using strcat_s, strncat, strlcat, or
  snprintf (warning: strncat is easily misused).
	(void) strcat(fullname, templ);
data/vmem-1.8/src/common/mmap_posix.c:92:7:  [4] (buffer) sscanf:
  The scanf() family's %s operation, without a limit specification, permits
  buffer overflows (CWE-120, CWE-20). Specify a limit to %s, or use a
  different input function. If the scanf format is influenceable by an
  attacker, it's exploitable.
		if (sscanf(line, sscanf_os, &lo, &hi) == 2) {
data/vmem-1.8/src/common/os_posix.c:131: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.
	return access(pathname, mode);
data/vmem-1.8/src/common/os_posix.c:381:9:  [4] (shell) execv:
  This causes a new program to execute and is difficult to use safely
  (CWE-78). try using a library call that implements the same functionality
  if available.
	return execv(path, argv);
data/vmem-1.8/src/common/os_windows.c:268:2:  [4] (buffer) wcscpy:
  Does not check for buffer overflows when copying to destination [MS-banned]
  (CWE-120). Consider using a function version that stops copying at the end
  of the buffer.
	wcscpy(npath, path);
data/vmem-1.8/src/common/out.c:313:35:  [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.
static Vsnprintf_func Vsnprintf = vsnprintf;
data/vmem-1.8/src/common/out.c:335:41:  [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 = (vsnprintf_func == NULL) ? vsnprintf : vsnprintf_func;
data/vmem-1.8/src/common/util.c:98: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(lib_name, lib);
data/vmem-1.8/src/common/util.c:99:2:  [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(lib_name, suffix);
data/vmem-1.8/src/common/util.c:100: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(func_name, func);
data/vmem-1.8/src/common/util.c:101:2:  [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(func_name, suffix);
data/vmem-1.8/src/common/util.c:340: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(result, s1);
data/vmem-1.8/src/common/util.c:341:2:  [4] (buffer) strcat:
  Does not check for buffer overflows when concatenating to destination
  [MS-banned] (CWE-120). Consider using strcat_s, strncat, strlcat, or
  snprintf (warning: strncat is easily misused).
	strcat(result, s2);
data/vmem-1.8/src/examples/ex_common.h:59: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.
	return access(file, F_OK);
data/vmem-1.8/src/examples/libvmem/libart/arttree.c:352:7:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
		if (access(ctx->dirname, F_OK) == 0) {
data/vmem-1.8/src/examples/libvmem/libart/arttree.c:1310:2:  [4] (format) vfprintf:
  If format strings can be influenced by an attacker, they can be exploited
  (CWE-134). Use a constant for the format specification.
	vfprintf(stderr, fmt, ap);
data/vmem-1.8/src/jemalloc/include/jemalloc/internal/util.h:109: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.
    JEMALLOC_ATTR(format(printf, 3, 4));
data/vmem-1.8/src/jemalloc/include/jemalloc/internal/util.h:113:51:  [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.
    const char *format, ...) JEMALLOC_ATTR(format(printf, 3, 4));
data/vmem-1.8/src/jemalloc/include/jemalloc/internal/util.h:115: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.
    JEMALLOC_ATTR(format(printf, 1, 2));
data/vmem-1.8/src/jemalloc/src/prof.c:790:22:  [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.
JEMALLOC_ATTR(format(printf, 2, 3))
data/vmem-1.8/src/jemalloc/src/stats.c:23:2:  [4] (format) snprintf:
  If format strings can be influenced by an attacker, they can be exploited,
  and note that sprintf variations do not always \0-terminate (CWE-134). Use
  a constant for the format specification.
	snprintf(buf, sizeof(buf), n, p);				\
data/vmem-1.8/src/jemalloc/src/stats.c:35:2:  [4] (format) snprintf:
  If format strings can be influenced by an attacker, they can be exploited,
  and note that sprintf variations do not always \0-terminate (CWE-134). Use
  a constant for the format specification.
	snprintf(buf, sizeof(buf), n, p);				\
data/vmem-1.8/src/jemalloc/src/stats.c:47:2:  [4] (format) snprintf:
  If format strings can be influenced by an attacker, they can be exploited,
  and note that sprintf variations do not always \0-terminate (CWE-134). Use
  a constant for the format specification.
	snprintf(buf, sizeof(buf), n, p);				\
data/vmem-1.8/src/jemalloc/src/util.c:593:22:  [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.
JEMALLOC_ATTR(format(printf, 3, 4))
data/vmem-1.8/src/jemalloc/src/util.c:632:22:  [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.
JEMALLOC_ATTR(format(printf, 3, 4))
data/vmem-1.8/src/jemalloc/src/util.c:645:22:  [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.
JEMALLOC_ATTR(format(printf, 1, 2))
data/vmem-1.8/src/jemalloc/test/include/test/test.h:326:62:  [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.
void	test_skip(const char *format, ...) JEMALLOC_ATTR(format(printf, 1, 2));
data/vmem-1.8/src/jemalloc/test/include/test/test.h:327:62:  [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.
void	test_fail(const char *format, ...) JEMALLOC_ATTR(format(printf, 1, 2));
data/vmem-1.8/src/jemalloc/test/src/test.c:8:22:  [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.
JEMALLOC_ATTR(format(printf, 1, 2))
data/vmem-1.8/src/jemalloc/test/src/test.c:21:22:  [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.
JEMALLOC_ATTR(format(printf, 1, 2))
data/vmem-1.8/src/test/set_funcs/set_funcs.c:105: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((char *)p, s);
data/vmem-1.8/src/test/tools/sparsefile/sparsefile.c:62:2:  [4] (format) vfwprintf:
  If format strings can be influenced by an attacker, they can be exploited
  (CWE-134). Use a constant for the format specification.
	vfwprintf(stderr, fmt, ap);
data/vmem-1.8/src/test/traces_custom_function/traces_custom_function.c:89:12:  [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.
	ret_val = vsnprintf(str, size, format2, ap);
data/vmem-1.8/src/test/unittest/unittest.h:144:24:  [4] (format) printf:
  If format strings can be influenced by an attacker, they can be exploited
  (CWE-134). Use a constant for the format specification.
	__attribute__((format(printf, 6, 7)));
data/vmem-1.8/src/test/unittest/unittest.h:148:24:  [4] (format) printf:
  If format strings can be influenced by an attacker, they can be exploited
  (CWE-134). Use a constant for the format specification.
	__attribute__((format(printf, 6, 7)));
data/vmem-1.8/src/test/unittest/unittest.h:152:24:  [4] (format) printf:
  If format strings can be influenced by an attacker, they can be exploited
  (CWE-134). Use a constant for the format specification.
	__attribute__((format(printf, 4, 5)));
data/vmem-1.8/src/test/unittest/unittest.h:155:24:  [4] (format) printf:
  If format strings can be influenced by an attacker, they can be exploited
  (CWE-134). Use a constant for the format specification.
	__attribute__((format(printf, 4, 5)));
data/vmem-1.8/src/test/unittest/unittest.h:160:24:  [4] (format) printf:
  If format strings can be influenced by an attacker, they can be exploited
  (CWE-134). Use a constant for the format specification.
	__attribute__((format(printf, 4, 5)));
data/vmem-1.8/src/test/unittest/unittest.h:163:24:  [4] (format) printf:
  If format strings can be influenced by an attacker, they can be exploited
  (CWE-134). Use a constant for the format specification.
	__attribute__((format(printf, 4, 5)));
data/vmem-1.8/src/test/unittest/ut.c:262:8:  [4] (format) vsnprintf:
  If format strings can be influenced by an attacker, they can be exploited,
  and note that sprintf variations do not always \0-terminate (CWE-134). Use
  a constant for the format specification.
		sn = vsnprintf(&buf[cc], MAXPRINT - cc, fmt, ap);
data/vmem-1.8/src/test/vmem_custom_alloc/vmem_custom_alloc.c:161:3:  [4] (buffer) strcpy:
  Does not check for buffer overflows when copying to destination [MS-banned]
  (CWE-120). Consider using snprintf, strcpy_s, or strlcpy (warning: strncpy
  easily misused).
		strcpy(test, TEST_STRING_VALUE);
data/vmem-1.8/src/test/vmmalloc_fork/vmmalloc_fork.c:158:4:  [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/echo", "/bin/echo", "Hello world!", NULL);
data/vmem-1.8/src/windows/include/err.h:52:2:  [4] (format) vfprintf:
  If format strings can be influenced by an attacker, they can be exploited
  (CWE-134). Use a constant for the format specification.
	vfprintf(stderr, fmt, vl);
data/vmem-1.8/src/windows/include/err.h:66:2:  [4] (format) vfprintf:
  If format strings can be influenced by an attacker, they can be exploited
  (CWE-134). Use a constant for the format specification.
	vfprintf(stderr, fmt, vl);
data/vmem-1.8/src/windows/include/unistd.h:116:2:  [4] (buffer) sprintf:
  Does not check for buffer overflows (CWE-120). Use sprintf_s, snprintf, or
  vsnprintf.
	sprintf(path, "%s%s", fname, ext);
data/vmem-1.8/src/windows/win_mmap.c:480:4:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
			access,
data/vmem-1.8/src/windows/win_mmap.c:497:5:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
				access,
data/vmem-1.8/src/windows/win_mmap.c:533:15:  [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.
	mt->Access = access;
data/vmem-1.8/utils/check_license/check-license.c:71:26:  [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.
#define ERROR2(fmt, ...)	fprintf(stderr, fmt "\n", __VA_ARGS__)
data/vmem-1.8/utils/check_license/check-license.c:509:2:  [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(help_str, argv[0]);
data/vmem-1.8/src/common/file.c:176:16:  [3] (buffer) realpath:
  This function does not protect against buffer overflows, and some
  implementations can overflow internally (CWE-120/CWE-785!). Ensure that the
  destination buffer is at least of size MAXPATHLEN, andto protect against
  implementation problems, the input argument should also be checked to
  ensure it is no larger than MAXPATHLEN.
	char *rpath = realpath(spath, npath);
data/vmem-1.8/src/common/file_posix.c:228:12:  [3] (buffer) realpath:
  This function does not protect against buffer overflows, and some
  implementations can overflow internally (CWE-120/CWE-785!). Ensure that the
  destination buffer is at least of size MAXPATHLEN, andto protect against
  implementation problems, the input argument should also be checked to
  ensure it is no larger than MAXPATHLEN.
	daxpath = realpath(spath, NULL);
data/vmem-1.8/src/common/os_posix.c:356:9:  [3] (buffer) getenv:
  Environment variables are untrustable input if they can be set by an
  attacker. They can have any content and length, and the same variable can
  be set more than once (CWE-807, CWE-20). Check environment variables
  carefully before using them.
	return getenv(name);
data/vmem-1.8/src/common/os_thread_windows.c:112:2:  [3] (misc) InitializeCriticalSection:
  Exceptions can be thrown in low-memory situations. Use
  InitializeCriticalSectionAndSpinCount instead.
	InitializeCriticalSection(&mutex_internal->lock);
data/vmem-1.8/src/common/os_thread_windows.c:135:2:  [3] (misc) EnterCriticalSection:
  On some versions of Windows, exceptions can be thrown in low-memory
  situations. Use InitializeCriticalSectionAndSpinCount instead.
	EnterCriticalSection(&mutex_internal->lock);
data/vmem-1.8/src/common/os_windows.c:507: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.
	if (!overwrite && getenv(name))
data/vmem-1.8/src/common/os_windows.c:543:9:  [3] (buffer) getenv:
  Environment variables are untrustable input if they can be set by an
  attacker. They can have any content and length, and the same variable can
  be set more than once (CWE-807, CWE-20). Check environment variables
  carefully before using them.
	return getenv(name);
data/vmem-1.8/src/common/util.c:321:25:  [3] (buffer) getenv:
  Environment variables are untrustable input if they can be set by an
  attacker. They can have any content and length, and the same variable can
  be set more than once (CWE-807, CWE-20). Check environment variables
  carefully before using them.
		char *pmreorder_env = getenv("PMREORDER_EMIT_LOG");
data/vmem-1.8/src/common/util_posix.c:62:9:  [3] (buffer) realpath:
  This function does not protect against buffer overflows, and some
  implementations can overflow internally (CWE-120/CWE-785!). Ensure that the
  destination buffer is at least of size MAXPATHLEN, andto protect against
  implementation problems, the input argument should also be checked to
  ensure it is no larger than MAXPATHLEN.
	return realpath(path, NULL);
data/vmem-1.8/src/examples/libvmem/libart/arttree.c:290:17:  [3] (buffer) getopt:
  Some older implementations do not protect against internal buffer overflows
  (CWE-120, CWE-20). Check implementation on installation, or limit the size
  of all string inputs.
		while ((opt = getopt(ac, av, "m:n:s:")) != -1) {
data/vmem-1.8/src/examples/libvmem/libart/arttree.c:562:16:  [3] (buffer) getopt:
  Some older implementations do not protect against internal buffer overflows
  (CWE-120, CWE-20). Check implementation on installation, or limit the size
  of all string inputs.
	while ((opt = getopt(ac, av, "n:")) != -1) {
data/vmem-1.8/src/jemalloc/include/jemalloc/internal/mutex.h:103:3:  [3] (misc) EnterCriticalSection:
  On some versions of Windows, exceptions can be thrown in low-memory
  situations. Use InitializeCriticalSectionAndSpinCount instead.
		EnterCriticalSection(&mutex->lock);
data/vmem-1.8/src/jemalloc/include/jemalloc/internal/mutex.h:140:3:  [3] (misc) EnterCriticalSection:
  On some versions of Windows, exceptions can be thrown in low-memory
  situations. Use InitializeCriticalSectionAndSpinCount instead.
		EnterCriticalSection(&rwlock->lock);
data/vmem-1.8/src/jemalloc/include/jemalloc/internal/mutex.h:156:3:  [3] (misc) EnterCriticalSection:
  On some versions of Windows, exceptions can be thrown in low-memory
  situations. Use InitializeCriticalSectionAndSpinCount instead.
		EnterCriticalSection(&rwlock->lock);
data/vmem-1.8/src/jemalloc/src/jemalloc.c:612:16:  [3] (buffer) getenv:
  Environment variables are untrustable input if they can be set by an
  attacker. They can have any content and length, and the same variable can
  be set more than once (CWE-807, CWE-20). Check environment variables
  carefully before using them.
			if ((opts = getenv(envname)) != NULL) {
data/vmem-1.8/src/jemalloc/test/src/mtx.c:47:2:  [3] (misc) EnterCriticalSection:
  On some versions of Windows, exceptions can be thrown in low-memory
  situations. Use InitializeCriticalSectionAndSpinCount instead.
	EnterCriticalSection(&mtx->lock);
data/vmem-1.8/src/windows/getopt/getopt.c:60:5:  [3] (buffer) getopt:
  Some older implementations do not protect against internal buffer overflows
  (CWE-120, CWE-20). Check implementation on installation, or limit the size
  of all string inputs.
int getopt(int argc, char* const argv[], const char* optstring) {
data/vmem-1.8/src/windows/getopt/getopt.c:185:5:  [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 getopt_long(int argc, char* const argv[], const char* optstring,
data/vmem-1.8/src/windows/getopt/getopt.c:223:12:  [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.
    return getopt(argc, argv, optstring);
data/vmem-1.8/src/windows/getopt/getopt.h:49:5:  [3] (buffer) getopt:
  Some older implementations do not protect against internal buffer overflows
  (CWE-120, CWE-20). Check implementation on installation, or limit the size
  of all string inputs.
int getopt(int argc, char* const argv[], const char* optstring);
data/vmem-1.8/src/windows/getopt/getopt.h:51:5:  [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 getopt_long(int argc, char* const argv[],
data/vmem-1.8/src/common/file.c:77: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 spath[PATH_MAX];
data/vmem-1.8/src/common/file.c:91:2:  [2] (buffer) char:
  Statically-sized arrays can be improperly restricted, leading to potential
  overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
  functions that limit length, or ensure that the size is larger than the
  maximum possible length.
	char sizebuf[MAX_SIZE_LENGTH + 1];
data/vmem-1.8/src/common/file.c:169: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 spath[PATH_MAX];
data/vmem-1.8/src/common/file.c:175: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 npath[PATH_MAX];
data/vmem-1.8/src/common/file.c:430: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(ADDR_SUM(addr, offset), buffer, size);
data/vmem-1.8/src/common/file.c:483:2:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination (CWE-120).
  Make sure destination can always hold the source data.
	memcpy(buffer, ADDR_SUM(addr, offset), size);
data/vmem-1.8/src/common/file.h:56: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 filename[NAME_MAX + 1];
data/vmem-1.8/src/common/file_posix.c:117:11:  [2] (misc) open:
  Check when opening files - can an attacker redirect it (via symlinks),
  force the opening of special file type (e.g., device files), move things
  around to create a race condition, control its ancestors, or change its
  contents? (CWE-362).
	int fd = open(dir, O_TMPFILE | O_RDWR | flags, S_IRUSR | S_IWUSR);
data/vmem-1.8/src/common/file_posix.c:212: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 spath[PATH_MAX];
data/vmem-1.8/src/common/file_posix.c:243: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 sizebuf[MAX_SIZE_LENGTH + 1];
data/vmem-1.8/src/common/file_posix.c:333: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 dax_region_path[PATH_MAX];
data/vmem-1.8/src/common/file_posix.c:334: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 reg_id[DAX_REGION_ID_LEN];
data/vmem-1.8/src/common/mmap_posix.c:80:2:  [2] (buffer) char:
  Statically-sized arrays can be improperly restricted, leading to potential
  overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
  functions that limit length, or ensure that the size is larger than the
  maximum possible length.
	char line[PROCMAXLEN];	/* for fgets() */
data/vmem-1.8/src/common/os_posix.c:75:10:  [2] (misc) open:
  Check when opening files - can an attacker redirect it (via symlinks),
  force the opening of special file type (e.g., device files), move things
  around to create a race condition, control its ancestors, or change its
  contents? (CWE-362).
		return open(pathname, flags, (mode_t)mode);
data/vmem-1.8/src/common/os_posix.c:77:10:  [2] (misc) open:
  Check when opening files - can an attacker redirect it (via symlinks),
  force the opening of special file type (e.g., device files), move things
  around to create a race condition, control its ancestors, or change its
  contents? (CWE-362).
		return open(pathname, flags);
data/vmem-1.8/src/common/os_posix.c:140:9:  [2] (misc) fopen:
  Check when opening files - can an attacker redirect it (via symlinks),
  force the opening of special file type (e.g., device files), move things
  around to create a race condition, control its ancestors, or change its
  contents? (CWE-362).
	return fopen(pathname, mode);
data/vmem-1.8/src/common/os_posix.c:167:9:  [2] (tmpfile) mkstemp:
  Potential for temporary file vulnerability in some circumstances. Some
  older Unix-like systems create temp files with permission to write by all
  by default, so be sure to set the umask to override this. Also, some older
  Unix systems might fail to use O_EXCL when opening the file, so make sure
  that O_EXCL is used by the library (CWE-377).
	return mkstemp(temp);
data/vmem-1.8/src/common/os_thread.h:50: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 padding[44]; /* linux: 40 windows: 44 */
data/vmem-1.8/src/common/os_thread.h:55: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 padding[56]; /* linux: 56 windows: 13 */
data/vmem-1.8/src/common/os_thread.h:60: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 padding[48]; /* linux: 48 windows: 12 */
data/vmem-1.8/src/common/os_thread.h:65: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 padding[32]; /* linux: 8 windows: 32 */
data/vmem-1.8/src/common/os_thread.h:70: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 padding[16]; /* 16 to be safe */
data/vmem-1.8/src/common/os_thread.h:79: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 padding[56];  /* linux: 56 windows: 8 */
data/vmem-1.8/src/common/os_thread.h:84:2:  [2] (buffer) char:
  Statically-sized arrays can be improperly restricted, leading to potential
  overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
  functions that limit length, or ensure that the size is larger than the
  maximum possible length.
	char padding[56];  /* linux: 56 windows: 8 */
data/vmem-1.8/src/common/os_thread.h:89: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 padding[512];
data/vmem-1.8/src/common/os_windows.c:77: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 bom[3];
data/vmem-1.8/src/common/os_windows.c:424: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(it_buf, iov[i].iov_base, iov[i].iov_len);
data/vmem-1.8/src/common/out.c:71: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 msg[MAXPRINT];
data/vmem-1.8/src/common/out.c:73:2:  [2] (buffer) wchar_t:
  Statically-sized arrays can be improperly restricted, leading to potential
  overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
  functions that limit length, or ensure that the size is larger than the
  maximum possible length.
	wchar_t wmsg[MAXPRINT];
data/vmem-1.8/src/common/out.c:188: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).
		Log_level = atoi(log_level);
data/vmem-1.8/src/common/out.c:198: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 log_file_pid[PATH_MAX];
data/vmem-1.8/src/common/out.c:211:4:  [2] (buffer) char:
  Statically-sized arrays can be improperly restricted, leading to potential
  overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
  functions that limit length, or ensure that the size is larger than the
  maximum possible length.
			char buff[UTIL_MAX_ERR_MSG];
data/vmem-1.8/src/common/out.c:223: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).
		int align = atoi(log_alignment);
data/vmem-1.8/src/common/out.c:234:9:  [2] (buffer) char:
  Statically-sized arrays can be improperly restricted, leading to potential
  overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
  functions that limit length, or ensure that the size is larger than the
  maximum possible length.
	static char namepath[PATH_MAX];
data/vmem-1.8/src/common/out.c:363: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[MAXPRINT];
data/vmem-1.8/src/common/out.c:367: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 errstr[UTIL_MAX_ERR_MSG] = "";
data/vmem-1.8/src/common/out.c:420: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 errstr[UTIL_MAX_ERR_MSG] = "";
data/vmem-1.8/src/common/out.c:432:4:  [2] (buffer) strcpy:
  Does not check for buffer overflows when copying to destination [MS-banned]
  (CWE-120). Consider using snprintf, strcpy_s, or strlcpy (warning: strncpy
  easily misused). Risk is low because the source is a constant string.
			strcpy(errormsg, "Vsnprintf failed");
data/vmem-1.8/src/common/out.c:442:3:  [2] (buffer) char:
  Statically-sized arrays can be improperly restricted, leading to potential
  overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
  functions that limit length, or ensure that the size is larger than the
  maximum possible length.
		char buf[MAXPRINT];
data/vmem-1.8/src/common/pool_hdr.h:78: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 signature[POOL_HDR_SIG_LEN];
data/vmem-1.8/src/common/pool_hdr.h:88:11:  [2] (buffer) char:
  Statically-sized arrays can be improperly restricted, leading to potential
  overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
  functions that limit length, or ensure that the size is larger than the
  maximum possible length.
	unsigned char unused[1920];	/* must be zero */
data/vmem-1.8/src/common/pool_hdr.h:90:11:  [2] (buffer) char:
  Statically-sized arrays can be improperly restricted, leading to potential
  overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
  functions that limit length, or ensure that the size is larger than the
  maximum possible length.
	unsigned char unused2[1976];	/* must be zero */
data/vmem-1.8/src/common/util.c:75: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 lib_name[LIB_LOG_LEN];
data/vmem-1.8/src/common/util.c:76:2:  [2] (buffer) char:
  Statically-sized arrays can be improperly restricted, leading to potential
  overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
  functions that limit length, or ensure that the size is larger than the
  maximum possible length.
	char func_name[FUNC_LOG_LEN];
data/vmem-1.8/src/common/util.c:77: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 suffix[SUFFIX_LEN];
data/vmem-1.8/src/common/util.c:82:3:  [2] (buffer) strcpy:
  Does not check for buffer overflows when copying to destination [MS-banned]
  (CWE-120). Consider using snprintf, strcpy_s, or strlcpy (warning: strncpy
  easily misused). Risk is low because the source is a constant string.
		strcpy(suffix, ".BEGIN");
data/vmem-1.8/src/common/util.c:84:3:  [2] (buffer) strcpy:
  Does not check for buffer overflows when copying to destination [MS-banned]
  (CWE-120). Consider using snprintf, strcpy_s, or strlcpy (warning: strncpy
  easily misused). Risk is low because the source is a constant string.
		strcpy(suffix, ".END");
data/vmem-1.8/src/common/util.c:271: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 unit[9] = {0};
data/vmem-1.8/src/common/util.c:323:22:  [2] (integer) atoi:
  Unless checked, the resulting number can exceed the expected range
  (CWE-190). If source untrusted, check both minimum and maximum, even if the
  input had no minus sign (large numbers can roll over into negative number;
  consider saving to an unsigned value if that is intended).
			_Pmreorder_emit = atoi(pmreorder_env);
data/vmem-1.8/src/common/util_windows.c:161:13:  [2] (buffer) MultiByteToWideChar:
  Requires maximum length in CHARACTERS, not bytes (CWE-120).
	int size = MultiByteToWideChar(CP_UTF8, MB_ERR_INVALID_CHARS, str, -1,
data/vmem-1.8/src/common/util_windows.c:170:6:  [2] (buffer) MultiByteToWideChar:
  Requires maximum length in CHARACTERS, not bytes (CWE-120).
	if (MultiByteToWideChar(CP_UTF8, MB_ERR_INVALID_CHARS, str, -1, wstr,
data/vmem-1.8/src/common/util_windows.c:203:13:  [2] (buffer) MultiByteToWideChar:
  Requires maximum length in CHARACTERS, not bytes (CWE-120).
	int size = MultiByteToWideChar(CP_UTF8, MB_ERR_INVALID_CHARS, in,
data/vmem-1.8/src/common/util_windows.c:208:6:  [2] (buffer) MultiByteToWideChar:
  Requires maximum length in CHARACTERS, not bytes (CWE-120).
	if (MultiByteToWideChar(CP_UTF8, MB_ERR_INVALID_CHARS, in, -1,
data/vmem-1.8/src/common/util_windows.c:251:3:  [2] (buffer) strcpy:
  Does not check for buffer overflows when copying to destination [MS-banned]
  (CWE-120). Consider using snprintf, strcpy_s, or strlcpy (warning: strncpy
  easily misused). Risk is low because the source is a constant string.
		strcpy(path, "unknown");
data/vmem-1.8/src/common/uuid.h:64:18:  [2] (buffer) char:
  Statically-sized arrays can be improperly restricted, leading to potential
  overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
  functions that limit length, or ensure that the size is larger than the
  maximum possible length.
typedef unsigned char uuid_t[POOL_HDR_UUID_LEN]; /* 16 byte binary uuid value */
data/vmem-1.8/src/common/uuid.h:67:33:  [2] (buffer) char:
  Statically-sized arrays can be improperly restricted, leading to potential
  overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
  functions that limit length, or ensure that the size is larger than the
  maximum possible length.
int util_uuid_from_string(const char uuid[POOL_HDR_UUID_STR_LEN],
data/vmem-1.8/src/examples/libvmem/libart/art.c:428: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(l->key, key, key_len);
data/vmem-1.8/src/examples/libvmem/libart/art.c:429: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(l->value, value, val_len);
data/vmem-1.8/src/examples/libvmem/libart/art.c:450:2:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination (CWE-120).
  Make sure destination can always hold the source data.
	memcpy(dest->partial, src->partial,
data/vmem-1.8/src/examples/libvmem/libart/art.c:522: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(new->children, n->children,
data/vmem-1.8/src/examples/libvmem/libart/art.c:559: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(new->children, n->children,
data/vmem-1.8/src/examples/libvmem/libart/art.c:561: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(new->keys, n->keys,
data/vmem-1.8/src/examples/libvmem/libart/art.c:649: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(new->n.partial, key + depth,
data/vmem-1.8/src/examples/libvmem/libart/art.c:673: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(new->n.partial, n->partial,
data/vmem-1.8/src/examples/libvmem/libart/art.c:689:4:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination (CWE-120).
  Make sure destination can always hold the source data.
			memcpy(n->partial, l->key + depth + prefix_diff + 1,
data/vmem-1.8/src/examples/libvmem/libart/art.c:803: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(new->keys, n->keys, 4);
data/vmem-1.8/src/examples/libvmem/libart/art.c:804: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(new->children, n->children, 4 * sizeof(void *));
data/vmem-1.8/src/examples/libvmem/libart/art.c:832: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(n->n.partial + prefix,
data/vmem-1.8/src/examples/libvmem/libart/art.c:838:4:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination (CWE-120).
  Make sure destination can always hold the source data.
			memcpy(child->partial, n->n.partial,
data/vmem-1.8/src/examples/libvmem/libart/art.h:90:11:  [2] (buffer) char:
  Statically-sized arrays can be improperly restricted, leading to potential
  overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
  functions that limit length, or ensure that the size is larger than the
  maximum possible length.
	unsigned char partial[MAX_PREFIX_LEN];
data/vmem-1.8/src/examples/libvmem/libart/art.h:98:11:  [2] (buffer) char:
  Statically-sized arrays can be improperly restricted, leading to potential
  overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
  functions that limit length, or ensure that the size is larger than the
  maximum possible length.
	unsigned char keys[4];
data/vmem-1.8/src/examples/libvmem/libart/art.h:107:11:  [2] (buffer) char:
  Statically-sized arrays can be improperly restricted, leading to potential
  overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
  functions that limit length, or ensure that the size is larger than the
  maximum possible length.
	unsigned char keys[16];
data/vmem-1.8/src/examples/libvmem/libart/art.h:117:11:  [2] (buffer) char:
  Statically-sized arrays can be improperly restricted, leading to potential
  overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
  functions that limit length, or ensure that the size is larger than the
  maximum possible length.
	unsigned char keys[256];
data/vmem-1.8/src/examples/libvmem/libart/arttree.c:430:21:  [2] (buffer) char:
  Statically-sized arrays can be improperly restricted, leading to potential
  overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
  functions that limit length, or ensure that the size is larger than the
  maximum possible length.
		if (strcmp((const char *)map[idx].name,
data/vmem-1.8/src/examples/libvmem/libart/arttree.c:503:12:  [2] (misc) fopen:
  Check when opening files - can an attacker redirect it (via symlinks),
  force the opening of special file type (e.g., device files), move things
  around to create a race condition, control its ancestors, or change its
  contents? (CWE-362).
		out_fp = fopen(av[1], "w+");
data/vmem-1.8/src/examples/libvmem/libart/arttree.c:592:12:  [2] (misc) fopen:
  Check when opening files - can an attacker redirect it (via symlinks),
  force the opening of special file type (e.g., device files), move things
  around to create a race condition, control its ancestors, or change its
  contents? (CWE-362).
			in_fp = fopen(av[optind], "r");
data/vmem-1.8/src/examples/libvmem/libart/arttree.c:633: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 outbuf[1024];
data/vmem-1.8/src/examples/libvmem/libart/arttree.c:645:9:  [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.
				l = sprintf(p, "%c", (*s)&0xff);
data/vmem-1.8/src/examples/libvmem/libart/arttree.c:647:9:  [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.
				l = sprintf(p, "\\%.2x", (*s)&0xff);
data/vmem-1.8/src/examples/libvmem/libart/arttree.c:856:24:  [2] (buffer) char:
  Statically-sized arrays can be improperly restricted, leading to potential
  overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
  functions that limit length, or ensure that the size is larger than the
  maximum possible length.
		ctx->key = (unsigned char *)strdup(av[1]);
data/vmem-1.8/src/examples/libvmem/libart/arttree.c:904:24:  [2] (buffer) char:
  Statically-sized arrays can be improperly restricted, leading to potential
  overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
  functions that limit length, or ensure that the size is larger than the
  maximum possible length.
		ctx->key = (unsigned char *)strdup(av[1]);
data/vmem-1.8/src/examples/libvmem/libart/arttree.c:1018: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 *args[20];
data/vmem-1.8/src/examples/libvmem/manpage.c:60:2:  [2] (buffer) strcpy:
  Does not check for buffer overflows when copying to destination [MS-banned]
  (CWE-120). Consider using snprintf, strcpy_s, or strlcpy (warning: strncpy
  easily misused). Risk is low because the source is a constant string.
	strcpy(ptr, "hello, world");
data/vmem-1.8/src/jemalloc/include/jemalloc/internal/prof.h:205:8:  [2] (buffer) char:
  Statically-sized arrays can be improperly restricted, leading to potential
  overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
  functions that limit length, or ensure that the size is larger than the
  maximum possible length.
extern char	opt_prof_prefix[
data/vmem-1.8/src/jemalloc/src/arena.c:2323: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(ret, ptr, copysize);
data/vmem-1.8/src/jemalloc/src/chunk_mmap.c:44:4:  [2] (buffer) char:
  Statically-sized arrays can be improperly restricted, leading to potential
  overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
  functions that limit length, or ensure that the size is larger than the
  maximum possible length.
			char buf[BUFERROR_BUF];
data/vmem-1.8/src/jemalloc/src/chunk_mmap.c:70:3:  [2] (buffer) char:
  Statically-sized arrays can be improperly restricted, leading to potential
  overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
  functions that limit length, or ensure that the size is larger than the
  maximum possible length.
		char buf[BUFERROR_BUF];
data/vmem-1.8/src/jemalloc/src/ctl.c:610: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(astats, pool->ctl_stats.arenas, (pool->ctl_stats.narenas + 1) *
data/vmem-1.8/src/jemalloc/src/ctl.c:621: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(&tstats, &astats[pool->ctl_stats.narenas],
data/vmem-1.8/src/jemalloc/src/ctl.c:623: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(&astats[pool->ctl_stats.narenas],
data/vmem-1.8/src/jemalloc/src/ctl.c:625: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(&astats[pool->ctl_stats.narenas + 1], &tstats,
data/vmem-1.8/src/jemalloc/src/ctl.c:642: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(pool->arenas, arenas_old, pool->ctl_stats.narenas *
data/vmem-1.8/src/jemalloc/src/ctl.c:682: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(tarenas, pool->arenas, sizeof(arena_t *) * pool->ctl_stats.narenas);
data/vmem-1.8/src/jemalloc/src/ctl.c:1035:4:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination (CWE-120).
  Make sure destination can always hold the source data.
			memcpy(oldp, (void *)&(v), copylen);		\
data/vmem-1.8/src/jemalloc/src/ctl.c:1273:4:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination (CWE-120).
  Make sure destination can always hold the source data.
			memcpy(tseqno, tcache_tsd->seqno, tcache_tsd->npools * sizeof (unsigned));
data/vmem-1.8/src/jemalloc/src/ctl.c:1283:4:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination (CWE-120).
  Make sure destination can always hold the source data.
			memcpy(tcaches, tcache_tsd->tcaches, tcache_tsd->npools * sizeof (tcache_t *));
data/vmem-1.8/src/jemalloc/src/ctl.c:1412: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(tarenas, pool->arenas, sizeof(arena_t *) * pool->ctl_stats.narenas);
data/vmem-1.8/src/jemalloc/src/ctl.c:1858:83:  [2] (buffer) char:
  Statically-sized arrays can be improperly restricted, leading to potential
  overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
  functions that limit length, or ensure that the size is larger than the
  maximum possible length.
CTL_RO_GEN(stats_arenas_i_dss, pools[mib[1]]->ctl_stats.arenas[mib[4]].dss, const char *)
data/vmem-1.8/src/jemalloc/src/huge.c:250: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(ret, ptr, copysize);
data/vmem-1.8/src/jemalloc/src/jemalloc.c:316: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(tseqno, tsd->seqno, tsd->npools * sizeof (unsigned));
data/vmem-1.8/src/jemalloc/src/jemalloc.c:326: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(tarenas, tsd->arenas, tsd->npools * sizeof (arena_t *));
data/vmem-1.8/src/jemalloc/src/jemalloc.c:540: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[JE_PATH_MAX + 1];
data/vmem-1.8/src/jemalloc/src/jemalloc.c:1780: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(pools_new, pools, npools * sizeof (pool_t *));
data/vmem-1.8/src/jemalloc/src/mutex.c:76: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 bootstrap_pool[BOOTSTRAP_POOL_SIZE] __attribute__((aligned (16)));
data/vmem-1.8/src/jemalloc/src/prof.c:27: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		opt_prof_prefix[
data/vmem-1.8/src/jemalloc/src/prof.c:64:8:  [2] (buffer) char:
  Statically-sized arrays can be improperly restricted, leading to potential
  overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
  functions that limit length, or ensure that the size is larger than the
  maximum possible length.
static char		prof_dump_buf[
data/vmem-1.8/src/jemalloc/src/prof.c:119: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(ret->vec, bt->vec, bt->len * sizeof(void *));
data/vmem-1.8/src/jemalloc/src/prof.c:782: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(&prof_dump_buf[prof_dump_buf_end], &s[i], n);
data/vmem-1.8/src/jemalloc/src/prof.c:796: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[PROF_PRINTF_BUFSIZE];
data/vmem-1.8/src/jemalloc/src/prof.c:825: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(&ctx->cnt_summed, &ctx->cnt_merged, sizeof(prof_cnt_t));
data/vmem-1.8/src/jemalloc/src/prof.c:836:4:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination (CWE-120).
  Make sure destination can always hold the source data.
			memcpy(&tcnt, &thr_cnt->cnts, sizeof(prof_cnt_t));
data/vmem-1.8/src/jemalloc/src/prof.c:976: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 filename[JE_PATH_MAX + 1];
data/vmem-1.8/src/jemalloc/src/prof.c:985:8:  [2] (misc) open:
  Check when opening files - can an attacker redirect it (via symlinks),
  force the opening of special file type (e.g., device files), move things
  around to create a race condition, control its ancestors, or change its
  contents? (CWE-362).
	mfd = open(filename, O_RDONLY);
data/vmem-1.8/src/jemalloc/src/prof.c:1128: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 filename[DUMP_FILENAME_BUFSIZE];
data/vmem-1.8/src/jemalloc/src/prof.c:1147: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 filename[JE_PATH_MAX + 1];
data/vmem-1.8/src/jemalloc/src/prof.c:1173: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 filename_buf[DUMP_FILENAME_BUFSIZE];
data/vmem-1.8/src/jemalloc/src/prof.c:1197: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 filename[DUMP_FILENAME_BUFSIZE];
data/vmem-1.8/src/jemalloc/src/prof.c:1332: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(opt_prof_prefix, PROF_PREFIX_DEFAULT,
data/vmem-1.8/src/jemalloc/src/quarantine.c:61: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(ret->objs, &quarantine->objs[quarantine->first],
data/vmem-1.8/src/jemalloc/src/quarantine.c:69: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(ret->objs, &quarantine->objs[quarantine->first], ncopy_a
data/vmem-1.8/src/jemalloc/src/quarantine.c:71: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(&ret->objs[ncopy_a], quarantine->objs, ncopy_b *
data/vmem-1.8/src/jemalloc/src/stats.c:22: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[256];							\
data/vmem-1.8/src/jemalloc/src/stats.c:34: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[256];							\
data/vmem-1.8/src/jemalloc/src/stats.c:46:2:  [2] (buffer) char:
  Statically-sized arrays can be improperly restricted, leading to potential
  overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
  functions that limit length, or ensure that the size is larger than the
  maximum possible length.
	char buf[256];							\
data/vmem-1.8/src/jemalloc/src/tcache.c:437: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(tseqno, tsd->seqno, tsd->npools * sizeof (unsigned));
data/vmem-1.8/src/jemalloc/src/tcache.c:447: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(tcaches, tsd->tcaches, tsd->npools * sizeof (tcache_t *));
data/vmem-1.8/src/jemalloc/src/util.c:304: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(s, uppercase ? "0X" : "0x", 2);
data/vmem-1.8/src/jemalloc/src/util.c:324:3:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination (CWE-120).
  Make sure destination can always hold the source data.
		memcpy(&str[i], s, cpylen);				\
data/vmem-1.8/src/jemalloc/src/util.c:502: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[D2S_BUFSIZE];
data/vmem-1.8/src/jemalloc/src/util.c:512: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[O2S_BUFSIZE];
data/vmem-1.8/src/jemalloc/src/util.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[U2S_BUFSIZE];
data/vmem-1.8/src/jemalloc/src/util.c:530: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[X2S_BUFSIZE];
data/vmem-1.8/src/jemalloc/src/util.c:539:5:  [2] (buffer) char:
  Statically-sized arrays can be improperly restricted, leading to potential
  overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
  functions that limit length, or ensure that the size is larger than the
  maximum possible length.
				char buf[2];
data/vmem-1.8/src/jemalloc/src/util.c:563: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[X2S_BUFSIZE];
data/vmem-1.8/src/jemalloc/src/util.c:611: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[MALLOC_PRINTF_BUFSIZE];
data/vmem-1.8/src/jemalloc/test/include/test/test.h:7: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 prefix[ASSERT_BUFSIZE];				\
data/vmem-1.8/src/jemalloc/test/include/test/test.h:8:3:  [2] (buffer) char:
  Statically-sized arrays can be improperly restricted, leading to potential
  overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
  functions that limit length, or ensure that the size is larger than the
  maximum possible length.
		char message[ASSERT_BUFSIZE];				\
data/vmem-1.8/src/jemalloc/test/include/test/test.h:217: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 prefix[ASSERT_BUFSIZE];				\
data/vmem-1.8/src/jemalloc/test/include/test/test.h: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 message[ASSERT_BUFSIZE];				\
data/vmem-1.8/src/jemalloc/test/include/test/test.h:233: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 prefix[ASSERT_BUFSIZE];				\
data/vmem-1.8/src/jemalloc/test/include/test/test.h:234: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 message[ASSERT_BUFSIZE];				\
data/vmem-1.8/src/jemalloc/test/include/test/test.h:250: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 prefix[ASSERT_BUFSIZE];				\
data/vmem-1.8/src/jemalloc/test/include/test/test.h:251: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 message[ASSERT_BUFSIZE];				\
data/vmem-1.8/src/jemalloc/test/include/test/test.h:263: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 prefix[ASSERT_BUFSIZE];				\
data/vmem-1.8/src/jemalloc/test/include/test/test.h:264: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 message[ASSERT_BUFSIZE];				\
data/vmem-1.8/src/jemalloc/test/include/test/test.h:276: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 prefix[ASSERT_BUFSIZE];					\
data/vmem-1.8/src/jemalloc/test/include/test/test.h:277: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 message[ASSERT_BUFSIZE];					\
data/vmem-1.8/src/jemalloc/test/integration/aligned_alloc.c:94:6:  [2] (buffer) char:
  Statically-sized arrays can be improperly restricted, leading to potential
  overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
  functions that limit length, or ensure that the size is larger than the
  maximum possible length.
					char buf[BUFERROR_BUF];
data/vmem-1.8/src/jemalloc/test/integration/posix_memalign.c:88:6:  [2] (buffer) char:
  Statically-sized arrays can be improperly restricted, leading to potential
  overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
  functions that limit length, or ensure that the size is larger than the
  maximum possible length.
					char buf[BUFERROR_BUF];
data/vmem-1.8/src/jemalloc/test/integration/thread_arena.c:21:3:  [2] (buffer) char:
  Statically-sized arrays can be improperly restricted, leading to potential
  overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
  functions that limit length, or ensure that the size is larger than the
  maximum possible length.
		char buf[BUFERROR_BUF];
data/vmem-1.8/src/jemalloc/test/integration/thread_arena.c:29:3:  [2] (buffer) char:
  Statically-sized arrays can be improperly restricted, leading to potential
  overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
  functions that limit length, or ensure that the size is larger than the
  maximum possible length.
		char buf[BUFERROR_BUF];
data/vmem-1.8/src/jemalloc/test/integration/thread_arena.c:54:3:  [2] (buffer) char:
  Statically-sized arrays can be improperly restricted, leading to potential
  overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
  functions that limit length, or ensure that the size is larger than the
  maximum possible length.
		char buf[BUFERROR_BUF];
data/vmem-1.8/src/jemalloc/test/unit/hash.c:86:4:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination (CWE-120).
  Make sure destination can always hold the source data.
			memcpy(&hashes[i*hashbytes], &out, hashbytes);
data/vmem-1.8/src/jemalloc/test/unit/hash.c:91:4:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination (CWE-120).
  Make sure destination can always hold the source data.
			memcpy(&hashes[i*hashbytes], out, hashbytes);
data/vmem-1.8/src/jemalloc/test/unit/hash.c:96:4:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination (CWE-120).
  Make sure destination can always hold the source data.
			memcpy(&hashes[i*hashbytes], out, hashbytes);
data/vmem-1.8/src/jemalloc/test/unit/hash.c:106:3:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination (CWE-120).
  Make sure destination can always hold the source data.
		memcpy(final, &out, sizeof(out));
data/vmem-1.8/src/jemalloc/test/unit/hash.c:111: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(final, out, sizeof(out));
data/vmem-1.8/src/jemalloc/test/unit/hash.c:116: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(final, out, sizeof(out));
data/vmem-1.8/src/jemalloc/test/unit/junk.c:20:17:  [2] (buffer) char:
  Statically-sized arrays can be improperly restricted, leading to potential
  overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
  functions that limit length, or ensure that the size is larger than the
  maximum possible length.
		assert_c_eq(((char *)ptr)[i], 0x5a,
data/vmem-1.8/src/jemalloc/test/unit/junk.c:34:17:  [2] (buffer) char:
  Statically-sized arrays can be improperly restricted, leading to potential
  overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
  functions that limit length, or ensure that the size is larger than the
  maximum possible length.
		assert_c_eq(((char *)ptr)[i], 0x5a,
data/vmem-1.8/src/jemalloc/test/unit/pool.h:11: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 mem_pool[TEST_POOL_SIZE];
data/vmem-1.8/src/jemalloc/test/unit/pool.h:12: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 mem_extend_ok[TEST_POOL_SIZE];
data/vmem-1.8/src/jemalloc/test/unit/pool_custom_alloc.c:3: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 buff_alloc[4*1024];
data/vmem-1.8/src/jemalloc/test/unit/prof_accum.c:13: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("/dev/null", O_WRONLY);
data/vmem-1.8/src/jemalloc/test/unit/prof_gdump.c:16:7:  [2] (misc) open:
  Check when opening files - can an attacker redirect it (via symlinks),
  force the opening of special file type (e.g., device files), move things
  around to create a race condition, control its ancestors, or change its
  contents? (CWE-362).
	fd = open("/dev/null", O_WRONLY);
data/vmem-1.8/src/jemalloc/test/unit/prof_idump.c:18: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("/dev/null", O_WRONLY);
data/vmem-1.8/src/jemalloc/test/unit/util.c:141: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[BUFLEN];
data/vmem-1.8/src/jemalloc/test/unit/util.c:174: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[BUFLEN];
data/vmem-1.8/src/libvmem/vmem.c:198: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(vmp->hdr.signature, VMEM_HDR_SIG, POOL_HDR_SIG_LEN);
data/vmem-1.8/src/libvmem/vmem.c:287: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(vmp->hdr.signature, VMEM_HDR_SIG, POOL_HDR_SIG_LEN);
data/vmem-1.8/src/libvmem/vmem.c:459:17:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination (CWE-120).
  Make sure destination can always hold the source data.
	return (char *)memcpy(retaddr, s, size);
data/vmem-1.8/src/libvmem/vmem.c:476:20:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination (CWE-120).
  Make sure destination can always hold the source data.
	return (wchar_t *)memcpy(retaddr, s, size);
data/vmem-1.8/src/libvmmalloc/libvmmalloc.c:426: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(vmp->hdr.signature, VMEM_HDR_SIG, POOL_HDR_SIG_LEN);
data/vmem-1.8/src/libvmmalloc/libvmmalloc.c:489: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(addr, Vmp->addr, Vmp->size);
data/vmem-1.8/src/libvmmalloc/libvmmalloc.c:719:13:  [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).
		Forkopt = atoi(env_str);
data/vmem-1.8/src/test/out_err/out_err.c:51:2:  [2] (buffer) char:
  Statically-sized arrays can be improperly restricted, leading to potential
  overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
  functions that limit length, or ensure that the size is larger than the
  maximum possible length.
	char buff[UT_MAX_ERR_MSG];
data/vmem-1.8/src/test/out_err_win/out_err_win.c:51:2:  [2] (buffer) char:
  Statically-sized arrays can be improperly restricted, leading to potential
  overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
  functions that limit length, or ensure that the size is larger than the
  maximum possible length.
	char buff[UT_MAX_ERR_MSG];
data/vmem-1.8/src/test/tools/sparsefile/sparsefile.c:59:2:  [2] (buffer) wchar_t:
  Statically-sized arrays can be improperly restricted, leading to potential
  overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
  functions that limit length, or ensure that the size is larger than the
  maximum possible length.
	wchar_t errmsg[MAXPRINT];
data/vmem-1.8/src/test/unittest/ut.c:163: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(wargv2, wargv, wargc * sizeof(wchar_t *));
data/vmem-1.8/src/test/unittest/ut.c:205: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 Buff_out[MAXPRINT];
data/vmem-1.8/src/test/unittest/ut.c:206: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 Buff_err[MAXPRINT];
data/vmem-1.8/src/test/unittest/ut.c:207: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 Buff_trace[MAXPRINT];
data/vmem-1.8/src/test/unittest/ut.c:208: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 Buff_stdout[MAXPRINT];
data/vmem-1.8/src/test/unittest/ut.c:224: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[MAXPRINT];
data/vmem-1.8/src/test/unittest/ut.c:228: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 errstr[UT_MAX_ERR_MSG] = "";
data/vmem-1.8/src/test/unittest/ut.c:497: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 fdfile[PATH_MAX];
data/vmem-1.8/src/test/unittest/ut.c:505:11:  [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).
		fdnum = atoi(dp->d_name);
data/vmem-1.8/src/test/unittest/ut.c:528: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 fdfile[PATH_MAX];
data/vmem-1.8/src/test/unittest/ut.c:536:11:  [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).
		fdnum = atoi(dp->d_name);
data/vmem-1.8/src/test/unittest/ut.c:646: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 name[MAX_PATH];
data/vmem-1.8/src/test/unittest/ut.c:741: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 logname[MAXLOGFILENAME];
data/vmem-1.8/src/test/unittest/ut.c:773:14:  [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).
		LogLevel = atoi(os_getenv("UNITTEST_LOG_LEVEL"));
data/vmem-1.8/src/test/unittest/ut.c:1026:13:  [2] (buffer) MultiByteToWideChar:
  Requires maximum length in CHARACTERS, not bytes (CWE-120).
	int size = MultiByteToWideChar(CP_UTF8, MB_ERR_INVALID_CHARS, wstr, -1,
data/vmem-1.8/src/test/unittest/ut.c:1037:6:  [2] (buffer) MultiByteToWideChar:
  Requires maximum length in CHARACTERS, not bytes (CWE-120).
	if (MultiByteToWideChar(CP_UTF8, MB_ERR_INVALID_CHARS, wstr, -1, str,
data/vmem-1.8/src/test/unittest/ut_backtrace.c:75: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 procname[PROCNAMELEN];
data/vmem-1.8/src/test/util_is_zeroed/util_is_zeroed.c:47: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 bigbuf[3000];
data/vmem-1.8/src/test/vmem_create_error/vmem_create_error.c:41: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 mem_pool[VMEM_MIN_POOL];
data/vmem-1.8/src/test/vmem_stats/vmem_stats.c:113:25:  [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).
		expect_custom_alloc = atoi(argv[1]);
data/vmem-1.8/src/test/vmem_valgrind/vmem_valgrind.c:113: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).
		test_case = atoi(argv[1]);
data/vmem-1.8/src/test/vmem_valgrind_region/vmem_valgrind_region.c:45:2:  [2] (buffer) char:
  Statically-sized arrays can be improperly restricted, leading to potential
  overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
  functions that limit length, or ensure that the size is larger than the
  maximum possible length.
	char data[1]; /* dynamically sized */
data/vmem-1.8/src/test/vmem_valgrind_region/vmem_valgrind_region.c:91:13:  [2] (integer) atoi:
  Unless checked, the resulting number can exceed the expected range
  (CWE-190). If source untrusted, check both minimum and maximum, even if the
  input had no minus sign (large numbers can roll over into negative number;
  consider saving to an unsigned value if that is intended).
	int test = atoi(argv[1]);
data/vmem-1.8/src/test/vmmalloc_memalign/vmmalloc_memalign.c:63: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 buff[UT_MAX_ERR_MSG];
data/vmem-1.8/src/test/vmmalloc_valgrind/vmmalloc_valgrind.c:51: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).
	if ((argc != 2) || (test_case = atoi(argv[1])) > 2)
data/vmem-1.8/src/windows/include/unistd.h:112: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 fname[_MAX_FNAME];
data/vmem-1.8/src/windows/include/unistd.h:113: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 ext[_MAX_EXT];
data/vmem-1.8/src/windows/jemalloc_gen/include/jemalloc/internal/jemalloc_internal.h:990: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(p, ptr, copysize);
data/vmem-1.8/utils/check_license/check-license.c:110:22:  [2] (misc) open:
  Check when opening files - can an attacker redirect it (via symlinks),
  force the opening of special file type (e.g., device files), move things
  around to create a race condition, control its ancestors, or change its
  contents? (CWE-362).
	if ((file_pattern = open(path_pattern, O_RDONLY)) == -1) {
data/vmem-1.8/utils/check_license/check-license.c:138:22:  [2] (misc) open:
  Check when opening files - can an attacker redirect it (via symlinks),
  force the opening of special file type (e.g., device files), move things
  around to create a race condition, control its ancestors, or change its
  contents? (CWE-362).
	if ((file_pattern = open(path_pattern, O_WRONLY | O_CREAT | O_EXCL,
data/vmem-1.8/utils/check_license/check-license.c:175: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 comment_str[COMMENT_STR_LEN];
data/vmem-1.8/utils/check_license/check-license.c:270:2:  [2] (buffer) char:
  Statically-sized arrays can be improperly restricted, leading to potential
  overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
  functions that limit length, or ensure that the size is larger than the
  maximum possible length.
	char buffer[LICENSE_MAX_LEN];
data/vmem-1.8/utils/check_license/check-license.c:275:22:  [2] (misc) open:
  Check when opening files - can an attacker redirect it (via symlinks),
  force the opening of special file type (e.g., device files), move things
  around to create a race condition, control its ancestors, or change its
  contents? (CWE-362).
	if ((file_license = open(path_license, O_RDONLY)) == -1) {
data/vmem-1.8/utils/check_license/check-license.c:326: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 buffer[LICENSE_MAX_LEN];
data/vmem-1.8/utils/check_license/check-license.c:336: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).
	if ((file_to_check = open(path_to_check, O_RDONLY)) == -1) {
data/vmem-1.8/utils/check_license/check-license.c:369:16:  [2] (integer) atoi:
  Unless checked, the resulting number can exceed the expected range
  (CWE-190). If source untrusted, check both minimum and maximum, even if the
  input had no minus sign (large numbers can roll over into negative number;
  consider saving to an unsigned value if that is intended).
		year_first = atoi(copyright);
data/vmem-1.8/utils/check_license/check-license.c:396: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).
		year_last = atoi(copyright);
data/vmem-1.8/utils/check_license/check-license.c:446: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 pattern[LICENSE_MAX_LEN];
data/vmem-1.8/utils/check_license/check-license.c:460: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 pattern[LICENSE_MAX_LEN];
data/vmem-1.8/utils/check_license/check-license.c:475: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 pattern[LICENSE_MAX_LEN];
data/vmem-1.8/src/common/file.c:93:15:  [1] (buffer) read:
  Check buffer boundaries if used in a loop including recursive loops
  (CWE-120, CWE-20).
	if ((nread = read(fd, sizebuf, MAX_SIZE_LENGTH)) < 0) {
data/vmem-1.8/src/common/file.h:107:19:  [1] (buffer) read:
  Check buffer boundaries if used in a loop including recursive loops
  (CWE-120, CWE-20).
#define util_read	read
data/vmem-1.8/src/common/file.h:111:35:  [1] (buffer) read:
  Check buffer boundaries if used in a loop including recursive loops
  (CWE-120, CWE-20).
#define util_read(fd, buf, count)	read(fd, buf, (unsigned)(count))
data/vmem-1.8/src/common/file_posix.c:70: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).
	char *fullname = alloca(strlen(dir) + strlen(templ) + 1);
data/vmem-1.8/src/common/file_posix.c:70: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).
	char *fullname = alloca(strlen(dir) + strlen(templ) + 1);
data/vmem-1.8/src/common/file_posix.c:79:22:  [1] (access) umask:
  Ensure that umask is given most restrictive possible setting (e.g., 066 or
  077) (CWE-732).
	mode_t prev_umask = umask(S_IRWXG | S_IRWXO);
data/vmem-1.8/src/common/file_posix.c:83:2:  [1] (access) umask:
  Ensure that umask is given most restrictive possible setting (e.g., 066 or
  077) (CWE-732).
	umask(prev_umask);
data/vmem-1.8/src/common/file_posix.c:179:2:  [1] (buffer) strncpy:
  Easily used incorrectly; doesn't always \0-terminate or check for invalid
  pointers [MS-banned] (CWE-120).
	strncpy(info->filename, d->d_name, NAME_MAX + 1);
data/vmem-1.8/src/common/file_posix.c:257: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(spath);
data/vmem-1.8/src/common/file_posix.c:268:8:  [1] (buffer) read:
  Check buffer boundaries if used in a loop including recursive loops
  (CWE-120, CWE-20).
		rc = read(fd, sizebuf, MAX_SIZE_LENGTH);
data/vmem-1.8/src/common/file_posix.c:364:16:  [1] (buffer) read:
  Check buffer boundaries if used in a loop including recursive loops
  (CWE-120, CWE-20).
	ssize_t len = read(dax_reg_id_fd, reg_id, DAX_REGION_ID_LEN);
data/vmem-1.8/src/common/file_windows.c:72:15:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated; if given one it may
  perform an over-read (it could cause a crash if unprotected) (CWE-126).
	size_t len = strlen(dir) + strlen(templ) + 1;
data/vmem-1.8/src/common/file_windows.c:72: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).
	size_t len = strlen(dir) + strlen(templ) + 1;
data/vmem-1.8/src/common/file_windows.c:179:2:  [1] (buffer) strncpy:
  Easily used incorrectly; doesn't always \0-terminate or check for invalid
  pointers [MS-banned] (CWE-120).
	strncpy(info->filename, data.cFileName, NAME_MAX + 1);
data/vmem-1.8/src/common/os_windows.c:262:43:  [1] (buffer) wcslen:
  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).
	wchar_t *npath = Malloc(sizeof(*npath) * wcslen(path) + _MAX_FNAME);
data/vmem-1.8/src/common/os_windows.c:280:31:  [1] (buffer) wcslen:
  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 ret = _snwprintf(npath + wcslen(npath), _MAX_FNAME, L"%u", rnd);
data/vmem-1.8/src/common/out.c:199:16:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated; if given one it may
  perform an over-read (it could cause a crash if unprotected) (CWE-126).
		size_t len = strlen(log_file);
data/vmem-1.8/src/common/util.c:78: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).
	size_t lib_len = strlen(lib);
data/vmem-1.8/src/common/util.c:79:20:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated; if given one it may
  perform an over-read (it could cause a crash if unprotected) (CWE-126).
	size_t func_len = strlen(func);
data/vmem-1.8/src/common/util.c:86: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).
	size_t suffix_len = strlen(suffix);
data/vmem-1.8/src/common/util.c:227: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).
	int len = (int)strlen(str);
data/vmem-1.8/src/common/util.c:273:12:  [1] (buffer) sscanf:
  It's unclear if the %s limit in the format string is small enough
  (CWE-120). Check that the limit is sufficiently small, or use a different
  input function.
	int ret = sscanf(str, "%zu%8s", &size, unit);
data/vmem-1.8/src/common/util.c:336:24:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated; if given one it may
  perform an over-read (it could cause a crash if unprotected) (CWE-126).
	char *result = malloc(strlen(s1) + strlen(s2) + 1);
data/vmem-1.8/src/common/util.c:336:37:  [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 *result = malloc(strlen(s1) + strlen(s2) + 1);
data/vmem-1.8/src/common/util.c:384:2:  [1] (buffer) strncpy:
  Easily used incorrectly; doesn't always \0-terminate or check for invalid
  pointers [MS-banned] (CWE-120).
	strncpy(dst, src, max_length);
data/vmem-1.8/src/common/util.c:419: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).
		position = strlen(buffer);
data/vmem-1.8/src/common/util_posix.c:139:3:  [1] (buffer) strncpy:
  Easily used incorrectly; doesn't always \0-terminate or check for invalid
  pointers [MS-banned] (CWE-120). Risk is low because the source is a
  constant string.
		strncpy(path, "unknown", pathlen);
data/vmem-1.8/src/examples/libvmem/libart/arttree.c:868: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)strlen((const char *)ctx->key));
data/vmem-1.8/src/examples/libvmem/libart/arttree.c:872:10:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated; if given one it may
  perform an over-read (it could cause a crash if unprotected) (CWE-126).
					    strlen((const char *)ctx->key)));
data/vmem-1.8/src/examples/libvmem/libart/arttree.c:878:5:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated; if given one it may
  perform an over-read (it could cause a crash if unprotected) (CWE-126).
				strlen((const char *)ctx->key)));
data/vmem-1.8/src/examples/libvmem/libart/arttree.c:915: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).
			(int)strlen((const char *)ctx->key));
data/vmem-1.8/src/examples/libvmem/libart/arttree.c:919:10:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated; if given one it may
  perform an over-read (it could cause a crash if unprotected) (CWE-126).
					    strlen((const char *)ctx->key)));
data/vmem-1.8/src/examples/libvmem/libart/arttree.c:925:5:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated; if given one it may
  perform an over-read (it could cause a crash if unprotected) (CWE-126).
				strlen((const char *)ctx->key)));
data/vmem-1.8/src/examples/libvmem/libart/arttree.c:1016:11:  [1] (buffer) read:
  Check buffer boundaries if used in a loop including recursive loops
  (CWE-120, CWE-20).
		ssize_t read;
data/vmem-1.8/src/include/libvmmalloc.h:132:14:  [1] (free) memalign:
  On some systems (though not Linux-based systems) an attempt to free()
  results from memalign() may fail. This may, on a few systems, be
  exploitable. Also note that memalign() may not check that the boundary
  parameter is correct (CWE-676). Use posix_memalign instead (defined in
  POSIX's 1003.1d). Don't switch to valloc(); it is marked as obsolete in BSD
  4.3, as legacy in SUSv2, and is no longer defined in SUSv3. In some cases,
  malloc()'s alignment may be sufficient.
extern void *memalign(size_t boundary, size_t size)
data/vmem-1.8/src/jemalloc/src/ckh.c:532: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).
	hash(key, strlen((const char *)key), 0x94122f33U, r_hash);
data/vmem-1.8/src/jemalloc/src/ctl.c:816: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).
				if (strlen(child->name) == elen &&
data/vmem-1.8/src/jemalloc/src/jemalloc.c:87:30:  [1] (buffer) read:
  Check buffer boundaries if used in a loop including recursive loops
  (CWE-120, CWE-20).
# pragma section(".CRT$XCU", read)
data/vmem-1.8/src/jemalloc/src/jemalloc.c:707:5:  [1] (buffer) strncpy:
  Easily used incorrectly; doesn't always \0-terminate or check for invalid
  pointers [MS-banned] (CWE-120).
				strncpy(o, v, cpylen);			\
data/vmem-1.8/src/jemalloc/src/prof.c:768: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).
	slen = strlen(s);
data/vmem-1.8/src/jemalloc/src/prof.c:1005:12:  [1] (buffer) read:
  Check buffer boundaries if used in a loop including recursive loops
  (CWE-120, CWE-20).
			nread = read(mfd, &prof_dump_buf[prof_dump_buf_end],
data/vmem-1.8/src/jemalloc/src/tsd.c:101:35:  [1] (buffer) read:
  Check buffer boundaries if used in a loop including recursive loops
  (CWE-120, CWE-20).
#  pragma section(".CRT$XLY",long,read)
data/vmem-1.8/src/jemalloc/src/util.c:53:59:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated; if given one it may
  perform an over-read (it could cause a crash if unprotected) (CWE-126).
	UNUSED int result = syscall(SYS_write, STDERR_FILENO, s, strlen(s));
data/vmem-1.8/src/jemalloc/src/util.c:55:46:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated; if given one it may
  perform an over-read (it could cause a crash if unprotected) (CWE-126).
	UNUSED int result = write(STDERR_FILENO, s, strlen(s));
data/vmem-1.8/src/jemalloc/src/util.c:90:3:  [1] (buffer) strncpy:
  Easily used incorrectly; doesn't always \0-terminate or check for invalid
  pointers [MS-banned] (CWE-120).
		strncpy(buf, b, buflen);
data/vmem-1.8/src/jemalloc/src/util.c:554: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).
					slen = (prec < 0) ? strlen(s) : (size_t)prec;
data/vmem-1.8/src/jemalloc/test/unit/mallctl.c:11:54:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated; if given one it may
  perform an over-read (it could cause a crash if unprotected) (CWE-126).
	assert_d_eq(mallctl("version", NULL, NULL, "0.0.0", strlen("0.0.0")),
data/vmem-1.8/src/jemalloc/test/unit/mallctl.c:52:6:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated; if given one it may
  perform an over-read (it could cause a crash if unprotected) (CWE-126).
	    strlen("0.0.0")), EPERM, "mallctl() should return EPERM on "
data/vmem-1.8/src/jemalloc/test/unit/util.c:149: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_d_eq(result, strlen(expected_str_untruncated),		\
data/vmem-1.8/src/jemalloc/test/unit/util.c:179: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_d_eq(result, strlen(expected_str), "Unexpected result");	\
data/vmem-1.8/src/libvmem/vmem.c:453:16:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated; if given one it may
  perform an over-read (it could cause a crash if unprotected) (CWE-126).
	size_t size = strlen(s) + 1;
data/vmem-1.8/src/libvmem/vmem.c:470:17:  [1] (buffer) wcslen:
  Does not handle strings that are not \0-terminated; if given one it may
  perform an over-read (it could cause a crash if unprotected) (CWE-126).
	size_t size = (wcslen(s) + 1) * sizeof(wchar_t);
data/vmem-1.8/src/libvmmalloc/libvmmalloc.c:214:1:  [1] (free) memalign:
  On some systems (though not Linux-based systems) an attempt to free()
  results from memalign() may fail. This may, on a few systems, be
  exploitable. Also note that memalign() may not check that the boundary
  parameter is correct (CWE-676). Use posix_memalign instead (defined in
  POSIX's 1003.1d). Don't switch to valloc(); it is marked as obsolete in BSD
  4.3, as legacy in SUSv2, and is no longer defined in SUSv3. In some cases,
  malloc()'s alignment may be sufficient.
memalign(size_t boundary, size_t size)
data/vmem-1.8/src/libvmmalloc/libvmmalloc.c:366:32:  [1] (free) memalign:
  On some systems (though not Linux-based systems) an attempt to free()
  results from memalign() may fail. This may, on a few systems, be
  exploitable. Also note that memalign() may not check that the boundary
  parameter is correct (CWE-676). Use posix_memalign instead (defined in
  POSIX's 1003.1d). Don't switch to valloc(); it is marked as obsolete in BSD
  4.3, as legacy in SUSv2, and is no longer defined in SUSv3. In some cases,
  malloc()'s alignment may be sufficient.
	const void *caller) = (void *)memalign;
data/vmem-1.8/src/test/set_funcs/set_funcs.c:100:16:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated; if given one it may
  perform an over-read (it could cause a crash if unprotected) (CWE-126).
	size_t size = strlen(s) + 1;
data/vmem-1.8/src/test/traces_custom_function/traces_custom_function.c:76:25:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated; if given one it may
  perform an over-read (it could cause a crash if unprotected) (CWE-126).
	char *format2 = MALLOC(strlen(format) * 3);
data/vmem-1.8/src/test/unittest/ut_alloc.c:119:4:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated; if given one it may
  perform an over-read (it could cause a crash if unprotected) (CWE-126).
			strlen(str));
data/vmem-1.8/src/test/unittest/ut_backtrace.c:94:4:  [1] (buffer) strcpy:
  Does not check for buffer overflows when copying to destination [MS-banned]
  (CWE-120). Consider using snprintf, strcpy_s, or strlcpy (warning: strncpy
  easily misused). Risk is low because the source is a constant character.
			strcpy(procname, "?");
data/vmem-1.8/src/test/unittest/ut_file.c:194:19:  [1] (buffer) read:
  Check buffer boundaries if used in a loop including recursive loops
  (CWE-120, CWE-20).
	ssize_t retval = read(fd, buf, count);
data/vmem-1.8/src/test/unittest/ut_file.c:203:19:  [1] (buffer) read:
  Check buffer boundaries if used in a loop including recursive loops
  (CWE-120, CWE-20).
	ssize_t retval = read(fd, buf, (unsigned)count);
data/vmem-1.8/src/test/vmem_custom_alloc/vmem_custom_alloc.c:156: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).
	char *test = vmem_malloc(vmp, strlen(TEST_STRING_VALUE) + 1);
data/vmem-1.8/src/test/vmem_custom_alloc/vmem_custom_alloc.c:179: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).
	if (argc < 2 || argc > 3 || strlen(argv[1]) != 1)
data/vmem-1.8/src/test/vmmalloc_dummy_funcs/vmmalloc_dummy_funcs.c:49:1:  [1] (free) memalign:
  On some systems (though not Linux-based systems) an attempt to free()
  results from memalign() may fail. This may, on a few systems, be
  exploitable. Also note that memalign() may not check that the boundary
  parameter is correct (CWE-676). Use posix_memalign instead (defined in
  POSIX's 1003.1d). Don't switch to valloc(); it is marked as obsolete in BSD
  4.3, as legacy in SUSv2, and is no longer defined in SUSv3. In some cases,
  malloc()'s alignment may be sufficient.
memalign(size_t alignment, size_t size)
data/vmem-1.8/src/test/vmmalloc_dummy_funcs/vmmalloc_dummy_funcs.h:48:7:  [1] (free) memalign:
  On some systems (though not Linux-based systems) an attempt to free()
  results from memalign() may fail. This may, on a few systems, be
  exploitable. Also note that memalign() may not check that the boundary
  parameter is correct (CWE-676). Use posix_memalign instead (defined in
  POSIX's 1003.1d). Don't switch to valloc(); it is marked as obsolete in BSD
  4.3, as legacy in SUSv2, and is no longer defined in SUSv3. In some cases,
  malloc()'s alignment may be sufficient.
void *memalign(size_t boundary, size_t size);
data/vmem-1.8/src/test/vmmalloc_malloc_hooks/vmmalloc_malloc_hooks.c:83:6:  [1] (free) memalign:
  On some systems (though not Linux-based systems) an attempt to free()
  results from memalign() may fail. This may, on a few systems, be
  exploitable. Also note that memalign() may not check that the boundary
  parameter is correct (CWE-676). Use posix_memalign instead (defined in
  POSIX's 1003.1d). Don't switch to valloc(); it is marked as obsolete in BSD
  4.3, as legacy in SUSv2, and is no longer defined in SUSv3. In some cases,
  malloc()'s alignment may be sufficient.
	p = memalign(alignment, size);
data/vmem-1.8/src/test/vmmalloc_malloc_hooks/vmmalloc_malloc_hooks.c:134:8:  [1] (free) memalign:
  On some systems (though not Linux-based systems) an attempt to free()
  results from memalign() may fail. This may, on a few systems, be
  exploitable. Also note that memalign() may not check that the boundary
  parameter is correct (CWE-676). Use posix_memalign instead (defined in
  POSIX's 1003.1d). Don't switch to valloc(); it is marked as obsolete in BSD
  4.3, as legacy in SUSv2, and is no longer defined in SUSv3. In some cases,
  malloc()'s alignment may be sufficient.
	ptr = memalign(16, 4321);
data/vmem-1.8/src/test/vmmalloc_memalign/vmmalloc_memalign.c:87:12:  [1] (free) memalign:
  On some systems (though not Linux-based systems) an attempt to free()
  results from memalign() may fail. This may, on a few systems, be
  exploitable. Also note that memalign() may not check that the boundary
  parameter is correct (CWE-676). Use posix_memalign instead (defined in
  POSIX's 1003.1d). Don't switch to valloc(); it is marked as obsolete in BSD
  4.3, as legacy in SUSv2, and is no longer defined in SUSv3. In some cases,
  malloc()'s alignment may be sufficient.
		Aalloc = memalign;
data/vmem-1.8/src/windows/getopt/getopt.c:222:7:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated; if given one it may
  perform an over-read (it could cause a crash if unprotected) (CWE-126).
  if (strlen(argv[optind]) < 3 || strncmp(argv[optind], "--", 2) != 0)
data/vmem-1.8/src/windows/getopt/getopt.c:232: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).
      if (strlen(o->name) == argument_name_length) {
data/vmem-1.8/src/windows/include/platform.h:213:30:  [1] (buffer) read:
  Check buffer boundaries if used in a loop including recursive loops
  (CWE-120, CWE-20).
__pragma(section(".CRT$XCU", read)) \
data/vmem-1.8/src/windows/include/unistd.h:130:15:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated; if given one it may
  perform an over-read (it could cause a crash if unprotected) (CWE-126).
	size_t len = strlen(path);
data/vmem-1.8/utils/check_license/check-license.c:115:8:  [1] (buffer) read:
  Check buffer boundaries if used in a loop including recursive loops
  (CWE-120, CWE-20).
	ret = read(file_pattern, pattern, LICENSE_MAX_LEN);
data/vmem-1.8/utils/check_license/check-license.c:187:3:  [1] (buffer) strncpy:
  Easily used incorrectly; doesn't always \0-terminate or check for invalid
  pointers [MS-banned] (CWE-120).
		strncpy(comment_str, comment, COMMENT_STR_LEN - 1);
data/vmem-1.8/utils/check_license/check-license.c:195: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).
		comment_len = strlen(comment_str);
data/vmem-1.8/utils/check_license/check-license.c:254:42:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated; if given one it may
  perform an over-read (it could cause a crash if unprotected) (CWE-126).
	_length = (size_t)(end_str - beg_str) + strlen(LICENSE_END);
data/vmem-1.8/utils/check_license/check-license.c:281:8:  [1] (buffer) read:
  Check buffer boundaries if used in a loop including recursive loops
  (CWE-120, CWE-20).
	ret = read(file_license, buffer, LICENSE_MAX_LEN);
data/vmem-1.8/utils/check_license/check-license.c:292:2:  [1] (buffer) strncpy:
  Easily used incorrectly; doesn't always \0-terminate or check for invalid
  pointers [MS-banned] (CWE-120).
	strncpy(pattern, license, LICENSE_MAX_LEN);
data/vmem-1.8/utils/check_license/check-license.c:342:8:  [1] (buffer) read:
  Check buffer boundaries if used in a loop including recursive loops
  (CWE-120, CWE-20).
	ret = read(file_to_check, buffer, LICENSE_MAX_LEN);
data/vmem-1.8/utils/check_license/check-license.c:421:31:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated; if given one it may
  perform an over-read (it could cause a crash if unprotected) (CWE-126).
	if (memcmp(license, pattern, strlen(pattern)) != 0) {
data/vmem-1.8/utils/check_license/check-license.c:423: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).
		print_diff(license, pattern, strlen(pattern));

ANALYSIS SUMMARY:

Hits = 373
Lines analyzed = 76469 in approximately 2.30 seconds (33274 lines/second)
Physical Source Lines of Code (SLOC) = 52892
Hits@level = [0] 138 [1]  80 [2] 218 [3]  21 [4]  51 [5]   3
Hits@level+ = [0+] 511 [1+] 373 [2+] 293 [3+]  75 [4+]  54 [5+]   3
Hits/KSLOC@level+ = [0+] 9.6612 [1+] 7.05211 [2+] 5.53959 [3+] 1.41798 [4+] 1.02095 [5+] 0.0567194
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.