print (evaluate and print expression in debuggee)

Command
print
Syntax
print [expression]
Description
Shows the result of an expression that will be executed in the remote debuggee.
Parameters
[expression]
The expression is based on HyperDbg's scripting language.
Examples
The following command shows the @rax register in the debuggee.
1
0: kHyperDbg> print @rax
Copied!
The following command shows the data as an 8-byte hex, pointed by the @rcx register.
1
0: kHyperDbg> print dq(@rcx))
Copied!
The following command shows the value pointed by [email protected] which $proc is equivalent to current _EPROCESS added to the rdx register.
1
0: kHyperDbg> print [email protected]
Copied!
The following command shows the value of an address, which first, rax register is added with 0xa0 constant then a dereference occurs and the target is shown as a QWORD hex.
1
0: kHyperDbg> print poi(@rax+a0)
Copied!
IOCTL
This commands works over serial by sending the serial packets to the remote computer.
First of all, you should fill the following structure, set the ScriptBufferSize and ScriptBufferPointer to the values you got from the script engine interpreter, and leave the Resultand set the IsFormat to false.
After that, you should move the interpreted buffer to the end of the structure (this structure is a header for the interpreted buffer).
1
typedef struct _DEBUGGEE_SCRIPT_PACKET {
2
​
3
  UINT32 ScriptBufferSize;
4
  UINT32 ScriptBufferPointer;
5
  BOOLEAN IsFormat;
6
  UINT32 Result;
7
​
8
  //
9
  // The script buffer is here
10
  //
11
​
12
} DEBUGGEE_SCRIPT_PACKET, *PDEBUGGEE_SCRIPT_PACKET;
Copied!
Next step is sending the above structure to the debuggee when debuggee is paused and waiting for new command on vmx-root mode.
You should send the above structure with DEBUGGER_REMOTE_PACKET_REQUESTED_ACTION_ON_VMX_ROOT_RUN_SCRIPT as RequestedAction and DEBUGGER_REMOTE_PACKET_TYPE_DEBUGGER_TO_DEBUGGEE_EXECUTE_ON_VMX_ROOT as PacketType.
In return, the debuggee sends the above structure with the following type.
1
DEBUGGER_REMOTE_PACKET_REQUESTED_ACTION_DEBUGGEE_RESULT_OF_RUNNING_SCRIPT
Copied!
In the returned structure, the Result is filled by the kernel.
If the Result is DEBUGEER_OPERATION_WAS_SUCCESSFULL, then the operation was successful. Otherwise, the returned result is an error.
The following function is responsible for sending script buffers in the debugger.
1
BOOLEAN KdSendScriptPacketToDebuggee(UINT64 BufferAddress, UINT32 BufferLength, UINT32 Pointer, BOOLEAN IsFormat);
Copied!
Remarks
This command is exactly like print(expr); in script engine, except that HyperDbg automatically adds print( and );.
This command is guaranteed to keep debuggee in a halt state (in Debugger Mode); thus, nothing will change during its execution.
Requirements
None
Related
None

pause (break to the debugger and pause processing kernel packets)

lm (view loaded modules)

Last modified 3mo ago

Copy link

Edit on GitHub

Contents