3 ms·
I believe this is more commonly known as "overlapping instructions/opcodes"; and it was a relatively common technique for size optimisation or obfuscation in th
by userbinator 6y ago
I believe this is more commonly known as "overlapping instructions/opcodes"; and it was a relatively common technique for size optimisation or obfuscation in the 80s and early 90s, when Asm was the norm for PC software.
To my knowledge, there are no tools which do a good job of presenting the parallel execution streams. Instead, the typical flow requires the human to iterate through attempting disassembly at different offsets.
I remember seeing one (tracing) disassembler which does this, presenting the different streams side-by-side until they realign again. No doubt cracking groups probably have their own private versions of such tools.
- adrian_b 6y agoYes, indeed, this technique was frequently used in ancient programs. For example, many decades ago I have disassembled many Microsoft programs, like the MS-DOS Basic interpreter or Fortran compiler. In all those Microsoft programs, there were many loops where the jump at the end of the loop jumped in the middle of the initial instruction. Thus the first execution of the loop executed different instructions than the next executions, which was used, e.g., for the loop initialization. There were also many if-then-else structures where one of the branches ended with a jump towards the middle of some instruction, so that depending on which was the value of the condition different instructions were executed. The instructions whose middle position was the target of a jump were usually instructions with immediate operands, so that when executed from the beginning the immediate value was treated as data, while when reached through a jump in the middle of the instruction, the immediate data was treated as an instruction opcode.
- dataking 6y agoThe term unintended instructions is common in the infosec community and was (as far as I know) popularized by the seminal paper on ROP https://hovav.net/ucsd/dist/geometry.pdf https://hovav.net/ucsd/dist/geometry.pdf I'm sure different terms are used in other communities.