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/intel-processor-trace-2.0.3/include/posix/threads.h
Examining data/intel-processor-trace-2.0.3/include/pt_compiler.h
Examining data/intel-processor-trace-2.0.3/include/pt_version.h
Examining data/intel-processor-trace-2.0.3/include/windows/inttypes.h
Examining data/intel-processor-trace-2.0.3/include/windows/threads.h
Examining data/intel-processor-trace-2.0.3/libipt/internal/include/posix/pt_section_posix.h
Examining data/intel-processor-trace-2.0.3/libipt/internal/include/pt_asid.h
Examining data/intel-processor-trace-2.0.3/libipt/internal/include/pt_block_cache.h
Examining data/intel-processor-trace-2.0.3/libipt/internal/include/pt_block_decoder.h
Examining data/intel-processor-trace-2.0.3/libipt/internal/include/pt_config.h
Examining data/intel-processor-trace-2.0.3/libipt/internal/include/pt_cpu.h
Examining data/intel-processor-trace-2.0.3/libipt/internal/include/pt_cpuid.h
Examining data/intel-processor-trace-2.0.3/libipt/internal/include/pt_decoder_function.h
Examining data/intel-processor-trace-2.0.3/libipt/internal/include/pt_encoder.h
Examining data/intel-processor-trace-2.0.3/libipt/internal/include/pt_event_queue.h
Examining data/intel-processor-trace-2.0.3/libipt/internal/include/pt_ild.h
Examining data/intel-processor-trace-2.0.3/libipt/internal/include/pt_image.h
Examining data/intel-processor-trace-2.0.3/libipt/internal/include/pt_image_section_cache.h
Examining data/intel-processor-trace-2.0.3/libipt/internal/include/pt_insn.h
Examining data/intel-processor-trace-2.0.3/libipt/internal/include/pt_insn_decoder.h
Examining data/intel-processor-trace-2.0.3/libipt/internal/include/pt_last_ip.h
Examining data/intel-processor-trace-2.0.3/libipt/internal/include/pt_mapped_section.h
Examining data/intel-processor-trace-2.0.3/libipt/internal/include/pt_msec_cache.h
Examining data/intel-processor-trace-2.0.3/libipt/internal/include/pt_opcodes.h
Examining data/intel-processor-trace-2.0.3/libipt/internal/include/pt_packet.h
Examining data/intel-processor-trace-2.0.3/libipt/internal/include/pt_packet_decoder.h
Examining data/intel-processor-trace-2.0.3/libipt/internal/include/pt_query_decoder.h
Examining data/intel-processor-trace-2.0.3/libipt/internal/include/pt_retstack.h
Examining data/intel-processor-trace-2.0.3/libipt/internal/include/pt_section.h
Examining data/intel-processor-trace-2.0.3/libipt/internal/include/pt_section_file.h
Examining data/intel-processor-trace-2.0.3/libipt/internal/include/pt_sync.h
Examining data/intel-processor-trace-2.0.3/libipt/internal/include/pt_time.h
Examining data/intel-processor-trace-2.0.3/libipt/internal/include/pt_tnt_cache.h
Examining data/intel-processor-trace-2.0.3/libipt/internal/include/pti-disp-defs.h
Examining data/intel-processor-trace-2.0.3/libipt/internal/include/pti-disp.h
Examining data/intel-processor-trace-2.0.3/libipt/internal/include/pti-disp_default.h
Examining data/intel-processor-trace-2.0.3/libipt/internal/include/pti-imm-defs.h
Examining data/intel-processor-trace-2.0.3/libipt/internal/include/pti-imm.h
Examining data/intel-processor-trace-2.0.3/libipt/internal/include/pti-modrm-defs.h
Examining data/intel-processor-trace-2.0.3/libipt/internal/include/pti-modrm.h
Examining data/intel-processor-trace-2.0.3/libipt/internal/include/pti-sib.h
Examining data/intel-processor-trace-2.0.3/libipt/internal/include/windows/pt_section_windows.h
Examining data/intel-processor-trace-2.0.3/libipt/src/posix/pt_cpuid.c
Examining data/intel-processor-trace-2.0.3/libipt/src/posix/pt_section_posix.c
Examining data/intel-processor-trace-2.0.3/libipt/src/pt_asid.c
Examining data/intel-processor-trace-2.0.3/libipt/src/pt_block_cache.c
Examining data/intel-processor-trace-2.0.3/libipt/src/pt_block_decoder.c
Examining data/intel-processor-trace-2.0.3/libipt/src/pt_config.c
Examining data/intel-processor-trace-2.0.3/libipt/src/pt_cpu.c
Examining data/intel-processor-trace-2.0.3/libipt/src/pt_decoder_function.c
Examining data/intel-processor-trace-2.0.3/libipt/src/pt_encoder.c
Examining data/intel-processor-trace-2.0.3/libipt/src/pt_error.c
Examining data/intel-processor-trace-2.0.3/libipt/src/pt_event_queue.c
Examining data/intel-processor-trace-2.0.3/libipt/src/pt_ild.c
Examining data/intel-processor-trace-2.0.3/libipt/src/pt_image.c
Examining data/intel-processor-trace-2.0.3/libipt/src/pt_image_section_cache.c
Examining data/intel-processor-trace-2.0.3/libipt/src/pt_insn.c
Examining data/intel-processor-trace-2.0.3/libipt/src/pt_insn_decoder.c
Examining data/intel-processor-trace-2.0.3/libipt/src/pt_last_ip.c
Examining data/intel-processor-trace-2.0.3/libipt/src/pt_msec_cache.c
Examining data/intel-processor-trace-2.0.3/libipt/src/pt_packet.c
Examining data/intel-processor-trace-2.0.3/libipt/src/pt_packet_decoder.c
Examining data/intel-processor-trace-2.0.3/libipt/src/pt_query_decoder.c
Examining data/intel-processor-trace-2.0.3/libipt/src/pt_retstack.c
Examining data/intel-processor-trace-2.0.3/libipt/src/pt_section.c
Examining data/intel-processor-trace-2.0.3/libipt/src/pt_section_file.c
Examining data/intel-processor-trace-2.0.3/libipt/src/pt_sync.c
Examining data/intel-processor-trace-2.0.3/libipt/src/pt_time.c
Examining data/intel-processor-trace-2.0.3/libipt/src/pt_tnt_cache.c
Examining data/intel-processor-trace-2.0.3/libipt/src/pt_version.c
Examining data/intel-processor-trace-2.0.3/libipt/src/windows/pt_cpuid.c
Examining data/intel-processor-trace-2.0.3/libipt/src/windows/pt_section_windows.c
Examining data/intel-processor-trace-2.0.3/libipt/test/src/ptunit-asid.c
Examining data/intel-processor-trace-2.0.3/libipt/test/src/ptunit-block_cache.c
Examining data/intel-processor-trace-2.0.3/libipt/test/src/ptunit-config.c
Examining data/intel-processor-trace-2.0.3/libipt/test/src/ptunit-cpp.cpp
Examining data/intel-processor-trace-2.0.3/libipt/test/src/ptunit-cpu.c
Examining data/intel-processor-trace-2.0.3/libipt/test/src/ptunit-event_queue.c
Examining data/intel-processor-trace-2.0.3/libipt/test/src/ptunit-fetch.c
Examining data/intel-processor-trace-2.0.3/libipt/test/src/ptunit-ild.c
Examining data/intel-processor-trace-2.0.3/libipt/test/src/ptunit-image.c
Examining data/intel-processor-trace-2.0.3/libipt/test/src/ptunit-image_section_cache.c
Examining data/intel-processor-trace-2.0.3/libipt/test/src/ptunit-last_ip.c
Examining data/intel-processor-trace-2.0.3/libipt/test/src/ptunit-mapped_section.c
Examining data/intel-processor-trace-2.0.3/libipt/test/src/ptunit-msec_cache.c
Examining data/intel-processor-trace-2.0.3/libipt/test/src/ptunit-packet.c
Examining data/intel-processor-trace-2.0.3/libipt/test/src/ptunit-query.c
Examining data/intel-processor-trace-2.0.3/libipt/test/src/ptunit-retstack.c
Examining data/intel-processor-trace-2.0.3/libipt/test/src/ptunit-section-file.c
Examining data/intel-processor-trace-2.0.3/libipt/test/src/ptunit-section.c
Examining data/intel-processor-trace-2.0.3/libipt/test/src/ptunit-sync.c
Examining data/intel-processor-trace-2.0.3/libipt/test/src/ptunit-time.c
Examining data/intel-processor-trace-2.0.3/libipt/test/src/ptunit-tnt_cache.c
Examining data/intel-processor-trace-2.0.3/pevent/include/pevent.h
Examining data/intel-processor-trace-2.0.3/pevent/src/pevent.c
Examining data/intel-processor-trace-2.0.3/pevent/test/src/ptunit-pevent.c
Examining data/intel-processor-trace-2.0.3/ptdump/src/ptdump.c
Examining data/intel-processor-trace-2.0.3/pttc/include/errcode.h
Examining data/intel-processor-trace-2.0.3/pttc/include/file.h
Examining data/intel-processor-trace-2.0.3/pttc/include/parse.h
Examining data/intel-processor-trace-2.0.3/pttc/include/pttc.h
Examining data/intel-processor-trace-2.0.3/pttc/include/util.h
Examining data/intel-processor-trace-2.0.3/pttc/include/yasm.h
Examining data/intel-processor-trace-2.0.3/pttc/src/errcode.c
Examining data/intel-processor-trace-2.0.3/pttc/src/file.c
Examining data/intel-processor-trace-2.0.3/pttc/src/main.c
Examining data/intel-processor-trace-2.0.3/pttc/src/parse.c
Examining data/intel-processor-trace-2.0.3/pttc/src/posix/util.c
Examining data/intel-processor-trace-2.0.3/pttc/src/pttc.c
Examining data/intel-processor-trace-2.0.3/pttc/src/util.c
Examining data/intel-processor-trace-2.0.3/pttc/src/windows/util.c
Examining data/intel-processor-trace-2.0.3/pttc/src/yasm.c
Examining data/intel-processor-trace-2.0.3/ptunit/include/ptunit.h
Examining data/intel-processor-trace-2.0.3/ptunit/include/ptunit_mkfile.h
Examining data/intel-processor-trace-2.0.3/ptunit/include/ptunit_threads.h
Examining data/intel-processor-trace-2.0.3/ptunit/src/posix/ptunit_mkfile.c
Examining data/intel-processor-trace-2.0.3/ptunit/src/ptunit.c
Examining data/intel-processor-trace-2.0.3/ptunit/src/windows/ptunit_mkfile.c
Examining data/intel-processor-trace-2.0.3/ptunit/test/src/ptunit-selftest.c
Examining data/intel-processor-trace-2.0.3/ptxed/include/load_elf.h
Examining data/intel-processor-trace-2.0.3/ptxed/src/load_elf.c
Examining data/intel-processor-trace-2.0.3/ptxed/src/ptxed.c
Examining data/intel-processor-trace-2.0.3/sideband/internal/include/pt_sb_context.h
Examining data/intel-processor-trace-2.0.3/sideband/internal/include/pt_sb_decoder.h
Examining data/intel-processor-trace-2.0.3/sideband/internal/include/pt_sb_file.h
Examining data/intel-processor-trace-2.0.3/sideband/internal/include/pt_sb_pevent.h
Examining data/intel-processor-trace-2.0.3/sideband/internal/include/pt_sb_session.h
Examining data/intel-processor-trace-2.0.3/sideband/src/pt_sb_context.c
Examining data/intel-processor-trace-2.0.3/sideband/src/pt_sb_file.c
Examining data/intel-processor-trace-2.0.3/sideband/src/pt_sb_pevent.c
Examining data/intel-processor-trace-2.0.3/sideband/src/pt_sb_session.c
FINAL RESULTS:
data/intel-processor-trace-2.0.3/include/pt_version.h:57:11: [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.
return fprintf(file, "%" PRIu8 ".%" PRIu8 ".%" PRIu16,
data/intel-processor-trace-2.0.3/libipt/src/pt_image.c:51: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).
return strcpy(dup, str);
data/intel-processor-trace-2.0.3/libipt/src/pt_image_section_cache.c:50: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).
return strcpy(dup, str);
data/intel-processor-trace-2.0.3/libipt/src/pt_section.c:53: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).
return strcpy(dup, str);
data/intel-processor-trace-2.0.3/ptdump/src/ptdump.c:50:11: [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.
# define snprintf _snprintf_c
data/intel-processor-trace-2.0.3/ptdump/src/ptdump.c:522:3: [4] (format) snprintf:
If format strings can be influenced by an attacker, they can be exploited,
and note that sprintf variations do not always \0-terminate (CWE-134). Use
a constant for the format specification.
snprintf(field, sizeof(field), __VA_ARGS__); \
data/intel-processor-trace-2.0.3/pttc/src/parse.c:41:11: [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.
# define snprintf _snprintf_c
data/intel-processor-trace-2.0.3/pttc/src/parse.c:201: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(p->ptfilename, p->y->fileroot);
data/intel-processor-trace-2.0.3/pttc/src/parse.c:202: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(p->ptfilename, pt_suffix);
data/intel-processor-trace-2.0.3/pttc/src/parse.c:280: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(filename, p->y->fileroot);
data/intel-processor-trace-2.0.3/pttc/src/parse.c:283:3: [4] (buffer) strcat:
Does not check for buffer overflows when concatenating to destination
[MS-banned] (CWE-120). Consider using strcat_s, strncat, strlcat, or
snprintf (warning: strncat is easily misused).
strcat(filename, extra);
data/intel-processor-trace-2.0.3/pttc/src/parse.c:285: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(filename, cpu_suffix);
data/intel-processor-trace-2.0.3/pttc/src/parse.c:286: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(filename, exp_suffix);
data/intel-processor-trace-2.0.3/pttc/src/parse.c:465:15: [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.
status = fprintf(f, "%016" PRIx64, addr);
data/intel-processor-trace-2.0.3/pttc/src/parse.c:467:15: [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.
status = fprintf(f, "%" PRIx64, addr);
data/intel-processor-trace-2.0.3/pttc/src/parse.c:521:15: [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.
status = fprintf(f, "%02" PRIx8, byte);
data/intel-processor-trace-2.0.3/pttc/src/parse.c:528:14: [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.
status = fprintf(f, "%016" PRIx64, addr);
data/intel-processor-trace-2.0.3/pttc/src/parse.c:530:14: [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.
status = fprintf(f, "%" PRIx64, addr);
data/intel-processor-trace-2.0.3/pttc/src/parse.c:1768: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(record.comm.comm, comm);
data/intel-processor-trace-2.0.3/pttc/src/posix/util.c:53:3: [4] (shell) execvp:
This causes a new program to execute and is difficult to use safely
(CWE-78). try using a library call that implements the same functionality
if available.
execvp(file, argv);
data/intel-processor-trace-2.0.3/pttc/src/util.c:48: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).
return strcpy(dup, s);
data/intel-processor-trace-2.0.3/pttc/src/windows/util.c:89: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(args + size, argv[i]);
data/intel-processor-trace-2.0.3/pttc/src/yasm.c:42:11: [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.
# define snprintf _snprintf_c
data/intel-processor-trace-2.0.3/pttc/src/yasm.c:90:6: [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(value, "%" PRIx64, &addr) != 1)
data/intel-processor-trace-2.0.3/pttc/src/yasm.c:304:8: [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(tmp, "%" PRIx64, &addr) != 1)
data/intel-processor-trace-2.0.3/pttc/src/yasm.c:679: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(y->binfile, y->fileroot);
data/intel-processor-trace-2.0.3/pttc/src/yasm.c:680: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(y->binfile+n, bin_suffix);
data/intel-processor-trace-2.0.3/pttc/src/yasm.c:681: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(y->lstfile, y->fileroot);
data/intel-processor-trace-2.0.3/pttc/src/yasm.c:682: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(y->lstfile+n, lst_suffix);
data/intel-processor-trace-2.0.3/ptunit/src/ptunit.c:331:2: [4] (format) fprintf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
fprintf(stdout,
data/intel-processor-trace-2.0.3/ptxed/src/load_elf.c:161:4: [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(" offset=0x%" PRIx32, phdr.p_offset);
data/intel-processor-trace-2.0.3/ptxed/src/load_elf.c:162:4: [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(" size=0x%" PRIx32, phdr.p_filesz);
data/intel-processor-trace-2.0.3/ptxed/src/load_elf.c:163:4: [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(" vaddr=0x%" PRIx32, phdr.p_vaddr);
data/intel-processor-trace-2.0.3/ptxed/src/load_elf.c:284:4: [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(" offset=0x%" PRIx64, phdr.p_offset);
data/intel-processor-trace-2.0.3/ptxed/src/load_elf.c:285:4: [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(" size=0x%" PRIx64, phdr.p_filesz);
data/intel-processor-trace-2.0.3/ptxed/src/load_elf.c:286:4: [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(" vaddr=0x%" PRIx64, phdr.p_vaddr);
data/intel-processor-trace-2.0.3/ptxed/src/ptxed.c:907: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("%016" PRIx64, insn->ip);
data/intel-processor-trace-2.0.3/ptxed/src/ptxed.c:978:4: [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(", ip: %016" PRIx64, event->variant.enabled.ip);
data/intel-processor-trace-2.0.3/ptxed/src/ptxed.c:985:4: [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(", ip: %016" PRIx64, event->variant.disabled.ip);
data/intel-processor-trace-2.0.3/ptxed/src/ptxed.c:992:4: [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(", at: %016" PRIx64,
data/intel-processor-trace-2.0.3/ptxed/src/ptxed.c:996:5: [4] (format) printf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
printf(", ip: %016" PRIx64,
data/intel-processor-trace-2.0.3/ptxed/src/ptxed.c:1005:4: [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(", from: %016" PRIx64,
data/intel-processor-trace-2.0.3/ptxed/src/ptxed.c:1009:5: [4] (format) printf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
printf(", to: %016" PRIx64,
data/intel-processor-trace-2.0.3/ptxed/src/ptxed.c:1026:4: [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(", ip: %016" PRIx64,
data/intel-processor-trace-2.0.3/ptxed/src/ptxed.c:1034:4: [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(", ip: %016" PRIx64, event->variant.overflow.ip);
data/intel-processor-trace-2.0.3/ptxed/src/ptxed.c:1042:4: [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(", ip: %016" PRIx64,
data/intel-processor-trace-2.0.3/ptxed/src/ptxed.c:1055:4: [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(", ip: %016" PRIx64, event->variant.tsx.ip);
data/intel-processor-trace-2.0.3/ptxed/src/ptxed.c:1063:3: [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("vmcs, base: %016" PRIx64, event->variant.vmcs.base);
data/intel-processor-trace-2.0.3/ptxed/src/ptxed.c:1067:3: [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("vmcs, base: %016" PRIx64,
data/intel-processor-trace-2.0.3/ptxed/src/ptxed.c:1071:4: [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(", ip: %016" PRIx64,
data/intel-processor-trace-2.0.3/ptxed/src/ptxed.c:1079:4: [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(", ip: %016" PRIx64, event->variant.exstop.ip);
data/intel-processor-trace-2.0.3/ptxed/src/ptxed.c:1083:3: [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("mwait %" PRIx32 " %" PRIx32,
data/intel-processor-trace-2.0.3/ptxed/src/ptxed.c:1087:4: [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(", ip: %016" PRIx64, event->variant.mwait.ip);
data/intel-processor-trace-2.0.3/ptxed/src/ptxed.c:1116:3: [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("ptwrite: %" PRIx64, event->variant.ptwrite.payload);
data/intel-processor-trace-2.0.3/ptxed/src/ptxed.c:1119:4: [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(", ip: %016" PRIx64, event->variant.ptwrite.ip);
data/intel-processor-trace-2.0.3/ptxed/src/ptxed.c:1126:4: [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(", ip: %016" PRIx64, event->variant.tick.ip);
data/intel-processor-trace-2.0.3/ptxed/src/ptxed.c:1134:3: [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("mnt: %" PRIx64, event->variant.mnt.payload);
data/intel-processor-trace-2.0.3/ptxed/src/ptxed.c:1512:4: [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(" %" PRIx64, stats->blocks);
data/intel-processor-trace-2.0.3/ptxed/src/ptxed.c:1540:3: [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("%016" PRIx64, ip);
data/intel-processor-trace-2.0.3/sideband/src/pt_sb_pevent.c:58:11: [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.
# define snprintf _snprintf_c
data/intel-processor-trace-2.0.3/sideband/src/pt_sb_pevent.c:463:4: [4] (format) fprintf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
fprintf(stream, "\n addr: %" PRIx64, mmap->addr);
data/intel-processor-trace-2.0.3/sideband/src/pt_sb_pevent.c:464:4: [4] (format) fprintf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
fprintf(stream, "\n len: %" PRIx64, mmap->len);
data/intel-processor-trace-2.0.3/sideband/src/pt_sb_pevent.c:465:4: [4] (format) fprintf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
fprintf(stream, "\n pgoff: %" PRIx64, mmap->pgoff);
data/intel-processor-trace-2.0.3/sideband/src/pt_sb_pevent.c:479:4: [4] (format) fprintf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
fprintf(stream, "PERF_RECORD_LOST %" PRIx64 ", %"
data/intel-processor-trace-2.0.3/sideband/src/pt_sb_pevent.c:484:4: [4] (format) fprintf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
fprintf(stream, "\n id: %" PRIx64, lost->id);
data/intel-processor-trace-2.0.3/sideband/src/pt_sb_pevent.c:485:4: [4] (format) fprintf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
fprintf(stream, "\n lost: %" PRIx64, lost->lost);
data/intel-processor-trace-2.0.3/sideband/src/pt_sb_pevent.c:521:4: [4] (format) fprintf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
fprintf(stream, "PERF_RECORD_EXIT %x/%x, %x/%x, %"
data/intel-processor-trace-2.0.3/sideband/src/pt_sb_pevent.c:531:4: [4] (format) fprintf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
fprintf(stream, "\n time: %" PRIx64, exit->time);
data/intel-processor-trace-2.0.3/sideband/src/pt_sb_pevent.c:544:4: [4] (format) fprintf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
fprintf(stream, "PERF_RECORD_THROTTLE %" PRIx64 ", %"
data/intel-processor-trace-2.0.3/sideband/src/pt_sb_pevent.c:550:4: [4] (format) fprintf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
fprintf(stream, "\n time: %" PRIx64, throttle->time);
data/intel-processor-trace-2.0.3/sideband/src/pt_sb_pevent.c:551:4: [4] (format) fprintf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
fprintf(stream, "\n id: %" PRIx64, throttle->id);
data/intel-processor-trace-2.0.3/sideband/src/pt_sb_pevent.c:552:4: [4] (format) fprintf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
fprintf(stream, "\n stream_id: %" PRIx64,
data/intel-processor-trace-2.0.3/sideband/src/pt_sb_pevent.c:566:4: [4] (format) fprintf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
fprintf(stream, "PERF_RECORD_UNTHROTTLE %" PRIx64
data/intel-processor-trace-2.0.3/sideband/src/pt_sb_pevent.c:572:4: [4] (format) fprintf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
fprintf(stream, "\n time: %" PRIx64, throttle->time);
data/intel-processor-trace-2.0.3/sideband/src/pt_sb_pevent.c:573:4: [4] (format) fprintf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
fprintf(stream, "\n id: %" PRIx64, throttle->id);
data/intel-processor-trace-2.0.3/sideband/src/pt_sb_pevent.c:574:4: [4] (format) fprintf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
fprintf(stream, "\n stream_id: %" PRIx64,
data/intel-processor-trace-2.0.3/sideband/src/pt_sb_pevent.c:588:4: [4] (format) fprintf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
fprintf(stream, "PERF_RECORD_FORK %x/%x, %x/%x, %"
data/intel-processor-trace-2.0.3/sideband/src/pt_sb_pevent.c:598:4: [4] (format) fprintf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
fprintf(stream, "\n time: %" PRIx64, fork->time);
data/intel-processor-trace-2.0.3/sideband/src/pt_sb_pevent.c:623:4: [4] (format) fprintf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
fprintf(stream, "\n addr: %" PRIx64, mmap2->addr);
data/intel-processor-trace-2.0.3/sideband/src/pt_sb_pevent.c:624:4: [4] (format) fprintf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
fprintf(stream, "\n len: %" PRIx64, mmap2->len);
data/intel-processor-trace-2.0.3/sideband/src/pt_sb_pevent.c:625:4: [4] (format) fprintf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
fprintf(stream, "\n pgoff: %" PRIx64, mmap2->pgoff);
data/intel-processor-trace-2.0.3/sideband/src/pt_sb_pevent.c:628:4: [4] (format) fprintf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
fprintf(stream, "\n ino: %" PRIx64, mmap2->ino);
data/intel-processor-trace-2.0.3/sideband/src/pt_sb_pevent.c:629:4: [4] (format) fprintf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
fprintf(stream, "\n ino_generation: %" PRIx64,
data/intel-processor-trace-2.0.3/sideband/src/pt_sb_pevent.c:649:4: [4] (format) fprintf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
fprintf(stream, "PERF_RECORD_AUX%s %" PRIx64 ", %"
data/intel-processor-trace-2.0.3/sideband/src/pt_sb_pevent.c:655:4: [4] (format) fprintf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
fprintf(stream, "\n aux offset: %" PRIx64,
data/intel-processor-trace-2.0.3/sideband/src/pt_sb_pevent.c:657:4: [4] (format) fprintf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
fprintf(stream, "\n aux size: %" PRIx64,
data/intel-processor-trace-2.0.3/sideband/src/pt_sb_pevent.c:659:4: [4] (format) fprintf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
fprintf(stream, "\n flags: %" PRIx64, aux->flags);
data/intel-processor-trace-2.0.3/sideband/src/pt_sb_pevent.c:691:4: [4] (format) fprintf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
fprintf(stream, "PERF_RECORD_LOST_SAMPLES %" PRIx64,
data/intel-processor-trace-2.0.3/sideband/src/pt_sb_pevent.c:696:4: [4] (format) fprintf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
fprintf(stream, "\n lost: %" PRIx64,
data/intel-processor-trace-2.0.3/sideband/src/pt_sb_pevent.c:761:3: [4] (format) fprintf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
fprintf(stream, " %" PRIx64, *event->sample.time);
data/intel-processor-trace-2.0.3/sideband/src/pt_sb_pevent.c:764:3: [4] (format) fprintf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
fprintf(stream, " %" PRIx64, *event->sample.id);
data/intel-processor-trace-2.0.3/sideband/src/pt_sb_pevent.c:770:3: [4] (format) fprintf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
fprintf(stream, " %" PRIx64, *event->sample.stream_id);
data/intel-processor-trace-2.0.3/sideband/src/pt_sb_pevent.c:773:3: [4] (format) fprintf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
fprintf(stream, " %" PRIx64, *event->sample.identifier);
data/intel-processor-trace-2.0.3/sideband/src/pt_sb_pevent.c:792:3: [4] (format) fprintf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
fprintf(stream, "\n time: %" PRIx64, *event->sample.time);
data/intel-processor-trace-2.0.3/sideband/src/pt_sb_pevent.c:795:3: [4] (format) fprintf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
fprintf(stream, "\n id: %" PRIx64, *event->sample.id);
data/intel-processor-trace-2.0.3/sideband/src/pt_sb_pevent.c:801:3: [4] (format) fprintf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
fprintf(stream, "\n stream id: %" PRIx64,
data/intel-processor-trace-2.0.3/sideband/src/pt_sb_pevent.c:805:3: [4] (format) fprintf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
fprintf(stream, "\n identifier: %" PRIx64,
data/intel-processor-trace-2.0.3/sideband/src/pt_sb_session.c:40:11: [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.
# define snprintf _snprintf_c
data/intel-processor-trace-2.0.3/include/windows/threads.h:148:2: [3] (misc) InitializeCriticalSection:
Exceptions can be thrown in low-memory situations. Use
InitializeCriticalSectionAndSpinCount instead.
InitializeCriticalSection(&mtx->cs);
data/intel-processor-trace-2.0.3/include/windows/threads.h:164:2: [3] (misc) EnterCriticalSection:
On some versions of Windows, exceptions can be thrown in low-memory
situations. Use InitializeCriticalSectionAndSpinCount instead.
EnterCriticalSection(&mtx->cs);
data/intel-processor-trace-2.0.3/pttc/src/windows/util.c:107:9: [3] (shell) CreateProcess:
This causes a new process to execute and is difficult to use safely
(CWE-78). Specify the application path in the first argument, NOT as part
of the second, or embedded spaces could allow an attacker to force a
different program to run.
bret = CreateProcess(NULL, args,
data/intel-processor-trace-2.0.3/pttc/src/windows/util.c:107:9: [3] (shell) CreateProcess:
This causes a new process to execute and is difficult to use safely
(CWE-78). Specify the application path in the first argument, NOT as part
of the second, or embedded spaces could allow an attacker to force a
different program to run.
bret = CreateProcess(NULL, args,
data/intel-processor-trace-2.0.3/ptunit/src/posix/ptunit_mkfile.c:47:11: [3] (buffer) getenv:
Environment variables are untrustable input if they can be set by an
attacker. They can have any content and length, and the same variable can
be set more than once (CWE-807, CWE-20). Check environment variables
carefully before using them.
tmpdir = getenv("TMP");
data/intel-processor-trace-2.0.3/ptunit/src/windows/ptunit_mkfile.c:54:11: [3] (tmpfile) GetTempFileName:
Temporary file race condition in certain cases (e.g., if run as SYSTEM in
many versions of Windows) (CWE-377).
status = GetTempFileName(dirname, "ptunit-tmp-", 0, buffer);
data/intel-processor-trace-2.0.3/libipt/src/posix/pt_section_posix.c:222:7: [2] (misc) open:
Check when opening files - can an attacker redirect it (via symlinks),
force the opening of special file type (e.g., device files), move things
around to create a race condition, control its ancestors, or change its
contents? (CWE-362).
fd = open(filename, O_RDONLY);
data/intel-processor-trace-2.0.3/libipt/src/posix/pt_section_posix.c:306: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, begin, size);
data/intel-processor-trace-2.0.3/libipt/src/pt_asid.c:53: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(asid, user, size);
data/intel-processor-trace-2.0.3/libipt/src/pt_asid.c:77: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(user, asid, size);
data/intel-processor-trace-2.0.3/libipt/src/pt_block_decoder.c:514: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(ublock, block, size);
data/intel-processor-trace-2.0.3/libipt/src/pt_block_decoder.c:780: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(block->raw, insn.raw, insn.size);
data/intel-processor-trace-2.0.3/libipt/src/pt_block_decoder.c:2084: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(block->raw, insn.raw, insn.size);
data/intel-processor-trace-2.0.3/libipt/src/pt_block_decoder.c:3467: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(uevent, ev, size);
data/intel-processor-trace-2.0.3/libipt/src/pt_config.c:131: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(config, uconfig, size);
data/intel-processor-trace-2.0.3/libipt/src/pt_cpu.c: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 vendor_string[pt_cpuid_vendor_size];
data/intel-processor-trace-2.0.3/libipt/src/pt_insn_decoder.c:1207: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(uinsn, insn, size);
data/intel-processor-trace-2.0.3/libipt/src/pt_insn_decoder.c:1736: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(uevent, ev, size);
data/intel-processor-trace-2.0.3/libipt/src/pt_packet_decoder.c:231: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(upkt, pkt, size);
data/intel-processor-trace-2.0.3/libipt/src/pt_query_decoder.c:928:11: [2] (buffer) memcpy:
Does not check for buffer overflows when copying to destination (CWE-120).
Make sure destination can always hold the source data.
(void) memcpy(event, decoder->event, size);
data/intel-processor-trace-2.0.3/libipt/src/windows/pt_section_windows.c:372: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, begin, size);
data/intel-processor-trace-2.0.3/libipt/test/src/ptunit-ild.c:47: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(insn.raw, raw, size);
data/intel-processor-trace-2.0.3/libipt/test/src/ptunit-ild.c:73: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(insn.raw, raw, size);
data/intel-processor-trace-2.0.3/libipt/test/src/ptunit-ild.c:101: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(insn.raw, raw, size);
data/intel-processor-trace-2.0.3/libipt/test/src/ptunit-image.c:329: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, &mapping->content[begin], size);
data/intel-processor-trace-2.0.3/libipt/test/src/ptunit-image_section_cache.c:513: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, §ion->content[begin], (size_t) (end - begin));
data/intel-processor-trace-2.0.3/libipt/test/src/ptunit-section-file.c:66: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).
file = fopen(filename, "rb");
data/intel-processor-trace-2.0.3/libipt/test/src/ptunit-section-file.c:161: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).
file = fopen(filename, "rb");
data/intel-processor-trace-2.0.3/pevent/src/pevent.c:368: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(*stream, object, size);
data/intel-processor-trace-2.0.3/pevent/test/src/ptunit-pevent.c:391:3: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char buffer[1024];
data/intel-processor-trace-2.0.3/pevent/test/src/ptunit-pevent.c:399: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(mmap.record.filename, "foo.so");
data/intel-processor-trace-2.0.3/pevent/test/src/ptunit-pevent.c:444:3: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char buffer[1024];
data/intel-processor-trace-2.0.3/pevent/test/src/ptunit-pevent.c:449: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(comm.record.comm, "foo -b ar");
data/intel-processor-trace-2.0.3/pevent/test/src/ptunit-pevent.c:572:3: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char buffer[1024];
data/intel-processor-trace-2.0.3/pevent/test/src/ptunit-pevent.c:586: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(mmap2.record.filename, "foo.so");
data/intel-processor-trace-2.0.3/ptdump/src/ptdump.c: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 offset[17];
data/intel-processor-trace-2.0.3/ptdump/src/ptdump.c:115: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 raw[33];
data/intel-processor-trace-2.0.3/ptdump/src/ptdump.c:118: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 opcode[10];
data/intel-processor-trace-2.0.3/ptdump/src/ptdump.c:122: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 standard[25];
data/intel-processor-trace-2.0.3/ptdump/src/ptdump.c:125: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 extended[48];
data/intel-processor-trace-2.0.3/ptdump/src/ptdump.c:131:3: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char id[5];
data/intel-processor-trace-2.0.3/ptdump/src/ptdump.c:134: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 payload[17];
data/intel-processor-trace-2.0.3/ptdump/src/ptdump.c:367: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).
file = fopen(filename, "rb");
data/intel-processor-trace-2.0.3/ptdump/src/ptdump.c:606:3: [2] (buffer) sprintf:
Does not check for buffer overflows (CWE-120). Use sprintf_s, snprintf, or
vsnprintf. Risk is low because the source has a constant maximum length.
sprintf(pos, "%02x", *begin);
data/intel-processor-trace-2.0.3/pttc/src/file.c:200:6: [2] (misc) fopen:
Check when opening files - can an attacker redirect it (via symlinks),
force the opening of special file type (e.g., device files), move things
around to create a race condition, control its ancestors, or change its
contents? (CWE-362).
f = fopen(filename, "rb");
data/intel-processor-trace-2.0.3/pttc/src/parse.c: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 filename[FILENAME_MAX];
data/intel-processor-trace-2.0.3/pttc/src/parse.c:76: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 extension[256];
data/intel-processor-trace-2.0.3/pttc/src/parse.c:235: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 cpu_suffix[19];
data/intel-processor-trace-2.0.3/pttc/src/parse.c:257:10: [2] (buffer) sprintf:
Does not check for buffer overflows (CWE-120). Use sprintf_s, snprintf, or
vsnprintf. Risk is low because the source has a constant maximum length.
len = sprintf(cpu_suffix,
data/intel-processor-trace-2.0.3/pttc/src/parse.c:261:10: [2] (buffer) sprintf:
Does not check for buffer overflows (CWE-120). Use sprintf_s, snprintf, or
vsnprintf. Risk is low because the source has a constant maximum length.
len = sprintf(cpu_suffix,
data/intel-processor-trace-2.0.3/pttc/src/parse.c:316: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 s[slen];
data/intel-processor-trace-2.0.3/pttc/src/parse.c:337:6: [2] (misc) fopen:
Check when opening files - can an attacker redirect it (via symlinks),
force the opening of special file type (e.g., device files), move things
around to create a race condition, control its ancestors, or change its
contents? (CWE-362).
f = fopen(filename, "w");
data/intel-processor-trace-2.0.3/pttc/src/parse.c:362:8: [2] (misc) fopen:
Check when opening files - can an attacker redirect it (via symlinks),
force the opening of special file type (e.g., device files), move things
around to create a race condition, control its ancestors, or change its
contents? (CWE-362).
f = fopen(filename, "w");
data/intel-processor-trace-2.0.3/pttc/src/parse.c:385: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 *tmp, label[256];
data/intel-processor-trace-2.0.3/pttc/src/parse.c:573:14: [2] (misc) fopen:
Check when opening files - can an attacker redirect it (via symlinks),
force the opening of special file type (e.g., device files), move things
around to create a race condition, control its ancestors, or change its
contents? (CWE-362).
p->ptfile = fopen(p->ptfilename, "wb");
data/intel-processor-trace-2.0.3/pttc/src/parse.c:587: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[128];
data/intel-processor-trace-2.0.3/pttc/src/parse.c:707: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(start, buffer, size);
data/intel-processor-trace-2.0.3/pttc/src/parse.c:1139: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 msg[128];
data/intel-processor-trace-2.0.3/pttc/src/parse.c:1159:2: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char name[FILENAME_MAX];
data/intel-processor-trace-2.0.3/pttc/src/parse.c:1184:10: [2] (misc) fopen:
Check when opening files - can an attacker redirect it (via symlinks),
force the opening of special file type (e.g., device files), move things
around to create a race condition, control its ancestors, or change its
contents? (CWE-362).
file = fopen(name, "w");
data/intel-processor-trace-2.0.3/pttc/src/yasm.c:62: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 label[255];
data/intel-processor-trace-2.0.3/pttc/src/yasm.c:133: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 label[255];
data/intel-processor-trace-2.0.3/pttc/src/yasm.c:162: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[linelen];
data/intel-processor-trace-2.0.3/pttc/src/yasm.c:766: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 s[slen];
data/intel-processor-trace-2.0.3/pttc/src/yasm.c:767: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[max_filename_len];
data/intel-processor-trace-2.0.3/ptunit/src/posix/ptunit_mkfile.c:42:14: [2] (tmpfile) tmpfile:
Function tmpfile() has a security flaw on some systems (e.g., older System
V systems) (CWE-377).
const char *tmpfile;
data/intel-processor-trace-2.0.3/ptunit/src/posix/ptunit_mkfile.c:43: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 template[256], *filename;
data/intel-processor-trace-2.0.3/ptunit/src/posix/ptunit_mkfile.c:51:62: [2] (tmpfile) tmpfile:
Function tmpfile() has a security flaw on some systems (e.g., older System
V systems) (CWE-377).
len = snprintf(template, sizeof(template), "%s/%s", tmpdir, tmpfile);
data/intel-processor-trace-2.0.3/ptunit/src/posix/ptunit_mkfile.c:59:7: [2] (tmpfile) mkstemp:
Potential for temporary file vulnerability in some circumstances. Some
older Unix-like systems create temp files with permission to write by all
by default, so be sure to set the umask to override this. Also, some older
Unix systems might fail to use O_EXCL when opening the file, so make sure
that O_EXCL is used by the library (CWE-377).
fd = mkstemp(template);
data/intel-processor-trace-2.0.3/ptunit/src/ptunit.c:118:9: [2] (buffer) memcpy:
Does not check for buffer overflows when copying to destination (CWE-120).
Make sure destination can always hold the source data.
return memcpy(dup, str, len);
data/intel-processor-trace-2.0.3/ptunit/src/windows/ptunit_mkfile.c:39: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 dirbuffer[MAX_PATH], buffer[MAX_PATH], *filename;
data/intel-processor-trace-2.0.3/ptunit/src/windows/ptunit_mkfile.c:58: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).
file = fopen(buffer, mode);
data/intel-processor-trace-2.0.3/ptxed/src/load_elf.c:310: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).
file = fopen(name, "rb");
data/intel-processor-trace-2.0.3/ptxed/src/ptxed.c:434: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).
file = fopen(filename, "rb");
data/intel-processor-trace-2.0.3/ptxed/src/ptxed.c:852: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[256];
data/intel-processor-trace-2.0.3/ptxed/src/ptxed.c:1411: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(insn->raw, block->raw, insn->size);
data/intel-processor-trace-2.0.3/sideband/src/pt_sb_file.c:57: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).
file = fopen(filename, "rb");
data/intel-processor-trace-2.0.3/sideband/src/pt_sb_pevent.c:177: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).
file = fopen(filename, "rb");
data/intel-processor-trace-2.0.3/sideband/src/pt_sb_pevent.c:277: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(copy, src, len);
data/intel-processor-trace-2.0.3/sideband/src/pt_sb_pevent.c:1183: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[FILENAME_MAX];
data/intel-processor-trace-2.0.3/sideband/src/pt_sb_session.c:140: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 iname[16];
data/intel-processor-trace-2.0.3/sideband/src/pt_sb_session.c:393: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(event, uevent, size);
data/intel-processor-trace-2.0.3/libipt/internal/include/pt_section.h:112:8: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
int (*read)(const struct pt_section *sec, uint8_t *buffer,
data/intel-processor-trace-2.0.3/libipt/src/posix/pt_section_posix.c:271:47: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
if (!mapping || !section->unmap || !section->read || !section->memsize)
data/intel-processor-trace-2.0.3/libipt/src/pt_image.c:46:8: [1] (buffer) strlen:
Does not handle strings that are not \0-terminated; if given one it may
perform an over-read (it could cause a crash if unprotected) (CWE-126).
len = strlen(str);
data/intel-processor-trace-2.0.3/libipt/src/pt_image_section_cache.c:45:8: [1] (buffer) strlen:
Does not handle strings that are not \0-terminated; if given one it may
perform an over-read (it could cause a crash if unprotected) (CWE-126).
len = strlen(str);
data/intel-processor-trace-2.0.3/libipt/src/pt_section.c:48:8: [1] (buffer) strlen:
Does not handle strings that are not \0-terminated; if given one it may
perform an over-read (it could cause a crash if unprotected) (CWE-126).
len = strlen(str);
data/intel-processor-trace-2.0.3/libipt/src/pt_section.c:630:16: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
if (!section->read)
data/intel-processor-trace-2.0.3/libipt/src/pt_section.c:642:18: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
return section->read(section, buffer, size, offset);
data/intel-processor-trace-2.0.3/libipt/src/pt_section_file.c:183:47: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
if (!mapping || !section->unmap || !section->read || !section->memsize)
data/intel-processor-trace-2.0.3/libipt/src/pt_section_file.c:203:9: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
size_t read;
data/intel-processor-trace-2.0.3/libipt/src/pt_section_file.c:237:15: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
return (int) read;
data/intel-processor-trace-2.0.3/libipt/src/windows/pt_section_windows.c:335:47: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
if (!mapping || !section->unmap || !section->read || !section->memsize)
data/intel-processor-trace-2.0.3/libipt/test/src/ptunit-image.c:385:16: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
if (!section->read)
data/intel-processor-trace-2.0.3/libipt/test/src/ptunit-image.c:388:18: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
return section->read(section, buffer, size, offset);
data/intel-processor-trace-2.0.3/libipt/test/src/ptunit-image.c:1007:29: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
static struct ptunit_result read(struct image_fixture *ifix)
data/intel-processor-trace-2.0.3/libipt/test/src/ptunit-image.c:2236:19: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
ptu_run_f(suite, read, rfix);
data/intel-processor-trace-2.0.3/libipt/test/src/ptunit-image_section_cache.c:1160:29: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
static struct ptunit_result read(struct iscache_fixture *cfix)
data/intel-processor-trace-2.0.3/libipt/test/src/ptunit-image_section_cache.c:1999:19: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
ptu_run_f(suite, read, cfix);
data/intel-processor-trace-2.0.3/libipt/test/src/ptunit-msec_cache.c:279:29: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
static struct ptunit_result read(struct test_fixture *tfix)
data/intel-processor-trace-2.0.3/libipt/test/src/ptunit-msec_cache.c:411:19: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
ptu_run_f(suite, read, cifix);
data/intel-processor-trace-2.0.3/libipt/test/src/ptunit-section.c:711:29: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
static struct ptunit_result read(struct section_fixture *sfix)
data/intel-processor-trace-2.0.3/libipt/test/src/ptunit-section.c:984:7: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
int read;
data/intel-processor-trace-2.0.3/libipt/test/src/ptunit-section.c:995:7: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
if (read < 0)
data/intel-processor-trace-2.0.3/libipt/test/src/ptunit-section.c:999:8: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
if ((read != 2) || (buffer[0] != 0x2) || (buffer[1] != 0x4))
data/intel-processor-trace-2.0.3/libipt/test/src/ptunit-section.c:1370:19: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
ptu_run_f(suite, read, sfix);
data/intel-processor-trace-2.0.3/pevent/src/pevent.c:481: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).
slen = strlen(event->record.mmap->filename) + 1;
data/intel-processor-trace-2.0.3/pevent/src/pevent.c:515: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).
slen = strlen(event->record.comm->comm) + 1;
data/intel-processor-trace-2.0.3/pevent/src/pevent.c:577: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).
slen = strlen(event->record.mmap2->filename) + 1;
data/intel-processor-trace-2.0.3/ptdump/src/ptdump.c:356:9: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
size_t read;
data/intel-processor-trace-2.0.3/ptdump/src/ptdump.c:428:6: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
if (read != 1) {
data/intel-processor-trace-2.0.3/pttc/src/file.c:63: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).
n = strlen(t->line[0]);
data/intel-processor-trace-2.0.3/pttc/src/file.c:129:2: [1] (buffer) strncpy:
Easily used incorrectly; doesn't always \0-terminate or check for invalid
pointers [MS-banned] (CWE-120).
strncpy(dest, t->line[n], destlen);
data/intel-processor-trace-2.0.3/pttc/src/file.c:170:9: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
size_t read;
data/intel-processor-trace-2.0.3/pttc/src/file.c:241:6: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
if (read != fsize) {
data/intel-processor-trace-2.0.3/pttc/src/parse.c:65:3: [1] (buffer) strncpy:
Easily used incorrectly; doesn't always \0-terminate or check for invalid
pointers [MS-banned] (CWE-120).
strncpy(filename, sb->name, sizeof(filename) - 1);
data/intel-processor-trace-2.0.3/pttc/src/parse.c:108:3: [1] (buffer) strncpy:
Easily used incorrectly; doesn't always \0-terminate or check for invalid
pointers [MS-banned] (CWE-120).
strncpy(filename, sb->name, base_len);
data/intel-processor-trace-2.0.3/pttc/src/parse.c:195: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).
n = strlen(p->y->fileroot) + 1;
data/intel-processor-trace-2.0.3/pttc/src/parse.c:197:27: [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).
p->ptfilename = malloc(n+strlen(pt_suffix));
data/intel-processor-trace-2.0.3/pttc/src/parse.c:245: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).
n = strlen(p->y->fileroot);
data/intel-processor-trace-2.0.3/pttc/src/parse.c:249: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).
n += 1 + strlen(extra);
data/intel-processor-trace-2.0.3/pttc/src/parse.c:271: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).
n += strlen(exp_suffix);
data/intel-processor-trace-2.0.3/pttc/src/parse.c:282:3: [1] (buffer) strcat:
Does not check for buffer overflows when concatenating to destination
[MS-banned] (CWE-120). Consider using strcat_s, strncat, strlcat, or
snprintf (warning: strncat is easily misused). Risk is low because the
source is a constant character.
strcat(filename, "-");
data/intel-processor-trace-2.0.3/pttc/src/parse.c:381:18: [1] (buffer) strlen:
Does not handle strings that are not \0-terminated; if given one it may
perform an over-read (it could cause a crash if unprotected) (CWE-126).
for (i = (int) strlen(line)-1; i >= 0 && isspace(line[i]); i--)
data/intel-processor-trace-2.0.3/pttc/src/parse.c:449:4: [1] (buffer) strncpy:
Easily used incorrectly; doesn't always \0-terminate or check for invalid
pointers [MS-banned] (CWE-120).
strncpy(label, line, (size_t) i);
data/intel-processor-trace-2.0.3/pttc/src/parse.c:1592:2: [1] (buffer) strncpy:
Easily used incorrectly; doesn't always \0-terminate or check for invalid
pointers [MS-banned] (CWE-120).
strncpy(record.mmap.filename, filename,
data/intel-processor-trace-2.0.3/pttc/src/parse.c:1698:2: [1] (buffer) strncpy:
Easily used incorrectly; doesn't always \0-terminate or check for invalid
pointers [MS-banned] (CWE-120).
strncpy(record.mmap.filename, filename,
data/intel-processor-trace-2.0.3/pttc/src/parse.c:2575: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(directive) + 1;
data/intel-processor-trace-2.0.3/pttc/src/util.c:45: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).
dup = malloc(strlen(s)+1);
data/intel-processor-trace-2.0.3/pttc/src/windows/util.c:76: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).
size += strlen(argv[i]) + 3;
data/intel-processor-trace-2.0.3/pttc/src/windows/util.c:90: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).
size += strlen(argv[i]);
data/intel-processor-trace-2.0.3/pttc/src/yasm.c:184: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).
tmp += strlen("[section");
data/intel-processor-trace-2.0.3/pttc/src/yasm.c:195: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).
org = tmp + strlen("[org");
data/intel-processor-trace-2.0.3/pttc/src/yasm.c:271: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).
tmp += strlen("[section");
data/intel-processor-trace-2.0.3/pttc/src/yasm.c:384: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).
n = strlen(s);
data/intel-processor-trace-2.0.3/pttc/src/yasm.c:512:2: [1] (buffer) strncpy:
Easily used incorrectly; doesn't always \0-terminate or check for invalid
pointers [MS-banned] (CWE-120).
strncpy(pd->name, name, pd->nlen);
data/intel-processor-trace-2.0.3/pttc/src/yasm.c:515:2: [1] (buffer) strncpy:
Easily used incorrectly; doesn't always \0-terminate or check for invalid
pointers [MS-banned] (CWE-120).
strncpy(pd->payload, payload, pd->plen);
data/intel-processor-trace-2.0.3/pttc/src/yasm.c:568: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).
directive += strlen(pt_marker);
data/intel-processor-trace-2.0.3/pttc/src/yasm.c:575: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).
directive += strlen(sb_marker);
data/intel-processor-trace-2.0.3/pttc/src/yasm.c:666: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).
memmove(y->fileroot, tmp, strlen(tmp)+1);
data/intel-processor-trace-2.0.3/pttc/src/yasm.c:669: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).
y->binfile = malloc(strlen(y->fileroot)+strlen(bin_suffix)+1);
data/intel-processor-trace-2.0.3/pttc/src/yasm.c:669: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).
y->binfile = malloc(strlen(y->fileroot)+strlen(bin_suffix)+1);
data/intel-processor-trace-2.0.3/pttc/src/yasm.c:673: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).
y->lstfile = malloc(strlen(y->fileroot)+strlen(lst_suffix)+1);
data/intel-processor-trace-2.0.3/pttc/src/yasm.c:673: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).
y->lstfile = malloc(strlen(y->fileroot)+strlen(lst_suffix)+1);
data/intel-processor-trace-2.0.3/pttc/src/yasm.c:677: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).
n = strlen(y->fileroot);
data/intel-processor-trace-2.0.3/pttc/src/yasm.c:854:2: [1] (buffer) strncpy:
Easily used incorrectly; doesn't always \0-terminate or check for invalid
pointers [MS-banned] (CWE-120).
strncpy(dest, y->st_asm->line, destlen);
data/intel-processor-trace-2.0.3/ptunit/src/ptunit.c:218:21: [1] (buffer) strlen:
Does not handle strings that are not \0-terminated; if given one it may
perform an over-read (it could cause a crash if unprotected) (CWE-126).
for (base = file + strlen(file); base != file; base -= 1) {
data/intel-processor-trace-2.0.3/ptxed/src/ptxed.c:423:9: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
size_t read;
data/intel-processor-trace-2.0.3/ptxed/src/ptxed.c:495:6: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
if (read != 1) {
ANALYSIS SUMMARY:
Hits = 247
Lines analyzed = 58911 in approximately 1.45 seconds (40615 lines/second)
Physical Source Lines of Code (SLOC) = 37628
Hits@level = [0] 474 [1] 67 [2] 76 [3] 6 [4] 98 [5] 0
Hits@level+ = [0+] 721 [1+] 247 [2+] 180 [3+] 104 [4+] 98 [5+] 0
Hits/KSLOC@level+ = [0+] 19.1613 [1+] 6.56426 [2+] 4.78367 [3+] 2.7639 [4+] 2.60444 [5+] 0
Dot directories skipped = 1 (--followdotdir overrides)
Minimum risk level = 1
Not every hit is necessarily a security vulnerability.
There may be other security vulnerabilities; review your code!
See 'Secure Programming HOWTO'
(https://dwheeler.com/secure-programs) for more information.