-
Notifications
You must be signed in to change notification settings - Fork 121
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Off-by-one access in fillRegister #39
Comments
There's a similar case with the bytes '\x62' in the below case: default:
switch (GV.OperandSize) {
case 16:
#ifndef BEA_LIGHT_DISASSEMBLY
(void)strcpy((char *)pMyOperand->OpMnemonic + i, Registers16Bits[index]);
Cheers |
Same with '\x4f' in: case 64:
#ifndef BEA_LIGHT_DISASSEMBLY
(void)strcpy((char *)pMyOperand->OpMnemonic + i,
Registers64Bits[index]);
Cheers |
0vercl0k
added a commit
to 0vercl0k/rp
that referenced
this issue
Jan 17, 2022
0vercl0k
added a commit
to 0vercl0k/rp
that referenced
this issue
Jan 17, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello,
The following bytes '\x44\x0f\xf8\x41\x8b' (disassembled as
psubb mm0,mmword ptr [rcx-75h]
by windbg) triggers an off-by-one in theRegistersMMX
global variable:The
index
variable is off-by-one:Cheers
The text was updated successfully, but these errors were encountered: