A complete listing of the contextual patching actions are described in the following sections.
The main patching dialog can be launched via the Assemble action in the right click context menu. It simulates a basic IDA disassembly view that can be used to edit one or several instructions in rapid succession.
The assembly line is an editable field that can be used to modify instructions in real-time. Pressing enter will commit (patch) the entered instruction into the database.
Your current location (a.k.a your cursor) will always be highlighted in green. Instructions that will be clobbered as a result of your patch / edit will be highlighted in red prior to committing the patch.
DOWN arrow keys can be used while still focused on the editable assembly text field to quickly move the cursor up and down the disassembly view without using the mouse.
The most common patching action is to NOP out one or more instructions. For this reason, the NOP action will always be visible in the right click menu for quick access.
Individual instructions can be NOP’ed, as well as a selected range of instructions.
Force Conditional Jump
Forcing a conditional jump to always execute a ‘good’ path is another common patching action. The plugin will only show this action when right clicking a conditional jump instruction.
If you never want a conditional jump to be taken, you can just NOP it instead!
Save & Quick Apply
Patches can be saved (applied) to a selected executable via the patching submenu at any time. The quick-apply action makes it even faster to save subsequent patches using the same settings.
The plugin will also make an active effort to retain a backup (
.bak) of the original executable which it uses to ‘cleanly’ apply the current set of database patches during each save.
Finally, if you are ever unhappy with a patch you can simply right click patched (yellow) blocks of instructions to revert them to their original value.
While it is ‘easy’ to revert bytes back to their original value, it can be ‘hard’ to restore analysis to its previous state. Reverting a patch may occasionally require additional human fixups.
- Further improve ARM / ARM64 / THUMB correctness
- Define ‘better’ behavior for cpp::like::symbols(…) / IDBs (very sketchy right now)
- Adding / Updating / Modifying / Showing / Warning about Relocation Entries??
- Handle renamed registers (like against dwarf annotated idb)?
- A number of new instructions (circa 2017 and later) are not supported by Keystone
- A few problematic instruction encodings by Keystone
Time and motivation permitting, future work may include:
- Enable the remaining major architectures supported by Keystone:
- PPC32 / PPC64 / MIPS32 / MIPS64 / SPARC / SystemZ
- Multi instruction assembly (eg.
xor eax, eax; ret;)
- Multi line assembly (eg. shellcode / asm labels)
- Interactive byte / data / string editing
- Symbol hinting / auto-complete / fuzzy-matching
- Syntax highlighting the editable assembly line
- Better hinting of errors, syntax issues, etc
- NOP / Force Jump from Hex-Rays view (sounds easy, but probably pretty hard!)
- radio button toggle between ‘pretty print’ mode vs ‘raw’ mode? or display both?
Pretty: mov [rsp+48h+dwCreationDisposition], 3
Raw: mov [rsp+20h], 3
I welcome external contributions, issues, and feature requests. Please make any pull requests to the
develop branch of this repository if you would like them to be considered for a future release.
- Markus Gaasedelen (@gaasedelen)
If you like the site, please consider joining the telegram channel or supporting us on Patreon using the button below.