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/capstone-4.0.2/LEB128.h
Examining data/capstone-4.0.2/MCDisassembler.h
Examining data/capstone-4.0.2/MCFixedLenDisassembler.h
Examining data/capstone-4.0.2/MCInst.c
Examining data/capstone-4.0.2/MCInst.h
Examining data/capstone-4.0.2/MCInstrDesc.c
Examining data/capstone-4.0.2/MCInstrDesc.h
Examining data/capstone-4.0.2/MCRegisterInfo.c
Examining data/capstone-4.0.2/MCRegisterInfo.h
Examining data/capstone-4.0.2/MathExtras.h
Examining data/capstone-4.0.2/SStream.c
Examining data/capstone-4.0.2/SStream.h
Examining data/capstone-4.0.2/arch/AArch64/AArch64AddressingModes.h
Examining data/capstone-4.0.2/arch/AArch64/AArch64BaseInfo.c
Examining data/capstone-4.0.2/arch/AArch64/AArch64BaseInfo.h
Examining data/capstone-4.0.2/arch/AArch64/AArch64Disassembler.c
Examining data/capstone-4.0.2/arch/AArch64/AArch64Disassembler.h
Examining data/capstone-4.0.2/arch/AArch64/AArch64InstPrinter.c
Examining data/capstone-4.0.2/arch/AArch64/AArch64InstPrinter.h
Examining data/capstone-4.0.2/arch/AArch64/AArch64Mapping.c
Examining data/capstone-4.0.2/arch/AArch64/AArch64Mapping.h
Examining data/capstone-4.0.2/arch/AArch64/AArch64Module.c
Examining data/capstone-4.0.2/arch/AArch64/AArch64Module.h
Examining data/capstone-4.0.2/arch/ARM/ARMAddressingModes.h
Examining data/capstone-4.0.2/arch/ARM/ARMBaseInfo.h
Examining data/capstone-4.0.2/arch/ARM/ARMDisassembler.c
Examining data/capstone-4.0.2/arch/ARM/ARMDisassembler.h
Examining data/capstone-4.0.2/arch/ARM/ARMInstPrinter.c
Examining data/capstone-4.0.2/arch/ARM/ARMInstPrinter.h
Examining data/capstone-4.0.2/arch/ARM/ARMMapping.c
Examining data/capstone-4.0.2/arch/ARM/ARMMapping.h
Examining data/capstone-4.0.2/arch/ARM/ARMModule.c
Examining data/capstone-4.0.2/arch/ARM/ARMModule.h
Examining data/capstone-4.0.2/arch/EVM/EVMDisassembler.c
Examining data/capstone-4.0.2/arch/EVM/EVMDisassembler.h
Examining data/capstone-4.0.2/arch/EVM/EVMInstPrinter.c
Examining data/capstone-4.0.2/arch/EVM/EVMInstPrinter.h
Examining data/capstone-4.0.2/arch/EVM/EVMMapping.c
Examining data/capstone-4.0.2/arch/EVM/EVMMapping.h
Examining data/capstone-4.0.2/arch/EVM/EVMModule.c
Examining data/capstone-4.0.2/arch/EVM/EVMModule.h
Examining data/capstone-4.0.2/arch/M680X/M680XDisassembler.c
Examining data/capstone-4.0.2/arch/M680X/M680XDisassembler.h
Examining data/capstone-4.0.2/arch/M680X/M680XDisassemblerInternals.h
Examining data/capstone-4.0.2/arch/M680X/M680XInstPrinter.c
Examining data/capstone-4.0.2/arch/M680X/M680XInstPrinter.h
Examining data/capstone-4.0.2/arch/M680X/M680XModule.c
Examining data/capstone-4.0.2/arch/M680X/M680XModule.h
Examining data/capstone-4.0.2/arch/M68K/M68KDisassembler.c
Examining data/capstone-4.0.2/arch/M68K/M68KDisassembler.h
Examining data/capstone-4.0.2/arch/M68K/M68KInstPrinter.c
Examining data/capstone-4.0.2/arch/M68K/M68KInstPrinter.h
Examining data/capstone-4.0.2/arch/M68K/M68KModule.c
Examining data/capstone-4.0.2/arch/M68K/M68KModule.h
Examining data/capstone-4.0.2/arch/Mips/MipsDisassembler.c
Examining data/capstone-4.0.2/arch/Mips/MipsDisassembler.h
Examining data/capstone-4.0.2/arch/Mips/MipsInstPrinter.c
Examining data/capstone-4.0.2/arch/Mips/MipsInstPrinter.h
Examining data/capstone-4.0.2/arch/Mips/MipsMapping.c
Examining data/capstone-4.0.2/arch/Mips/MipsMapping.h
Examining data/capstone-4.0.2/arch/Mips/MipsModule.c
Examining data/capstone-4.0.2/arch/Mips/MipsModule.h
Examining data/capstone-4.0.2/arch/PowerPC/PPCDisassembler.c
Examining data/capstone-4.0.2/arch/PowerPC/PPCDisassembler.h
Examining data/capstone-4.0.2/arch/PowerPC/PPCInstPrinter.c
Examining data/capstone-4.0.2/arch/PowerPC/PPCInstPrinter.h
Examining data/capstone-4.0.2/arch/PowerPC/PPCMapping.c
Examining data/capstone-4.0.2/arch/PowerPC/PPCMapping.h
Examining data/capstone-4.0.2/arch/PowerPC/PPCModule.c
Examining data/capstone-4.0.2/arch/PowerPC/PPCModule.h
Examining data/capstone-4.0.2/arch/PowerPC/PPCPredicates.h
Examining data/capstone-4.0.2/arch/Sparc/Sparc.h
Examining data/capstone-4.0.2/arch/Sparc/SparcDisassembler.c
Examining data/capstone-4.0.2/arch/Sparc/SparcDisassembler.h
Examining data/capstone-4.0.2/arch/Sparc/SparcInstPrinter.c
Examining data/capstone-4.0.2/arch/Sparc/SparcInstPrinter.h
Examining data/capstone-4.0.2/arch/Sparc/SparcMapping.c
Examining data/capstone-4.0.2/arch/Sparc/SparcMapping.h
Examining data/capstone-4.0.2/arch/Sparc/SparcModule.c
Examining data/capstone-4.0.2/arch/Sparc/SparcModule.h
Examining data/capstone-4.0.2/arch/SystemZ/SystemZDisassembler.c
Examining data/capstone-4.0.2/arch/SystemZ/SystemZDisassembler.h
Examining data/capstone-4.0.2/arch/SystemZ/SystemZInstPrinter.c
Examining data/capstone-4.0.2/arch/SystemZ/SystemZInstPrinter.h
Examining data/capstone-4.0.2/arch/SystemZ/SystemZMCTargetDesc.c
Examining data/capstone-4.0.2/arch/SystemZ/SystemZMCTargetDesc.h
Examining data/capstone-4.0.2/arch/SystemZ/SystemZMapping.c
Examining data/capstone-4.0.2/arch/SystemZ/SystemZMapping.h
Examining data/capstone-4.0.2/arch/SystemZ/SystemZModule.c
Examining data/capstone-4.0.2/arch/SystemZ/SystemZModule.h
Examining data/capstone-4.0.2/arch/TMS320C64x/TMS320C64xDisassembler.c
Examining data/capstone-4.0.2/arch/TMS320C64x/TMS320C64xDisassembler.h
Examining data/capstone-4.0.2/arch/TMS320C64x/TMS320C64xInstPrinter.c
Examining data/capstone-4.0.2/arch/TMS320C64x/TMS320C64xInstPrinter.h
Examining data/capstone-4.0.2/arch/TMS320C64x/TMS320C64xMapping.c
Examining data/capstone-4.0.2/arch/TMS320C64x/TMS320C64xMapping.h
Examining data/capstone-4.0.2/arch/TMS320C64x/TMS320C64xModule.c
Examining data/capstone-4.0.2/arch/TMS320C64x/TMS320C64xModule.h
Examining data/capstone-4.0.2/arch/X86/X86ATTInstPrinter.c
Examining data/capstone-4.0.2/arch/X86/X86BaseInfo.h
Examining data/capstone-4.0.2/arch/X86/X86Disassembler.c
Examining data/capstone-4.0.2/arch/X86/X86Disassembler.h
Examining data/capstone-4.0.2/arch/X86/X86DisassemblerDecoder.c
Examining data/capstone-4.0.2/arch/X86/X86DisassemblerDecoder.h
Examining data/capstone-4.0.2/arch/X86/X86DisassemblerDecoderCommon.h
Examining data/capstone-4.0.2/arch/X86/X86InstPrinter.h
Examining data/capstone-4.0.2/arch/X86/X86IntelInstPrinter.c
Examining data/capstone-4.0.2/arch/X86/X86Mapping.c
Examining data/capstone-4.0.2/arch/X86/X86Mapping.h
Examining data/capstone-4.0.2/arch/X86/X86Module.c
Examining data/capstone-4.0.2/arch/X86/X86Module.h
Examining data/capstone-4.0.2/arch/X86/qsort.h
Examining data/capstone-4.0.2/arch/XCore/XCoreDisassembler.c
Examining data/capstone-4.0.2/arch/XCore/XCoreDisassembler.h
Examining data/capstone-4.0.2/arch/XCore/XCoreInstPrinter.c
Examining data/capstone-4.0.2/arch/XCore/XCoreInstPrinter.h
Examining data/capstone-4.0.2/arch/XCore/XCoreMapping.c
Examining data/capstone-4.0.2/arch/XCore/XCoreMapping.h
Examining data/capstone-4.0.2/arch/XCore/XCoreModule.c
Examining data/capstone-4.0.2/arch/XCore/XCoreModule.h
Examining data/capstone-4.0.2/bindings/ocaml/ocaml.c
Examining data/capstone-4.0.2/bindings/vb6/vbCapstone.cpp
Examining data/capstone-4.0.2/contrib/cs_driver/cs_driver/cs_driver.c
Examining data/capstone-4.0.2/contrib/m68k_instruction_tbl_gen/M68KInstructionTblGen.c
Examining data/capstone-4.0.2/contrib/windows_kernel/libc.cpp
Examining data/capstone-4.0.2/contrib/windows_kernel/libc.h
Examining data/capstone-4.0.2/cs.c
Examining data/capstone-4.0.2/cs_priv.h
Examining data/capstone-4.0.2/cstool/cstool.c
Examining data/capstone-4.0.2/cstool/cstool_arm.c
Examining data/capstone-4.0.2/cstool/cstool_arm64.c
Examining data/capstone-4.0.2/cstool/cstool_evm.c
Examining data/capstone-4.0.2/cstool/cstool_m680x.c
Examining data/capstone-4.0.2/cstool/cstool_m68k.c
Examining data/capstone-4.0.2/cstool/cstool_mips.c
Examining data/capstone-4.0.2/cstool/cstool_ppc.c
Examining data/capstone-4.0.2/cstool/cstool_sparc.c
Examining data/capstone-4.0.2/cstool/cstool_systemz.c
Examining data/capstone-4.0.2/cstool/cstool_tms320c64x.c
Examining data/capstone-4.0.2/cstool/cstool_x86.c
Examining data/capstone-4.0.2/cstool/cstool_xcore.c
Examining data/capstone-4.0.2/cstool/getopt.h
Examining data/capstone-4.0.2/include/capstone/arm.h
Examining data/capstone-4.0.2/include/capstone/arm64.h
Examining data/capstone-4.0.2/include/capstone/capstone.h
Examining data/capstone-4.0.2/include/capstone/evm.h
Examining data/capstone-4.0.2/include/capstone/m680x.h
Examining data/capstone-4.0.2/include/capstone/m68k.h
Examining data/capstone-4.0.2/include/capstone/mips.h
Examining data/capstone-4.0.2/include/capstone/platform.h
Examining data/capstone-4.0.2/include/capstone/ppc.h
Examining data/capstone-4.0.2/include/capstone/sparc.h
Examining data/capstone-4.0.2/include/capstone/systemz.h
Examining data/capstone-4.0.2/include/capstone/tms320c64x.h
Examining data/capstone-4.0.2/include/capstone/x86.h
Examining data/capstone-4.0.2/include/capstone/xcore.h
Examining data/capstone-4.0.2/include/platform.h
Examining data/capstone-4.0.2/include/windowsce/intrin.h
Examining data/capstone-4.0.2/include/windowsce/stdint.h
Examining data/capstone-4.0.2/suite/arm/test_arm_regression.c
Examining data/capstone-4.0.2/suite/benchmark/test_iter_benchmark.c
Examining data/capstone-4.0.2/suite/capstone_get_setup.c
Examining data/capstone-4.0.2/suite/fuzz/driverbin.c
Examining data/capstone-4.0.2/suite/fuzz/drivermc.c
Examining data/capstone-4.0.2/suite/fuzz/fuzz_diff.c
Examining data/capstone-4.0.2/suite/fuzz/fuzz_disasm.c
Examining data/capstone-4.0.2/suite/fuzz/fuzz_harness.c
Examining data/capstone-4.0.2/suite/fuzz/fuzz_llvm.cpp
Examining data/capstone-4.0.2/suite/fuzz/onefile.c
Examining data/capstone-4.0.2/suite/regress/invalid_read_in_print_operand.c
Examining data/capstone-4.0.2/tests/test_arm.c
Examining data/capstone-4.0.2/tests/test_arm64.c
Examining data/capstone-4.0.2/tests/test_basic.c
Examining data/capstone-4.0.2/tests/test_customized_mnem.c
Examining data/capstone-4.0.2/tests/test_detail.c
Examining data/capstone-4.0.2/tests/test_evm.c
Examining data/capstone-4.0.2/tests/test_iter.c
Examining data/capstone-4.0.2/tests/test_m680x.c
Examining data/capstone-4.0.2/tests/test_m68k.c
Examining data/capstone-4.0.2/tests/test_mips.c
Examining data/capstone-4.0.2/tests/test_ppc.c
Examining data/capstone-4.0.2/tests/test_skipdata.c
Examining data/capstone-4.0.2/tests/test_sparc.c
Examining data/capstone-4.0.2/tests/test_systemz.c
Examining data/capstone-4.0.2/tests/test_tms320c64x.c
Examining data/capstone-4.0.2/tests/test_winkernel.cpp
Examining data/capstone-4.0.2/tests/test_x86.c
Examining data/capstone-4.0.2/tests/test_xcore.c
Examining data/capstone-4.0.2/utils.c
Examining data/capstone-4.0.2/utils.h
Examining data/capstone-4.0.2/windows/winkernel_mm.c
Examining data/capstone-4.0.2/windows/winkernel_mm.h
FINAL RESULTS:
data/capstone-4.0.2/arch/AArch64/AArch64BaseInfo.c:640:4: [4] (buffer) strcpy:
Does not check for buffer overflows when copying to destination [MS-banned]
(CWE-120). Consider using snprintf, strcpy_s, or strlcpy (warning: strncpy
easily misused).
strcpy(result, SysRegPairs[i].Name);
data/capstone-4.0.2/arch/AArch64/AArch64BaseInfo.c:650:5: [4] (buffer) strcpy:
Does not check for buffer overflows when copying to destination [MS-banned]
(CWE-120). Consider using snprintf, strcpy_s, or strlcpy (warning: strncpy
easily misused).
strcpy(result, CycloneSysRegPairs[i].Name);
data/capstone-4.0.2/arch/AArch64/AArch64BaseInfo.c:660:4: [4] (buffer) strcpy:
Does not check for buffer overflows when copying to destination [MS-banned]
(CWE-120). Consider using snprintf, strcpy_s, or strlcpy (warning: strncpy
easily misused).
strcpy(result, S->InstPairs[i].Name);
data/capstone-4.0.2/arch/AArch64/AArch64InstPrinter.c:71:11: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
uint8_t access;
data/capstone-4.0.2/arch/AArch64/AArch64InstPrinter.c:73:89: [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.
MI->flat_insn->detail->arm64.operands[MI->flat_insn->detail->arm64.op_count].access = access;
data/capstone-4.0.2/arch/AArch64/AArch64InstPrinter.c:140:14: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
uint8_t access;
data/capstone-4.0.2/arch/AArch64/AArch64InstPrinter.c:142:92: [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.
MI->flat_insn->detail->arm64.operands[MI->flat_insn->detail->arm64.op_count].access = access;
data/capstone-4.0.2/arch/AArch64/AArch64InstPrinter.c:150:92: [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.
MI->flat_insn->detail->arm64.operands[MI->flat_insn->detail->arm64.op_count].access = access;
data/capstone-4.0.2/arch/AArch64/AArch64InstPrinter.c:205:14: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
uint8_t access;
data/capstone-4.0.2/arch/AArch64/AArch64InstPrinter.c:207:92: [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.
MI->flat_insn->detail->arm64.operands[MI->flat_insn->detail->arm64.op_count].access = access;
data/capstone-4.0.2/arch/AArch64/AArch64InstPrinter.c:215:92: [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.
MI->flat_insn->detail->arm64.operands[MI->flat_insn->detail->arm64.op_count].access = access;
data/capstone-4.0.2/arch/AArch64/AArch64InstPrinter.c:223:92: [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.
MI->flat_insn->detail->arm64.operands[MI->flat_insn->detail->arm64.op_count].access = access;
data/capstone-4.0.2/arch/AArch64/AArch64InstPrinter.c:248:13: [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.
uint8_t access;
data/capstone-4.0.2/arch/AArch64/AArch64InstPrinter.c:250:91: [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.
MI->flat_insn->detail->arm64.operands[MI->flat_insn->detail->arm64.op_count].access = access;
data/capstone-4.0.2/arch/AArch64/AArch64InstPrinter.c:258:91: [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.
MI->flat_insn->detail->arm64.operands[MI->flat_insn->detail->arm64.op_count].access = access;
data/capstone-4.0.2/arch/AArch64/AArch64InstPrinter.c:266:91: [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.
MI->flat_insn->detail->arm64.operands[MI->flat_insn->detail->arm64.op_count].access = access;
data/capstone-4.0.2/arch/AArch64/AArch64InstPrinter.c:274:91: [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.
MI->flat_insn->detail->arm64.operands[MI->flat_insn->detail->arm64.op_count].access = access;
data/capstone-4.0.2/arch/AArch64/AArch64InstPrinter.c:297:12: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
uint8_t access;
data/capstone-4.0.2/arch/AArch64/AArch64InstPrinter.c:299:90: [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.
MI->flat_insn->detail->arm64.operands[MI->flat_insn->detail->arm64.op_count].access = access;
data/capstone-4.0.2/arch/AArch64/AArch64InstPrinter.c:307:90: [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.
MI->flat_insn->detail->arm64.operands[MI->flat_insn->detail->arm64.op_count].access = access;
data/capstone-4.0.2/arch/AArch64/AArch64InstPrinter.c:315:90: [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.
MI->flat_insn->detail->arm64.operands[MI->flat_insn->detail->arm64.op_count].access = access;
data/capstone-4.0.2/arch/AArch64/AArch64InstPrinter.c:323:90: [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.
MI->flat_insn->detail->arm64.operands[MI->flat_insn->detail->arm64.op_count].access = access;
data/capstone-4.0.2/arch/AArch64/AArch64InstPrinter.c:356:13: [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.
uint8_t access;
data/capstone-4.0.2/arch/AArch64/AArch64InstPrinter.c:358:91: [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.
MI->flat_insn->detail->arm64.operands[MI->flat_insn->detail->arm64.op_count].access = access;
data/capstone-4.0.2/arch/AArch64/AArch64InstPrinter.c:366:91: [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.
MI->flat_insn->detail->arm64.operands[MI->flat_insn->detail->arm64.op_count].access = access;
data/capstone-4.0.2/arch/AArch64/AArch64InstPrinter.c:374:91: [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.
MI->flat_insn->detail->arm64.operands[MI->flat_insn->detail->arm64.op_count].access = access;
data/capstone-4.0.2/arch/AArch64/AArch64InstPrinter.c:382:91: [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.
MI->flat_insn->detail->arm64.operands[MI->flat_insn->detail->arm64.op_count].access = access;
data/capstone-4.0.2/arch/AArch64/AArch64InstPrinter.c:406:12: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
uint8_t access;
data/capstone-4.0.2/arch/AArch64/AArch64InstPrinter.c:408:90: [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.
MI->flat_insn->detail->arm64.operands[MI->flat_insn->detail->arm64.op_count].access = access;
data/capstone-4.0.2/arch/AArch64/AArch64InstPrinter.c:416:90: [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.
MI->flat_insn->detail->arm64.operands[MI->flat_insn->detail->arm64.op_count].access = access;
data/capstone-4.0.2/arch/AArch64/AArch64InstPrinter.c:424:90: [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.
MI->flat_insn->detail->arm64.operands[MI->flat_insn->detail->arm64.op_count].access = access;
data/capstone-4.0.2/arch/AArch64/AArch64InstPrinter.c:432:90: [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.
MI->flat_insn->detail->arm64.operands[MI->flat_insn->detail->arm64.op_count].access = access;
data/capstone-4.0.2/arch/AArch64/AArch64InstPrinter.c:710:12: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
uint8_t access;
data/capstone-4.0.2/arch/AArch64/AArch64InstPrinter.c:712:90: [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.
MI->flat_insn->detail->arm64.operands[MI->flat_insn->detail->arm64.op_count].access = access;
data/capstone-4.0.2/arch/AArch64/AArch64InstPrinter.c:725:13: [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.
uint8_t access;
data/capstone-4.0.2/arch/AArch64/AArch64InstPrinter.c:727:91: [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.
MI->flat_insn->detail->arm64.operands[MI->flat_insn->detail->arm64.op_count].access = access;
data/capstone-4.0.2/arch/AArch64/AArch64InstPrinter.c:757:13: [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.
uint8_t access;
data/capstone-4.0.2/arch/AArch64/AArch64InstPrinter.c:759:91: [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.
MI->flat_insn->detail->arm64.operands[MI->flat_insn->detail->arm64.op_count].access = access;
data/capstone-4.0.2/arch/AArch64/AArch64InstPrinter.c:788:13: [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.
uint8_t access;
data/capstone-4.0.2/arch/AArch64/AArch64InstPrinter.c:790:91: [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.
MI->flat_insn->detail->arm64.operands[MI->flat_insn->detail->arm64.op_count].access = access;
data/capstone-4.0.2/arch/AArch64/AArch64InstPrinter.c:807:11: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
uint8_t access;
data/capstone-4.0.2/arch/AArch64/AArch64InstPrinter.c:809:89: [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.
MI->flat_insn->detail->arm64.operands[MI->flat_insn->detail->arm64.op_count].access = access;
data/capstone-4.0.2/arch/AArch64/AArch64InstPrinter.c:829:13: [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.
uint8_t access;
data/capstone-4.0.2/arch/AArch64/AArch64InstPrinter.c:831:91: [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.
MI->flat_insn->detail->arm64.operands[MI->flat_insn->detail->arm64.op_count].access = access;
data/capstone-4.0.2/arch/AArch64/AArch64InstPrinter.c:842:13: [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.
uint8_t access;
data/capstone-4.0.2/arch/AArch64/AArch64InstPrinter.c:844:91: [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.
MI->flat_insn->detail->arm64.operands[MI->flat_insn->detail->arm64.op_count].access = access;
data/capstone-4.0.2/arch/AArch64/AArch64InstPrinter.c:869:11: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
uint8_t access;
data/capstone-4.0.2/arch/AArch64/AArch64InstPrinter.c:871:89: [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.
MI->flat_insn->detail->arm64.operands[MI->flat_insn->detail->arm64.op_count].access = access;
data/capstone-4.0.2/arch/AArch64/AArch64InstPrinter.c:887:11: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
uint8_t access;
data/capstone-4.0.2/arch/AArch64/AArch64InstPrinter.c:889:89: [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.
MI->flat_insn->detail->arm64.operands[MI->flat_insn->detail->arm64.op_count].access = access;
data/capstone-4.0.2/arch/AArch64/AArch64InstPrinter.c:910:12: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
uint8_t access;
data/capstone-4.0.2/arch/AArch64/AArch64InstPrinter.c:912:90: [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.
MI->flat_insn->detail->arm64.operands[MI->flat_insn->detail->arm64.op_count].access = access;
data/capstone-4.0.2/arch/AArch64/AArch64InstPrinter.c:934:11: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
uint8_t access;
data/capstone-4.0.2/arch/AArch64/AArch64InstPrinter.c:936:89: [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.
MI->flat_insn->detail->arm64.operands[MI->flat_insn->detail->arm64.op_count].access = access;
data/capstone-4.0.2/arch/AArch64/AArch64InstPrinter.c:968:11: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
uint8_t access;
data/capstone-4.0.2/arch/AArch64/AArch64InstPrinter.c:970:89: [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.
MI->flat_insn->detail->arm64.operands[MI->flat_insn->detail->arm64.op_count].access = access;
data/capstone-4.0.2/arch/AArch64/AArch64InstPrinter.c:1021:11: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
uint8_t access;
data/capstone-4.0.2/arch/AArch64/AArch64InstPrinter.c:1023:89: [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.
MI->flat_insn->detail->arm64.operands[MI->flat_insn->detail->arm64.op_count].access = access;
data/capstone-4.0.2/arch/AArch64/AArch64InstPrinter.c:1113:11: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
uint8_t access;
data/capstone-4.0.2/arch/AArch64/AArch64InstPrinter.c:1115:89: [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.
MI->flat_insn->detail->arm64.operands[MI->flat_insn->detail->arm64.op_count].access = access;
data/capstone-4.0.2/arch/AArch64/AArch64InstPrinter.c:1213:12: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
uint8_t access;
data/capstone-4.0.2/arch/AArch64/AArch64InstPrinter.c:1215:90: [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.
MI->flat_insn->detail->arm64.operands[MI->flat_insn->detail->arm64.op_count].access = access;
data/capstone-4.0.2/arch/AArch64/AArch64InstPrinter.c:1237:13: [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.
uint8_t access;
data/capstone-4.0.2/arch/AArch64/AArch64InstPrinter.c:1239:91: [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.
MI->flat_insn->detail->arm64.operands[MI->flat_insn->detail->arm64.op_count].access = access;
data/capstone-4.0.2/arch/AArch64/AArch64InstPrinter.c:1273:12: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
uint8_t access;
data/capstone-4.0.2/arch/AArch64/AArch64InstPrinter.c:1275:90: [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.
MI->flat_insn->detail->arm64.operands[MI->flat_insn->detail->arm64.op_count].access = access;
data/capstone-4.0.2/arch/AArch64/AArch64InstPrinter.c:1299:11: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
uint8_t access;
data/capstone-4.0.2/arch/AArch64/AArch64InstPrinter.c:1301:89: [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.
MI->flat_insn->detail->arm64.operands[MI->flat_insn->detail->arm64.op_count].access = access;
data/capstone-4.0.2/arch/AArch64/AArch64InstPrinter.c:1396:12: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
uint8_t access;
data/capstone-4.0.2/arch/AArch64/AArch64InstPrinter.c:1398:90: [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.
MI->flat_insn->detail->arm64.operands[MI->flat_insn->detail->arm64.op_count].access = access;
data/capstone-4.0.2/arch/AArch64/AArch64InstPrinter.c:1518:12: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
uint8_t access;
data/capstone-4.0.2/arch/AArch64/AArch64InstPrinter.c:1520:90: [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.
MI->flat_insn->detail->arm64.operands[MI->flat_insn->detail->arm64.op_count].access = access;
data/capstone-4.0.2/arch/AArch64/AArch64InstPrinter.c:1543:12: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
uint8_t access;
data/capstone-4.0.2/arch/AArch64/AArch64InstPrinter.c:1545:90: [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.
MI->flat_insn->detail->arm64.operands[MI->flat_insn->detail->arm64.op_count].access = access;
data/capstone-4.0.2/arch/AArch64/AArch64InstPrinter.c:1572:12: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
uint8_t access;
data/capstone-4.0.2/arch/AArch64/AArch64InstPrinter.c:1574:90: [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.
MI->flat_insn->detail->arm64.operands[MI->flat_insn->detail->arm64.op_count].access = access;
data/capstone-4.0.2/arch/AArch64/AArch64InstPrinter.c:1585:12: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
uint8_t access;
data/capstone-4.0.2/arch/AArch64/AArch64InstPrinter.c:1587:90: [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.
MI->flat_insn->detail->arm64.operands[MI->flat_insn->detail->arm64.op_count].access = access;
data/capstone-4.0.2/arch/AArch64/AArch64InstPrinter.c:1607:11: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
uint8_t access;
data/capstone-4.0.2/arch/AArch64/AArch64InstPrinter.c:1609:89: [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.
MI->flat_insn->detail->arm64.operands[MI->flat_insn->detail->arm64.op_count].access = access;
data/capstone-4.0.2/arch/AArch64/AArch64InstPrinter.c:1628:11: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
uint8_t access;
data/capstone-4.0.2/arch/AArch64/AArch64InstPrinter.c:1630:89: [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.
MI->flat_insn->detail->arm64.operands[MI->flat_insn->detail->arm64.op_count].access = access;
data/capstone-4.0.2/arch/AArch64/AArch64InstPrinter.c:1650:12: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
uint8_t access;
data/capstone-4.0.2/arch/AArch64/AArch64InstPrinter.c:1652:90: [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.
MI->flat_insn->detail->arm64.operands[MI->flat_insn->detail->arm64.op_count].access = access;
data/capstone-4.0.2/arch/AArch64/AArch64InstPrinter.c:1661:17: [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.
unsigned char access;
data/capstone-4.0.2/arch/AArch64/AArch64InstPrinter.c:1666:89: [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.
MI->flat_insn->detail->arm64.operands[MI->flat_insn->detail->arm64.op_count].access = access;
data/capstone-4.0.2/arch/AArch64/AArch64InstPrinter.c:1682:17: [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.
unsigned char access;
data/capstone-4.0.2/arch/AArch64/AArch64InstPrinter.c:1684:89: [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.
MI->flat_insn->detail->arm64.operands[MI->flat_insn->detail->arm64.op_count].access = access;
data/capstone-4.0.2/arch/AArch64/AArch64Mapping.c:1003:10: [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.
uint8_t access[5];
data/capstone-4.0.2/arch/AArch64/AArch64Mapping.c:1020:22: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
return insn_ops[i].access;
data/capstone-4.0.2/arch/AArch64/AArch64Mapping.c:1046:14: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
if ((op->access & CS_AC_READ) && !arr_exist(regs_read, read_count, op->reg)) {
data/capstone-4.0.2/arch/AArch64/AArch64Mapping.c:1050:14: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
if ((op->access & CS_AC_WRITE) && !arr_exist(regs_write, write_count, op->reg)) {
data/capstone-4.0.2/arch/ARM/ARMInstPrinter.c:146:11: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
uint8_t access;
data/capstone-4.0.2/arch/ARM/ARMInstPrinter.c:157:85: [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.
MI->flat_insn->detail->arm.operands[MI->flat_insn->detail->arm.op_count].access = access;
data/capstone-4.0.2/arch/ARM/ARMInstPrinter.c:636:17: [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.
uint8_t access;
data/capstone-4.0.2/arch/ARM/ARMInstPrinter.c:642:91: [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.
MI->flat_insn->detail->arm.operands[MI->flat_insn->detail->arm.op_count].access = access;
data/capstone-4.0.2/arch/ARM/ARMInstPrinter.c:835:13: [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.
uint8_t access;
data/capstone-4.0.2/arch/ARM/ARMInstPrinter.c:842:87: [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.
MI->flat_insn->detail->arm.operands[MI->flat_insn->detail->arm.op_count].access = access;
data/capstone-4.0.2/arch/ARM/ARMInstPrinter.c:1517:86: [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.
MI->flat_insn->detail->arm.operands[MI->flat_insn->detail->arm.op_count].access = access;
data/capstone-4.0.2/arch/ARM/ARMInstPrinter.c:2441:11: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
uint8_t access;
data/capstone-4.0.2/arch/ARM/ARMInstPrinter.c:2449:85: [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.
MI->flat_insn->detail->arm.operands[MI->flat_insn->detail->arm.op_count].access = access;
data/capstone-4.0.2/arch/ARM/ARMInstPrinter.c:2464:10: [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.
uint8_t access;
data/capstone-4.0.2/arch/ARM/ARMInstPrinter.c:2480:85: [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.
MI->flat_insn->detail->arm.operands[MI->flat_insn->detail->arm.op_count].access = access;
data/capstone-4.0.2/arch/ARM/ARMInstPrinter.c:2490:85: [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.
MI->flat_insn->detail->arm.operands[MI->flat_insn->detail->arm.op_count].access = access;
data/capstone-4.0.2/arch/ARM/ARMInstPrinter.c:2505:10: [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.
uint8_t access;
data/capstone-4.0.2/arch/ARM/ARMInstPrinter.c:2521:85: [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.
MI->flat_insn->detail->arm.operands[MI->flat_insn->detail->arm.op_count].access = access;
data/capstone-4.0.2/arch/ARM/ARMInstPrinter.c:2531:85: [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.
MI->flat_insn->detail->arm.operands[MI->flat_insn->detail->arm.op_count].access = access;
data/capstone-4.0.2/arch/ARM/ARMInstPrinter.c:2545:10: [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.
uint8_t access;
data/capstone-4.0.2/arch/ARM/ARMInstPrinter.c:2559:85: [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.
MI->flat_insn->detail->arm.operands[MI->flat_insn->detail->arm.op_count].access = access;
data/capstone-4.0.2/arch/ARM/ARMInstPrinter.c:2569:85: [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.
MI->flat_insn->detail->arm.operands[MI->flat_insn->detail->arm.op_count].access = access;
data/capstone-4.0.2/arch/ARM/ARMInstPrinter.c:2579:85: [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.
MI->flat_insn->detail->arm.operands[MI->flat_insn->detail->arm.op_count].access = access;
data/capstone-4.0.2/arch/ARM/ARMInstPrinter.c:2593:10: [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.
uint8_t access;
data/capstone-4.0.2/arch/ARM/ARMInstPrinter.c:2607:85: [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.
MI->flat_insn->detail->arm.operands[MI->flat_insn->detail->arm.op_count].access = access;
data/capstone-4.0.2/arch/ARM/ARMInstPrinter.c:2617:85: [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.
MI->flat_insn->detail->arm.operands[MI->flat_insn->detail->arm.op_count].access = access;
data/capstone-4.0.2/arch/ARM/ARMInstPrinter.c:2627:85: [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.
MI->flat_insn->detail->arm.operands[MI->flat_insn->detail->arm.op_count].access = access;
data/capstone-4.0.2/arch/ARM/ARMInstPrinter.c:2637:85: [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.
MI->flat_insn->detail->arm.operands[MI->flat_insn->detail->arm.op_count].access = access;
data/capstone-4.0.2/arch/ARM/ARMInstPrinter.c:2651:10: [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.
uint8_t access;
data/capstone-4.0.2/arch/ARM/ARMInstPrinter.c:2662:85: [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.
MI->flat_insn->detail->arm.operands[MI->flat_insn->detail->arm.op_count].access = access;
data/capstone-4.0.2/arch/ARM/ARMInstPrinter.c:2677:10: [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.
uint8_t access;
data/capstone-4.0.2/arch/ARM/ARMInstPrinter.c:2693:85: [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.
MI->flat_insn->detail->arm.operands[MI->flat_insn->detail->arm.op_count].access = access;
data/capstone-4.0.2/arch/ARM/ARMInstPrinter.c:2703:85: [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.
MI->flat_insn->detail->arm.operands[MI->flat_insn->detail->arm.op_count].access = access;
data/capstone-4.0.2/arch/ARM/ARMInstPrinter.c:2717:10: [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.
uint8_t access;
data/capstone-4.0.2/arch/ARM/ARMInstPrinter.c:2731:85: [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.
MI->flat_insn->detail->arm.operands[MI->flat_insn->detail->arm.op_count].access = access;
data/capstone-4.0.2/arch/ARM/ARMInstPrinter.c:2741:85: [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.
MI->flat_insn->detail->arm.operands[MI->flat_insn->detail->arm.op_count].access = access;
data/capstone-4.0.2/arch/ARM/ARMInstPrinter.c:2751:85: [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.
MI->flat_insn->detail->arm.operands[MI->flat_insn->detail->arm.op_count].access = access;
data/capstone-4.0.2/arch/ARM/ARMInstPrinter.c:2765:10: [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.
uint8_t access;
data/capstone-4.0.2/arch/ARM/ARMInstPrinter.c:2779:85: [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.
MI->flat_insn->detail->arm.operands[MI->flat_insn->detail->arm.op_count].access = access;
data/capstone-4.0.2/arch/ARM/ARMInstPrinter.c:2789:85: [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.
MI->flat_insn->detail->arm.operands[MI->flat_insn->detail->arm.op_count].access = access;
data/capstone-4.0.2/arch/ARM/ARMInstPrinter.c:2799:85: [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.
MI->flat_insn->detail->arm.operands[MI->flat_insn->detail->arm.op_count].access = access;
data/capstone-4.0.2/arch/ARM/ARMInstPrinter.c:2809:85: [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.
MI->flat_insn->detail->arm.operands[MI->flat_insn->detail->arm.op_count].access = access;
data/capstone-4.0.2/arch/ARM/ARMInstPrinter.c:2824:10: [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.
uint8_t access;
data/capstone-4.0.2/arch/ARM/ARMInstPrinter.c:2840:85: [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.
MI->flat_insn->detail->arm.operands[MI->flat_insn->detail->arm.op_count].access = access;
data/capstone-4.0.2/arch/ARM/ARMInstPrinter.c:2850:85: [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.
MI->flat_insn->detail->arm.operands[MI->flat_insn->detail->arm.op_count].access = access;
data/capstone-4.0.2/arch/ARM/ARMInstPrinter.c:2865:10: [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.
uint8_t access;
data/capstone-4.0.2/arch/ARM/ARMInstPrinter.c:2879:85: [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.
MI->flat_insn->detail->arm.operands[MI->flat_insn->detail->arm.op_count].access = access;
data/capstone-4.0.2/arch/ARM/ARMInstPrinter.c:2889:85: [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.
MI->flat_insn->detail->arm.operands[MI->flat_insn->detail->arm.op_count].access = access;
data/capstone-4.0.2/arch/ARM/ARMInstPrinter.c:2899:85: [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.
MI->flat_insn->detail->arm.operands[MI->flat_insn->detail->arm.op_count].access = access;
data/capstone-4.0.2/arch/ARM/ARMInstPrinter.c:2914:10: [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.
uint8_t access;
data/capstone-4.0.2/arch/ARM/ARMInstPrinter.c:2928:85: [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.
MI->flat_insn->detail->arm.operands[MI->flat_insn->detail->arm.op_count].access = access;
data/capstone-4.0.2/arch/ARM/ARMInstPrinter.c:2938:85: [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.
MI->flat_insn->detail->arm.operands[MI->flat_insn->detail->arm.op_count].access = access;
data/capstone-4.0.2/arch/ARM/ARMInstPrinter.c:2948:85: [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.
MI->flat_insn->detail->arm.operands[MI->flat_insn->detail->arm.op_count].access = access;
data/capstone-4.0.2/arch/ARM/ARMInstPrinter.c:2958:85: [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.
MI->flat_insn->detail->arm.operands[MI->flat_insn->detail->arm.op_count].access = access;
data/capstone-4.0.2/arch/ARM/ARMInstPrinter.c:2972:10: [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.
uint8_t access;
data/capstone-4.0.2/arch/ARM/ARMInstPrinter.c:2986:85: [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.
MI->flat_insn->detail->arm.operands[MI->flat_insn->detail->arm.op_count].access = access;
data/capstone-4.0.2/arch/ARM/ARMInstPrinter.c:2996:85: [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.
MI->flat_insn->detail->arm.operands[MI->flat_insn->detail->arm.op_count].access = access;
data/capstone-4.0.2/arch/ARM/ARMInstPrinter.c:3006:85: [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.
MI->flat_insn->detail->arm.operands[MI->flat_insn->detail->arm.op_count].access = access;
data/capstone-4.0.2/arch/ARM/ARMInstPrinter.c:3020:10: [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.
uint8_t access;
data/capstone-4.0.2/arch/ARM/ARMInstPrinter.c:3034:85: [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.
MI->flat_insn->detail->arm.operands[MI->flat_insn->detail->arm.op_count].access = access;
data/capstone-4.0.2/arch/ARM/ARMInstPrinter.c:3044:85: [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.
MI->flat_insn->detail->arm.operands[MI->flat_insn->detail->arm.op_count].access = access;
data/capstone-4.0.2/arch/ARM/ARMInstPrinter.c:3054:85: [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.
MI->flat_insn->detail->arm.operands[MI->flat_insn->detail->arm.op_count].access = access;
data/capstone-4.0.2/arch/ARM/ARMInstPrinter.c:3064:85: [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.
MI->flat_insn->detail->arm.operands[MI->flat_insn->detail->arm.op_count].access = access;
data/capstone-4.0.2/arch/ARM/ARMMapping.c:876:10: [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.
uint8_t access[7];
data/capstone-4.0.2/arch/ARM/ARMMapping.c:893:22: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
return insn_ops[i].access;
data/capstone-4.0.2/arch/ARM/ARMMapping.c:919:14: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
if ((op->access & CS_AC_READ) && !arr_exist(regs_read, read_count, op->reg)) {
data/capstone-4.0.2/arch/ARM/ARMMapping.c:923:14: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
if ((op->access & CS_AC_WRITE) && !arr_exist(regs_write, write_count, op->reg)) {
data/capstone-4.0.2/arch/M680X/M680XDisassembler.c:305:68: [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.
static void add_reg_to_rw_list(MCInst *MI, m680x_reg reg, e_access access)
data/capstone-4.0.2/arch/M680X/M680XDisassembler.c:312:10: [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.
switch (access) {
data/capstone-4.0.2/arch/M680X/M680XDisassembler.c:344:11: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
e_access access)
data/capstone-4.0.2/arch/M680X/M680XDisassembler.c:351:35: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
add_reg_to_rw_list(MI, op->reg, access);
data/capstone-4.0.2/arch/M680X/M680XDisassembler.c:418:53: [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.
update_am_reg_list(MI, info, &m680x->operands[i], access);
data/capstone-4.0.2/arch/M680X/M680XDisassembler.c:434:12: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
e_access access;
data/capstone-4.0.2/arch/M680X/M680XDisassembler.c:442:31: [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.
m680x->operands[i].access = access;
data/capstone-4.0.2/arch/M680X/M680XDisassembler.c:594:14: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
e_access access;
data/capstone-4.0.2/arch/M680X/M680XDisassembler.c:607:33: [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.
add_reg_to_rw_list(MI, reg, access);
data/capstone-4.0.2/arch/M68K/M68KInstPrinter.c:99:4: [4] (buffer) sprintf:
Does not check for buffer overflows (CWE-120). Use sprintf_s, snprintf, or
vsnprintf.
sprintf(buffer + strlen(buffer), "%s%d", prefix, first);
data/capstone-4.0.2/arch/M68K/M68KInstPrinter.c:101:5: [4] (buffer) sprintf:
Does not check for buffer overflows (CWE-120). Use sprintf_s, snprintf, or
vsnprintf.
sprintf(buffer + strlen(buffer), "-%s%d", prefix, first + run_length);
data/capstone-4.0.2/arch/TMS320C64x/TMS320C64xInstPrinter.c:117: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(insn_asm, ss.buffer);
data/capstone-4.0.2/arch/X86/X86ATTInstPrinter.c:374:67: [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.
static void get_op_access(cs_struct *h, unsigned int id, uint8_t *access, uint64_t *eflags)
data/capstone-4.0.2/arch/X86/X86ATTInstPrinter.c:380:3: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
access[0] = 0;
data/capstone-4.0.2/arch/X86/X86ATTInstPrinter.c:394: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[i] = arr[count - i];
data/capstone-4.0.2/arch/X86/X86ATTInstPrinter.c:396: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[i] = 0;
data/capstone-4.0.2/arch/X86/X86ATTInstPrinter.c:406:11: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
uint8_t access[6];
data/capstone-4.0.2/arch/X86/X86ATTInstPrinter.c:416:48: [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.
get_op_access(MI->csh, MCInst_getOpcode(MI), access, &MI->flat_insn->detail->x86.eflags);
data/capstone-4.0.2/arch/X86/X86ATTInstPrinter.c:417:85: [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.
MI->flat_insn->detail->x86.operands[MI->flat_insn->detail->x86.op_count].access = access[MI->flat_insn->detail->x86.op_count];
data/capstone-4.0.2/arch/X86/X86ATTInstPrinter.c:445:11: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
uint8_t access[6];
data/capstone-4.0.2/arch/X86/X86ATTInstPrinter.c:455:48: [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.
get_op_access(MI->csh, MCInst_getOpcode(MI), access, &MI->flat_insn->detail->x86.eflags);
data/capstone-4.0.2/arch/X86/X86ATTInstPrinter.c:456:85: [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.
MI->flat_insn->detail->x86.operands[MI->flat_insn->detail->x86.op_count].access = access[MI->flat_insn->detail->x86.op_count];
data/capstone-4.0.2/arch/X86/X86ATTInstPrinter.c:531:11: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
uint8_t access[6];
data/capstone-4.0.2/arch/X86/X86ATTInstPrinter.c:541:48: [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.
get_op_access(MI->csh, MCInst_getOpcode(MI), access, &MI->flat_insn->detail->x86.eflags);
data/capstone-4.0.2/arch/X86/X86ATTInstPrinter.c:542:85: [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.
MI->flat_insn->detail->x86.operands[MI->flat_insn->detail->x86.op_count].access = access[MI->flat_insn->detail->x86.op_count];
data/capstone-4.0.2/arch/X86/X86ATTInstPrinter.c:671:13: [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.
uint8_t access[6];
data/capstone-4.0.2/arch/X86/X86ATTInstPrinter.c:677:50: [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.
get_op_access(MI->csh, MCInst_getOpcode(MI), access, &MI->flat_insn->detail->x86.eflags);
data/capstone-4.0.2/arch/X86/X86ATTInstPrinter.c:678:87: [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.
MI->flat_insn->detail->x86.operands[MI->flat_insn->detail->x86.op_count].access = access[MI->flat_insn->detail->x86.op_count];
data/capstone-4.0.2/arch/X86/X86ATTInstPrinter.c:814:11: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
uint8_t access[6];
data/capstone-4.0.2/arch/X86/X86ATTInstPrinter.c:824:48: [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.
get_op_access(MI->csh, MCInst_getOpcode(MI), access, &MI->flat_insn->detail->x86.eflags);
data/capstone-4.0.2/arch/X86/X86ATTInstPrinter.c:825:85: [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.
MI->flat_insn->detail->x86.operands[MI->flat_insn->detail->x86.op_count].access = access[MI->flat_insn->detail->x86.op_count];
data/capstone-4.0.2/arch/X86/X86ATTInstPrinter.c:980:11: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
uint8_t access[6] = {0};
data/capstone-4.0.2/arch/X86/X86ATTInstPrinter.c:1092:48: [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.
get_op_access(MI->csh, MCInst_getOpcode(MI), access, &MI->flat_insn->detail->x86.eflags);
data/capstone-4.0.2/arch/X86/X86ATTInstPrinter.c:1093:51: [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.
MI->flat_insn->detail->x86.operands[0].access = access[0];
data/capstone-4.0.2/arch/X86/X86ATTInstPrinter.c:1094:51: [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.
MI->flat_insn->detail->x86.operands[1].access = access[1];
data/capstone-4.0.2/arch/X86/X86IntelInstPrinter.c:493:67: [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.
static void get_op_access(cs_struct *h, unsigned int id, uint8_t *access, uint64_t *eflags)
data/capstone-4.0.2/arch/X86/X86IntelInstPrinter.c:500:3: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
access[0] = 0;
data/capstone-4.0.2/arch/X86/X86IntelInstPrinter.c:507: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[i] = arr[i];
data/capstone-4.0.2/arch/X86/X86IntelInstPrinter.c:509: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[i] = 0;
data/capstone-4.0.2/arch/X86/X86IntelInstPrinter.c:513:2: [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[i] = 0;
data/capstone-4.0.2/arch/X86/X86IntelInstPrinter.c:525:11: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
uint8_t access[6];
data/capstone-4.0.2/arch/X86/X86IntelInstPrinter.c:537:48: [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.
get_op_access(MI->csh, MCInst_getOpcode(MI), access, &MI->flat_insn->detail->x86.eflags);
data/capstone-4.0.2/arch/X86/X86IntelInstPrinter.c:538:85: [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.
MI->flat_insn->detail->x86.operands[MI->flat_insn->detail->x86.op_count].access = access[MI->flat_insn->detail->x86.op_count];
data/capstone-4.0.2/arch/X86/X86IntelInstPrinter.c:565:11: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
uint8_t access[6];
data/capstone-4.0.2/arch/X86/X86IntelInstPrinter.c:577:48: [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.
get_op_access(MI->csh, MCInst_getOpcode(MI), access, &MI->flat_insn->detail->x86.eflags);
data/capstone-4.0.2/arch/X86/X86IntelInstPrinter.c:578:85: [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.
MI->flat_insn->detail->x86.operands[MI->flat_insn->detail->x86.op_count].access = access[MI->flat_insn->detail->x86.op_count];
data/capstone-4.0.2/arch/X86/X86IntelInstPrinter.c:661:11: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
uint8_t access[6];
data/capstone-4.0.2/arch/X86/X86IntelInstPrinter.c:673:48: [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.
get_op_access(MI->csh, MCInst_getOpcode(MI), access, &MI->flat_insn->detail->x86.eflags);
data/capstone-4.0.2/arch/X86/X86IntelInstPrinter.c:674:85: [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.
MI->flat_insn->detail->x86.operands[MI->flat_insn->detail->x86.op_count].access = access[MI->flat_insn->detail->x86.op_count];
data/capstone-4.0.2/arch/X86/X86IntelInstPrinter.c:719:11: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
uint8_t access[6];
data/capstone-4.0.2/arch/X86/X86IntelInstPrinter.c:727:48: [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.
get_op_access(MI->csh, MCInst_getOpcode(MI), access, &MI->flat_insn->detail->x86.eflags);
data/capstone-4.0.2/arch/X86/X86IntelInstPrinter.c:728:85: [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.
MI->flat_insn->detail->x86.operands[MI->flat_insn->detail->x86.op_count].access = access[MI->flat_insn->detail->x86.op_count];
data/capstone-4.0.2/arch/X86/X86IntelInstPrinter.c:795:11: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
uint8_t access[6] = {0};
data/capstone-4.0.2/arch/X86/X86IntelInstPrinter.c:824:48: [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.
get_op_access(MI->csh, MCInst_getOpcode(MI), access, &MI->flat_insn->detail->x86.eflags);
data/capstone-4.0.2/arch/X86/X86IntelInstPrinter.c:825:51: [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.
MI->flat_insn->detail->x86.operands[0].access = access[0];
data/capstone-4.0.2/arch/X86/X86IntelInstPrinter.c:826:51: [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.
MI->flat_insn->detail->x86.operands[1].access = access[1];
data/capstone-4.0.2/arch/X86/X86IntelInstPrinter.c:865:12: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
uint8_t access[6];
data/capstone-4.0.2/arch/X86/X86IntelInstPrinter.c:879:49: [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.
get_op_access(MI->csh, MCInst_getOpcode(MI), access, &MI->flat_insn->detail->x86.eflags);
data/capstone-4.0.2/arch/X86/X86IntelInstPrinter.c:880:86: [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.
MI->flat_insn->detail->x86.operands[MI->flat_insn->detail->x86.op_count].access = access[MI->flat_insn->detail->x86.op_count];
data/capstone-4.0.2/arch/X86/X86IntelInstPrinter.c:904:13: [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.
uint8_t access[6];
data/capstone-4.0.2/arch/X86/X86IntelInstPrinter.c:912:50: [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.
get_op_access(MI->csh, MCInst_getOpcode(MI), access, &MI->flat_insn->detail->x86.eflags);
data/capstone-4.0.2/arch/X86/X86IntelInstPrinter.c:913:87: [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.
MI->flat_insn->detail->x86.operands[MI->flat_insn->detail->x86.op_count].access = access[MI->flat_insn->detail->x86.op_count];
data/capstone-4.0.2/arch/X86/X86IntelInstPrinter.c:988:13: [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.
uint8_t access[6];
data/capstone-4.0.2/arch/X86/X86IntelInstPrinter.c:1006:50: [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.
get_op_access(MI->csh, MCInst_getOpcode(MI), access, &MI->flat_insn->detail->x86.eflags);
data/capstone-4.0.2/arch/X86/X86IntelInstPrinter.c:1007:87: [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.
MI->flat_insn->detail->x86.operands[MI->flat_insn->detail->x86.op_count].access = access[MI->flat_insn->detail->x86.op_count];
data/capstone-4.0.2/arch/X86/X86IntelInstPrinter.c:1028:11: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
uint8_t access[6];
data/capstone-4.0.2/arch/X86/X86IntelInstPrinter.c:1040:48: [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.
get_op_access(MI->csh, MCInst_getOpcode(MI), access, &MI->flat_insn->detail->x86.eflags);
data/capstone-4.0.2/arch/X86/X86IntelInstPrinter.c:1041:85: [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.
MI->flat_insn->detail->x86.operands[MI->flat_insn->detail->x86.op_count].access = access[MI->flat_insn->detail->x86.op_count];
data/capstone-4.0.2/arch/X86/X86Mapping.c:2689:18: [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.
enum cs_ac_type access;
data/capstone-4.0.2/arch/X86/X86Mapping.c:2982:62: [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.
x86_reg X86_insn_reg_intel(unsigned int id, enum cs_ac_type *access)
data/capstone-4.0.2/arch/X86/X86Mapping.c:3008:8: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
if (access) {
data/capstone-4.0.2/arch/X86/X86Mapping.c:3009:43: [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 = insn_regs_intel_sorted[mid].access;
data/capstone-4.0.2/arch/X86/X86Mapping.c:3065:60: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
x86_reg X86_insn_reg_att(unsigned int id, enum cs_ac_type *access)
data/capstone-4.0.2/arch/X86/X86Mapping.c:3071:8: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
if (access)
data/capstone-4.0.2/arch/X86/X86Mapping.c:3072:32: [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 = insn_regs_att[i].access;
data/capstone-4.0.2/arch/X86/X86Mapping.c:3513:10: [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.
uint8_t access[6];
data/capstone-4.0.2/arch/X86/X86Mapping.c:3535:22: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
return insn_ops[i].access;
data/capstone-4.0.2/arch/X86/X86Mapping.c:3561:14: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
if ((op->access & CS_AC_READ) && !arr_exist(regs_read, read_count, op->reg)) {
data/capstone-4.0.2/arch/X86/X86Mapping.c:3565:14: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
if ((op->access & CS_AC_WRITE) && !arr_exist(regs_write, write_count, op->reg)) {
data/capstone-4.0.2/arch/X86/X86Mapping.h:34:62: [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.
x86_reg X86_insn_reg_intel(unsigned int id, enum cs_ac_type *access);
data/capstone-4.0.2/arch/X86/X86Mapping.h:35:60: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
x86_reg X86_insn_reg_att(unsigned int id, enum cs_ac_type *access);
data/capstone-4.0.2/arch/XCore/XCoreInstPrinter.c:54: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(tmp, code); // safe because code is way shorter than 128 bytes
data/capstone-4.0.2/bindings/ocaml/ocaml.c:171:72: [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.
Store_field(tmp2, 4, Val_int(insn[j-1].detail->arm.operands[i].access));
data/capstone-4.0.2/bindings/ocaml/ocaml.c:398:72: [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.
Store_field(tmp2, 2, Val_int(insn[j-1].detail->x86.operands[i].access));
data/capstone-4.0.2/bindings/ocaml/ocaml.c:669:74: [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.
Store_field(tmp2, 2, Val_int(insn[j-1].detail->m680x.operands[i].access));
data/capstone-4.0.2/contrib/cs_driver/cs_driver/cs_driver.c:93:36: [4] (format) printf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
_Use_decl_annotations_ int __cdecl printf(const char * const _Format, ...) {
data/capstone-4.0.2/contrib/windows_kernel/libc.cpp:135:9: [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.
__cdecl vsnprintf(
data/capstone-4.0.2/contrib/windows_kernel/libc.h:39:13: [4] (format) vsnprintf:
If format strings can be influenced by an attacker, they can be exploited,
and note that sprintf variations do not always \0-terminate (CWE-134). Use
a constant for the format specification.
int __cdecl vsnprintf(char *buffer, size_t count,
data/capstone-4.0.2/cs.c:319:31: [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.
cs_vsnprintf_t cs_vsnprintf = vsnprintf;
data/capstone-4.0.2/cs.c:344:31: [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.
cs_vsnprintf_t cs_vsnprintf = vsnprintf;
data/capstone-4.0.2/cs.c:660:23: [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.
cs_vsnprintf = mem->vsnprintf;
data/capstone-4.0.2/cstool/cstool_arm.c:77:14: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
switch(op->access) {
data/capstone-4.0.2/cstool/cstool_arm64.c:17:10: [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.
uint8_t access;
data/capstone-4.0.2/cstool/cstool_arm64.c:79:16: [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 = op->access;
data/capstone-4.0.2/cstool/cstool_arm64.c:80:10: [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.
switch(access) {
data/capstone-4.0.2/cstool/cstool_m680x.c:149:11: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
if (op->access != CS_AC_INVALID)
data/capstone-4.0.2/cstool/cstool_m680x.c:150:46: [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.
printf("\t\t\taccess: %s\n", s_access[op->access]);
data/capstone-4.0.2/cstool/cstool_x86.c:287:14: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
switch(op->access) {
data/capstone-4.0.2/include/capstone/arm.h:417:10: [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.
uint8_t access;
data/capstone-4.0.2/include/capstone/arm64.h:654:10: [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.
uint8_t access;
data/capstone-4.0.2/include/capstone/capstone.h:153:17: [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.
cs_vsnprintf_t vsnprintf;
data/capstone-4.0.2/include/capstone/m680x.h:129:10: [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.
uint8_t access;
data/capstone-4.0.2/include/capstone/x86.h:289:11: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
uint8_t access;
data/capstone-4.0.2/suite/arm/test_arm_regression.c:7:9: [4] (format) snprintf:
If format strings can be influenced by an attacker, they can be exploited,
and note that sprintf variations do not always \0-terminate (CWE-134). Use
a constant for the format specification.
#define snprintf _snprintf
data/capstone-4.0.2/suite/arm/test_arm_regression.c:7:18: [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
data/capstone-4.0.2/suite/arm/test_arm_regression.c:54:10: [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.
used = snprintf(buf + *cur, *left, __VA_ARGS__); \
data/capstone-4.0.2/suite/arm/test_arm_regression.c:315: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.
used = snprintf(tmp_buf + cur, left, __VA_ARGS__); \
data/capstone-4.0.2/tests/test_arm.c:102:14: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
switch(op->access) {
data/capstone-4.0.2/tests/test_arm64.c:38:16: [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.
unsigned char access;
data/capstone-4.0.2/tests/test_arm64.c:100:16: [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 = op->access;
data/capstone-4.0.2/tests/test_arm64.c:101:10: [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.
switch(access) {
data/capstone-4.0.2/tests/test_m680x.c:175:11: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
if (op->access != CS_AC_INVALID)
data/capstone-4.0.2/tests/test_m680x.c:176:46: [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.
printf("\t\t\taccess: %s\n", s_access[op->access]);
data/capstone-4.0.2/tests/test_winkernel.cpp:163:13: [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.
int __cdecl printf(const char * const format, ...)
data/capstone-4.0.2/tests/test_x86.c:310:14: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
switch(op->access) {
data/capstone-4.0.2/cstool/cstool.c:314:14: [3] (buffer) getopt:
Some older implementations do not protect against internal buffer overflows
(CWE-120, CWE-20). Check implementation on installation, or limit the size
of all string inputs.
while ((c = getopt (argc, argv, "sudhv")) != -1) {
data/capstone-4.0.2/cstool/getopt.h:20:1: [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.
getopt (int nargc, char * const nargv[], const char *ostr)
data/capstone-4.0.2/MCInst.h:109: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 assembly[8]; // for special instruction, so that we dont need printer
data/capstone-4.0.2/MCInst.h:110: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 evm_data[32]; // for EVM PUSH operand
data/capstone-4.0.2/SStream.c:36: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(ss->buffer + ss->index, s, len);
data/capstone-4.0.2/SStream.h:10: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[512];
data/capstone-4.0.2/arch/AArch64/AArch64BaseInfo.c:83: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[22];
data/capstone-4.0.2/arch/AArch64/AArch64InstPrinter.c:1414: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[32];
data/capstone-4.0.2/arch/AArch64/AArch64InstPrinter.c:1600: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[128];
data/capstone-4.0.2/arch/AArch64/AArch64InstPrinter.c:1621: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[128];
data/capstone-4.0.2/arch/AArch64/AArch64Mapping.c:319: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(insn->detail->regs_read, insns[i].regs_use, sizeof(insns[i].regs_use));
data/capstone-4.0.2/arch/AArch64/AArch64Mapping.c:322: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(insn->detail->regs_write, insns[i].regs_mod, sizeof(insns[i].regs_mod));
data/capstone-4.0.2/arch/AArch64/AArch64Mapping.c:325: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(insn->detail->groups, insns[i].groups, sizeof(insns[i].groups));
data/capstone-4.0.2/arch/AArch64/AArch64Mapping.c:1038: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(regs_read, insn->detail->regs_read, read_count * sizeof(insn->detail->regs_read[0]));
data/capstone-4.0.2/arch/AArch64/AArch64Mapping.c:1039: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(regs_write, insn->detail->regs_write, write_count * sizeof(insn->detail->regs_write[0]));
data/capstone-4.0.2/arch/ARM/ARMMapping.c:293: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(insn->detail->regs_read, insns[i].regs_use, sizeof(insns[i].regs_use));
data/capstone-4.0.2/arch/ARM/ARMMapping.c:296: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(insn->detail->regs_write, insns[i].regs_mod, sizeof(insns[i].regs_mod));
data/capstone-4.0.2/arch/ARM/ARMMapping.c:299: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(insn->detail->groups, insns[i].groups, sizeof(insns[i].groups));
data/capstone-4.0.2/arch/ARM/ARMMapping.c:911: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(regs_read, insn->detail->regs_read, read_count * sizeof(insn->detail->regs_read[0]));
data/capstone-4.0.2/arch/ARM/ARMMapping.c:912: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(regs_write, insn->detail->regs_write, write_count * sizeof(insn->detail->regs_write[0]));
data/capstone-4.0.2/arch/EVM/EVMDisassembler.c:296: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(MI->evm_data, code + 1, len);
data/capstone-4.0.2/arch/EVM/EVMMapping.c:40: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(&insn->detail->evm, &insns[id], sizeof(insns[id]));
data/capstone-4.0.2/arch/M680X/M680XDisassembler.c:2299:3: [2] (buffer) memcpy:
Does not check for buffer overflows when copying to destination (CWE-120).
Make sure destination can always hold the source data.
memcpy(regs_read, insn->detail->regs_read,
data/capstone-4.0.2/arch/M680X/M680XDisassembler.c:2301:3: [2] (buffer) memcpy:
Does not check for buffer overflows when copying to destination (CWE-120).
Make sure destination can always hold the source data.
memcpy(regs_write, insn->detail->regs_write,
data/capstone-4.0.2/arch/M680X/M680XInstPrinter.c:147: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.
prePostfix = (char *)s_inc_dec[op->idx.inc_dec + 2];
data/capstone-4.0.2/arch/M680X/M680XInstPrinter.c:269: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(&detail->m680x, m680x, sizeof(cs_m680x));
data/capstone-4.0.2/arch/M68K/M68KInstPrinter.c:108: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/capstone-4.0.2/arch/M68K/M68KInstPrinter.c:276: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(&detail->m68k, ext, sizeof(cs_m68k));
data/capstone-4.0.2/arch/M68K/M68KInstPrinter.c:278: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(&detail->regs_read, &info->regs_read, regs_read_count * sizeof(uint16_t));
data/capstone-4.0.2/arch/M68K/M68KInstPrinter.c:281: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(&detail->regs_write, &info->regs_write, regs_write_count * sizeof(uint16_t));
data/capstone-4.0.2/arch/M68K/M68KInstPrinter.c:284: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(&detail->groups, &info->groups, groups_count);
data/capstone-4.0.2/arch/Mips/MipsMapping.c:236: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(insn->detail->regs_read, insns[i].regs_use, sizeof(insns[i].regs_use));
data/capstone-4.0.2/arch/Mips/MipsMapping.c:239: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(insn->detail->regs_write, insns[i].regs_mod, sizeof(insns[i].regs_mod));
data/capstone-4.0.2/arch/Mips/MipsMapping.c:242: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(insn->detail->groups, insns[i].groups, sizeof(insns[i].groups));
data/capstone-4.0.2/arch/PowerPC/PPCMapping.c:272: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(insn->detail->regs_read, insns[i].regs_use, sizeof(insns[i].regs_use));
data/capstone-4.0.2/arch/PowerPC/PPCMapping.c:275: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(insn->detail->regs_write, insns[i].regs_mod, sizeof(insns[i].regs_mod));
data/capstone-4.0.2/arch/PowerPC/PPCMapping.c:278: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(insn->detail->groups, insns[i].groups, sizeof(insns[i].groups));
data/capstone-4.0.2/arch/Sparc/SparcInstPrinter.c:356:2: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char instr[64]; // Sparc has no instruction this long
data/capstone-4.0.2/arch/Sparc/SparcMapping.c:171: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(insn->detail->regs_read, insns[i].regs_use, sizeof(insns[i].regs_use));
data/capstone-4.0.2/arch/Sparc/SparcMapping.c:174: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(insn->detail->regs_write, insns[i].regs_mod, sizeof(insns[i].regs_mod));
data/capstone-4.0.2/arch/Sparc/SparcMapping.c:177: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(insn->detail->groups, insns[i].groups, sizeof(insns[i].groups));
data/capstone-4.0.2/arch/SystemZ/SystemZMapping.c:92: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(insn->detail->regs_read, insns[i].regs_use, sizeof(insns[i].regs_use));
data/capstone-4.0.2/arch/SystemZ/SystemZMapping.c:95: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(insn->detail->regs_write, insns[i].regs_mod, sizeof(insns[i].regs_mod));
data/capstone-4.0.2/arch/SystemZ/SystemZMapping.c:98: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(insn->detail->groups, insns[i].groups, sizeof(insns[i].groups));
data/capstone-4.0.2/arch/TMS320C64x/TMS320C64xInstPrinter.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 *p, *p2, tmp[8];
data/capstone-4.0.2/arch/TMS320C64x/TMS320C64xInstPrinter.c:83:5: [2] (buffer) strcpy:
Does not check for buffer overflows when copying to destination [MS-banned]
(CWE-120). Consider using snprintf, strcpy_s, or strlcpy (warning: strncpy
easily misused). Risk is low because the source is a constant string.
strcpy(insn_asm, "Invalid!");
data/capstone-4.0.2/arch/TMS320C64x/TMS320C64xInstPrinter.c:87:5: [2] (buffer) strcpy:
Does not check for buffer overflows when copying to destination [MS-banned]
(CWE-120). Consider using snprintf, strcpy_s, or strlcpy (warning: strncpy
easily misused). Risk is low because the source is a constant string.
strcpy(tmp, "1T");
data/capstone-4.0.2/arch/TMS320C64x/TMS320C64xInstPrinter.c:89:5: [2] (buffer) strcpy:
Does not check for buffer overflows when copying to destination [MS-banned]
(CWE-120). Consider using snprintf, strcpy_s, or strlcpy (warning: strncpy
easily misused). Risk is low because the source is a constant string.
strcpy(tmp, "2T");
data/capstone-4.0.2/arch/TMS320C64x/TMS320C64xMapping.c:1702: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(insn->detail->regs_read, insns[i].regs_use, sizeof(insns[i].regs_use));
data/capstone-4.0.2/arch/TMS320C64x/TMS320C64xMapping.c:1705: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(insn->detail->regs_write, insns[i].regs_mod, sizeof(insns[i].regs_mod));
data/capstone-4.0.2/arch/TMS320C64x/TMS320C64xMapping.c:1708: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(insn->detail->groups, insns[i].groups, sizeof(insns[i].groups));
data/capstone-4.0.2/arch/X86/X86Mapping.c:2500: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(insn->detail->regs_read, insns[i].regs_use, sizeof(insns[i].regs_use));
data/capstone-4.0.2/arch/X86/X86Mapping.c:2506:6: [2] (buffer) memcpy:
Does not check for buffer overflows when copying to destination (CWE-120).
Make sure destination can always hold the source data.
memcpy(insn->detail->regs_write, insns[i].regs_mod, sizeof(insns[i].regs_mod));
data/capstone-4.0.2/arch/X86/X86Mapping.c:2511:7: [2] (buffer) memcpy:
Does not check for buffer overflows when copying to destination (CWE-120).
Make sure destination can always hold the source data.
memcpy(insn->detail->regs_write, insns[i].regs_mod, sizeof(insns[i].regs_mod));
data/capstone-4.0.2/arch/X86/X86Mapping.c:2521:7: [2] (buffer) memcpy:
Does not check for buffer overflows when copying to destination (CWE-120).
Make sure destination can always hold the source data.
memcpy(insn->detail->regs_write, insns[i].regs_mod, sizeof(insns[i].regs_mod));
data/capstone-4.0.2/arch/X86/X86Mapping.c:2654: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(insn->detail->groups, insns[i].groups, sizeof(insns[i].groups));
data/capstone-4.0.2/arch/X86/X86Mapping.c:3419: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(MI->flat_insn->detail->x86.prefix, MI->x86_prefix, ARR_SIZE(MI->x86_prefix));
data/capstone-4.0.2/arch/X86/X86Mapping.c:3553: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(regs_read, insn->detail->regs_read, read_count * sizeof(insn->detail->regs_read[0]));
data/capstone-4.0.2/arch/X86/X86Mapping.c:3554: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(regs_write, insn->detail->regs_write, write_count * sizeof(insn->detail->regs_write[0]));
data/capstone-4.0.2/arch/XCore/XCoreInstPrinter.c:52:2: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char tmp[128];
data/capstone-4.0.2/arch/XCore/XCoreInstPrinter.c:114:98: [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).
MI->flat_insn->detail->xcore.operands[MI->flat_insn->detail->xcore.op_count].mem.disp = atoi(p2);
data/capstone-4.0.2/arch/XCore/XCoreMapping.c:97: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(insn->detail->regs_read, insns[i].regs_use, sizeof(insns[i].regs_use));
data/capstone-4.0.2/arch/XCore/XCoreMapping.c:100:4: [2] (buffer) memcpy:
Does not check for buffer overflows when copying to destination (CWE-120).
Make sure destination can always hold the source data.
memcpy(insn->detail->regs_write, insns[i].regs_mod, sizeof(insns[i].regs_mod));
data/capstone-4.0.2/arch/XCore/XCoreMapping.c:103: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(insn->detail->groups, insns[i].groups, sizeof(insns[i].groups));
data/capstone-4.0.2/bindings/vb6/vbCapstone.cpp:62: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(curInst, (void*)&insn[index], bufSize); //size lets us get a partial version of whatever we have implemented in the vbstruct...
data/capstone-4.0.2/contrib/windows_kernel/libc.cpp:24: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[0];
data/capstone-4.0.2/contrib/windows_kernel/libc.cpp:96: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(mem, inblock.get(), min(CONTAINING_RECORD(inblock.get(), MEMBLOCK, data)->size, size));
data/capstone-4.0.2/cs.c:546: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->bytes, code + insn->size - copy_size, copy_size);
data/capstone-4.0.2/cs.c:922: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(insn_cache->bytes, buffer, skipdata_bytes);
data/capstone-4.0.2/cs.c:1136: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->bytes, *code, skipdata_bytes);
data/capstone-4.0.2/cs_priv.h:37: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 ITStates[8];
data/capstone-4.0.2/cs_priv.h: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 mnemonic[CS_MNEMONIC_SIZE];
data/capstone-4.0.2/include/capstone/capstone.h:336: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 mnemonic[CS_MNEMONIC_SIZE];
data/capstone-4.0.2/include/capstone/capstone.h:340: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 op_str[160];
data/capstone-4.0.2/suite/arm/test_arm_regression.c:136: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 a_buf[2048];
data/capstone-4.0.2/suite/arm/test_arm_regression.c:323: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_buf[2048];
data/capstone-4.0.2/suite/fuzz/driverbin.c:44: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).
fp = fopen(dir->d_name, "rb");
data/capstone-4.0.2/suite/fuzz/drivermc.c:15:5: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char line[MAX_LINE_SIZE];
data/capstone-4.0.2/suite/fuzz/drivermc.c:17: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 arch[MAX_LINE_SIZE];
data/capstone-4.0.2/suite/fuzz/drivermc.c:18:5: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char mode[MAX_LINE_SIZE];
data/capstone-4.0.2/suite/fuzz/drivermc.c:27: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).
fp = fopen(argv[i], "rb");
data/capstone-4.0.2/suite/fuzz/fuzz_diff.c:187: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 LLVMAssemblyText[80];
data/capstone-4.0.2/suite/fuzz/fuzz_diff.c:188: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 CapstoneAssemblyText[80];
data/capstone-4.0.2/suite/fuzz/fuzz_diff.c:199:19: [2] (misc) fopen:
Check when opening files - can an attacker redirect it (via symlinks),
force the opening of special file type (e.g., device files), move things
around to create a race condition, control its ancestors, or change its
contents? (CWE-362).
outfile = fopen("/dev/null", "w");
data/capstone-4.0.2/suite/fuzz/fuzz_disasm.c:236:19: [2] (misc) fopen:
Check when opening files - can an attacker redirect it (via symlinks),
force the opening of special file type (e.g., device files), move things
around to create a race condition, control its ancestors, or change its
contents? (CWE-362).
outfile = fopen("/dev/null", "w");
data/capstone-4.0.2/suite/fuzz/fuzz_harness.c:125: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).
FILE *fp = fopen(argv[1], "r");
data/capstone-4.0.2/suite/fuzz/onefile.c:17:10: [2] (misc) fopen:
Check when opening files - can an attacker redirect it (via symlinks),
force the opening of special file type (e.g., device files), move things
around to create a race condition, control its ancestors, or change its
contents? (CWE-362).
fp = fopen(argv[1], "rb");
data/capstone-4.0.2/tests/test_winkernel.cpp:137: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[10];
data/capstone-4.0.2/utils.h:25: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 groups[8]; // list of group this instruction belong to
data/capstone-4.0.2/windows/winkernel_mm.c:16: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[ANYSIZE_ARRAY]; // An address returned to a caller
data/capstone-4.0.2/SStream.c:34:36: [1] (buffer) strlen:
Does not handle strings that are not \0-terminated; if given one it may
perform an over-read (it could cause a crash if unprotected) (CWE-126).
unsigned int len = (unsigned int) strlen(s);
data/capstone-4.0.2/arch/ARM/ARMInstPrinter.c:398:7: [1] (buffer) strlen:
Does not handle strings that are not \0-terminated; if given one it may
perform an over-read (it could cause a crash if unprotected) (CWE-126).
strlen(insn_update_flgs[i].name))) {
data/capstone-4.0.2/arch/M68K/M68KInstPrinter.c:97:5: [1] (buffer) strcat:
Does not check for buffer overflows when concatenating to destination
[MS-banned] (CWE-120). Consider using strcat_s, strncat, strlcat, or
snprintf (warning: strncat is easily misused). Risk is low because the
source is a constant character.
strcat(buffer, "/");
data/capstone-4.0.2/arch/M68K/M68KInstPrinter.c:99: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).
sprintf(buffer + strlen(buffer), "%s%d", prefix, first);
data/capstone-4.0.2/arch/M68K/M68KInstPrinter.c:101: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).
sprintf(buffer + strlen(buffer), "-%s%d", prefix, first + run_length);
data/capstone-4.0.2/arch/PowerPC/PPCInstPrinter.c:200: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(mnem) > 0) {
data/capstone-4.0.2/arch/PowerPC/PPCInstPrinter.c:202: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).
if (mnem[strlen(mnem) - 1] == '-' || mnem[strlen(mnem) - 1] == '+' || mnem[strlen(mnem) - 1] == '.')
data/capstone-4.0.2/arch/PowerPC/PPCInstPrinter.c:202: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).
if (mnem[strlen(mnem) - 1] == '-' || mnem[strlen(mnem) - 1] == '+' || mnem[strlen(mnem) - 1] == '.')
data/capstone-4.0.2/arch/PowerPC/PPCInstPrinter.c:202:79: [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 (mnem[strlen(mnem) - 1] == '-' || mnem[strlen(mnem) - 1] == '+' || mnem[strlen(mnem) - 1] == '.')
data/capstone-4.0.2/arch/PowerPC/PPCInstPrinter.c:203: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).
mnem[strlen(mnem) - 1] = '\0';
data/capstone-4.0.2/arch/Sparc/SparcInstPrinter.c:361:3: [1] (buffer) strncpy:
Easily used incorrectly; doesn't always \0-terminate or check for invalid
pointers [MS-banned] (CWE-120).
strncpy(instr, mnem, sizeof(instr));
data/capstone-4.0.2/arch/Sparc/SparcMapping.c:652: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).
l1 = strlen(name);
data/capstone-4.0.2/arch/Sparc/SparcMapping.c:654: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).
l2 = strlen(hint_maps[i].name);
data/capstone-4.0.2/arch/X86/X86ATTInstPrinter.c:932:3: [1] (buffer) strncpy:
Easily used incorrectly; doesn't always \0-terminate or check for invalid
pointers [MS-banned] (CWE-120).
strncpy(OS->buffer, MI->assembly, sizeof(OS->buffer));
data/capstone-4.0.2/arch/X86/X86Disassembler.c:984:8: [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(instr->assembly, "ud0", 4);
data/capstone-4.0.2/arch/X86/X86Disassembler.c:1006:9: [1] (buffer) strncpy:
Easily used incorrectly; doesn't always \0-terminate or check for invalid
pointers [MS-banned] (CWE-120). Risk is low because the source is a
constant string.
strncpy(instr->assembly, "endbr64", 8);
data/capstone-4.0.2/arch/X86/X86Disassembler.c:1017:9: [1] (buffer) strncpy:
Easily used incorrectly; doesn't always \0-terminate or check for invalid
pointers [MS-banned] (CWE-120). Risk is low because the source is a
constant string.
strncpy(instr->assembly, "endbr32", 8);
data/capstone-4.0.2/arch/X86/X86IntelInstPrinter.c:779:3: [1] (buffer) strncpy:
Easily used incorrectly; doesn't always \0-terminate or check for invalid
pointers [MS-banned] (CWE-120).
strncpy(O->buffer, MI->assembly, sizeof(O->buffer));
data/capstone-4.0.2/cs.c:579:11: [1] (buffer) strncpy:
Easily used incorrectly; doesn't always \0-terminate or check for invalid
pointers [MS-banned] (CWE-120).
(void)strncpy(insn->mnemonic, tmp->insn.mnemonic, sizeof(insn->mnemonic) - 1);
data/capstone-4.0.2/cs.c:592:3: [1] (buffer) strncpy:
Easily used incorrectly; doesn't always \0-terminate or check for invalid
pointers [MS-banned] (CWE-120).
strncpy(insn->op_str, sp, sizeof(insn->op_str) - 1);
data/capstone-4.0.2/cs.c:708:14: [1] (buffer) strncpy:
Easily used incorrectly; doesn't always \0-terminate or check for invalid
pointers [MS-banned] (CWE-120).
(void)strncpy(tmp->insn.mnemonic, opt->mnemonic, sizeof(tmp->insn.mnemonic) - 1);
data/capstone-4.0.2/cs.c:719:13: [1] (buffer) strncpy:
Easily used incorrectly; doesn't always \0-terminate or check for invalid
pointers [MS-banned] (CWE-120).
(void)strncpy(tmp->insn.mnemonic, opt->mnemonic, sizeof(tmp->insn.mnemonic) - 1);
data/capstone-4.0.2/cs.c:927:4: [1] (buffer) strncpy:
Easily used incorrectly; doesn't always \0-terminate or check for invalid
pointers [MS-banned] (CWE-120).
strncpy(insn_cache->mnemonic, handle->skipdata_setup.mnemonic,
data/capstone-4.0.2/cs.c:1137:3: [1] (buffer) strncpy:
Easily used incorrectly; doesn't always \0-terminate or check for invalid
pointers [MS-banned] (CWE-120).
strncpy(insn->mnemonic, handle->skipdata_setup.mnemonic,
data/capstone-4.0.2/cstool/cstool.c:126:6: [1] (buffer) strlen:
Does not handle strings that are not \0-terminated; if given one it may
perform an over-read (it could cause a crash if unprotected) (CWE-126).
if (strlen(code) == 0)
data/capstone-4.0.2/cstool/cstool.c:129: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).
result = (uint8_t *)malloc(strlen(code));
data/capstone-4.0.2/suite/arm/test_arm_regression.c:359: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).
max_len = strlen(tmp_buf);
data/capstone-4.0.2/suite/arm/test_arm_regression.c:360: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).
tmp_len = strlen(valid_code->expected_out);
data/capstone-4.0.2/tests/test_m680x.c:370: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).
slen = (int)strlen(insn[j].mnemonic);
data/capstone-4.0.2/utils.c:94: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(str)+ 1;
ANALYSIS SUMMARY:
Hits = 390
Lines analyzed = 75826 in approximately 1.84 seconds (41229 lines/second)
Physical Source Lines of Code (SLOC) = 62392
Hits@level = [0] 918 [1] 30 [2] 88 [3] 2 [4] 270 [5] 0
Hits@level+ = [0+] 1308 [1+] 390 [2+] 360 [3+] 272 [4+] 270 [5+] 0
Hits/KSLOC@level+ = [0+] 20.9642 [1+] 6.2508 [2+] 5.76997 [3+] 4.35953 [4+] 4.32748 [5+] 0
Dot directories skipped = 2 (--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.