Questions about this topic? Sign up to ask in the talk tab.

Difference between revisions of "Shellcode/Environment"

From NetSec
Jump to: navigation, search
(→‎int3 breakpoints)
 
(40 intermediate revisions by 3 users not shown)
Line 1: Line 1:
−
It is possible use [[shellcode]] to [[#x86/x64_GetCPU_(any_OS)|determine instruction set architecture]], [[#GetPc|determine the process counter]], [[#Last_call|determine the location last returned to]], or [[#int3_breakpoints|bypass and detect int3 breakpoints]] within the current execution environment.
+
It is possible use [[shellcode]] to [[#x86/x64_GetCPU_(any_OS)|determine instruction set architecture]], [[#GetPc|the process counter]], [[#Last_call|the location last returned to]], or [[#int3_breakpoints|bypass and detect int3 breakpoints]] within the current execution environment.
  
 
{{info|<center>The code and ideas discussed here are part of an [[shellcode|all-encompassing shellcode portal]]. Everything described here and the full source of any given code is available in [[Shellcode/Appendix#Environment|the appendix]], as well as in the downloadable [[shellcodecs]] package.</center>}}  
 
{{info|<center>The code and ideas discussed here are part of an [[shellcode|all-encompassing shellcode portal]]. Everything described here and the full source of any given code is available in [[Shellcode/Appendix#Environment|the appendix]], as well as in the downloadable [[shellcodecs]] package.</center>}}  
  
  
−
== x86/x64 GetCPU (any OS) ==
 
−
 
−
Architecture can only be determined when compatible channels between the target [[instruction set architecture]]s can be isolated.  As long as the [[assembly#instructions|instructions]] perform valid behavior and do not cause access faults on [[operating system]]s native to the architecture, it is possible to use a single bytecode sequence in order to determine architecture across a variety of processors.  It takes a high amount of familiarity and experience with two or more given instruction sets to write shellcode for multiple architectures.
 
−
 
−
x64 does not vastly differ from x86 because '''AMD''' stepped in to correct intel's calling convention and architecture. 
 
−
 
−
=== Instruction Comparison ===
 
−
This chart was derived by cross referencing [[Alphanumeric_shellcode#Available_Instructions|available alphanumeric 64 bit instructions]] with [[Ascii_shellcode#Available_Instructions|available printable 32 bit instructions]].
 
−
 
−
{| class="wikitable" style="text-align:center; width:60%;"
 
−
|+ Intercompatible x86* Alphanumeric Opcodes
 
−
|-
 
−
! scope="col" | Hex
 
−
! scope="col" | ASCII
 
−
! scope="col" | Assembler Instruction
 
−
|-
 
−
! scope="row" | 0x64, 0x65
 
−
| d,e
 
−
|[fs &#x7c; gs] prefix
 
−
|-
 
−
! scope="row" | 0x66, 0x67
 
−
| f,g
 
−
| 16bit [operand &#x7c; ptr] override
 
−
|-
 
−
! scope="row" | 0x68, 0x6a
 
−
| h,j
 
−
| push
 
−
|-
 
−
! scope="row" | 0x69, 0x6b
 
−
| i,k
 
−
| imul
 
−
|-
 
−
! scope="row" | 0x6c-0x6f
 
−
| l-o
 
−
| ins[bwd], outs[bwd]
 
−
|-
 
−
! scope="row" | 0x70-0x7a
 
−
| p-z
 
−
| Conditional Jumps
 
−
|-
 
−
! scope="row" | 0x30-0x35
 
−
| 0-5
 
−
| xor
 
−
|-
 
−
! scope="row" | 0x36
 
−
| 6
 
−
| %ss segment register
 
−
|-
 
−
! scope="row" | 0x38-0x39
 
−
| 8,9
 
−
| cmp
 
−
|-
 
−
! scope="row" | 0x50-0x57
 
−
| P-W
 
−
| push *x, *i, *p
 
−
|-
 
−
! scope="row" | 0x58-0x5a
 
−
| XYZ
 
−
| pop [*ax, *cx, *dx]
 
−
|-
 
−
|}
 
−
 
−
=== Inter-compatibility theory ===
 
−
The opcodes which are specifically not compatible are limited to the 32 and 64 bit opcodes '''0x40-0x4f''', which allow a 32 bit processor to increment or decrement its general-purpose registers, but become prefixes for manipulation of 64 bit registers and 8 additional 64 bit general purpose registers in x64 environments, '''%r8-%r15'''. 
 
−
 
−
Because not ''all'' opcodes are intercompatible, yet comparisons and conditional jumps ''are'' intercompatible, it is possible to determine the architecture of an x86 processor using exclusively alphanumeric opcodes.
 
−
 
−
By making use of these additional registers (which 32 bit processors do not have), one can perform an operation that will set a value on a different register in the two processors.
 
−
 
−
Following this, a conditional statement can be made against one of the two registers to determine if the value was set. 
 
−
 
−
Using the '''pop''' instruction is the most effective way to set the value of a register due to instructional limitations (to keep the code alphanumeric).  Using an alternative register to %rsp or %esp as a placeholder for the stack pointer enables the use of an effective conditional statement to determine if the value of a register is equal to the most recent thing pushed or popped from the stack.
 
−
 
−
=== Practically Applied: Code ===
 
−
This simple alphanumeric bytecode is 15 bytes long, ending in a comparison which returns '''equal''' on a 32 bit system and '''not equal''' on a 64 bit system. 
 
−
 
−
When implementing this bytecode, a conditional jump afterwards may be best reserved for the '''t''' and '''u''' instructions, '''jump if equal''' and '''jump if not equal''', respectively.
 
−
 
−
* Assembled:
 
−
:'''TX4HPZTAZAYVH92'''
 
−
 
−
* Disassembly:
 
−
{| class="wikitable"
 
−
|-
 
−
! OpCodes
 
−
! x86
 
−
! x64
 
−
|-
 
−
| '''54'''
 
−
| <source lang="asm">push %esp</source>
 
−
| <source lang="asm">push %rsp</source>
 
−
|-
 
−
| '''58'''
 
−
| <source lang="asm">pop %eax</source>
 
−
| <source lang="asm">pop %rax</source>
 
−
|-
 
−
| '''34 48'''
 
−
| <source lang="asm">xor $0x48, %al</source>
 
−
| <source lang="asm">xor $0x48, %al</source>
 
−
|-
 
−
| '''50'''
 
−
| <source lang="asm">push %eax</source>
 
−
| <source lang="asm">push %rax</source>
 
−
|-
 
−
| '''5a'''
 
−
| <source lang="asm">pop %edx</source>
 
−
| <source lang="asm">pop %rdx</source>
 
−
|-
 
−
| '''54'''
 
−
| <source lang="asm">push %esp</source>
 
−
| <source lang="asm">push %rsp</source>
 
−
|-
 
−
| <div align="right"><font size="-1">'''''41''''' <br />
 
−
'''''5a'''''</font></div>
 
−
|<source lang="asm">inc %ecx
 
−
pop %edx</source>
 
−
|<source lang="asm">pop %r10</source>
 
−
|-
 
−
| <div align="right"><font size="-1">'''''41'''''<br />
 
−
'''''59'''''</font></div>
 
−
|<source lang="asm">inc %ecx
 
−
pop %ecx</source>
 
−
|<source lang="asm">pop %r9</source>
 
−
|-
 
−
| '''56'''
 
−
|<source lang="asm">push %esi</source>
 
−
|<source lang="asm">push %rsi</source>
 
−
|-
 
−
| <div align="right"><font size="-1">'''''48'''''<br />
 
−
'''''39 32'''''</font></div>
 
−
|<source lang="asm">dec %eax
 
−
cmp %esi,(%edx)</source>
 
−
|<source lang="asm">cmp %rsi,(%rdx)</source>
 
−
|}
 
−
 
−
This code executes similarly on both a 32-bit and 64-bit system - similarly, but not identically. The key discrepancy between how the two architectures execute this code is contained in the opcodes "0x41 - 0x4f".
 
−
 
−
Under a 32-bit architecture, this code pops the value of esp (which was pushed onto the stack previously) into edx and increments ecx. The esp register is a pointer to the top of the stack, so now rdx contains a pointer to the top of the stack. After this is done, the shellcode goes on to push esi onto the stack - so the value of esi now resides at the top of the stack. When the code executes its final comparison - "cmp %esi, (%edx)" - it is comparing the value of esi to the value that edx points to. As edx points to the top of the stack, and as we have just pushed esi onto the top of the stack, we are comparing the value of esi with the value of esi. For this reason, it returns ''equal''.
 
−
 
−
This shellcode is ''not equal'' under a 64-bit architecture, however. The opcodes "41 5a 41 59" have a different function - instead of popping the value of esp into rdx, it instead pops it into the 64-bit register %r10 without incrementing %ecx or %rcx, as 0x41 is used as a prefix to indicate the access to the 64-bit architecture. As a result, when the final comparison is made between rsi and the value referenced by rdx, it returns not equal, as rdx does not point to the top of the stack.
 
−
 
−
On a 64-bit system, this will not cause a segfault because (%rdx) points to somewhere inside the stack.
 
  
 
== GetPc ==
 
== GetPc ==
−
The '''GetPc''' technique is any technique implementing code which obtains the current instruction pointer.  This can be useful when writing [[polymorphic]] shellcode, or other code that must become aware of its environment because environment information cannot be supplied prior to execution of the code.  
+
The '''GetPc''' technique is implementation of code which obtains the current instruction pointer.  This can be useful when writing [[Shellcode/Self-modifying|self-modifying shellcode]], or other code that must become aware of its environment, as environment information cannot be supplied prior to execution of the code.  
  
 
=== x86 (32 bit) ===
 
=== x86 (32 bit) ===
Line 168: Line 26:
 
startup:
 
startup:
 
call getpc      ; the %rax register now contains %rip on the next line  
 
call getpc      ; the %rax register now contains %rip on the next line  
 +
</source>}}
 +
 +
* Alternatively:
 +
{{code|text=<source lang="asm">
 +
jmp startup
 +
pc:
 +
  nop
 +
startup:
 +
  lea -1(%rip), %rax  ; the %rax register now contains the address of `pc'.
 
</source>}}
 
</source>}}
  
 
== Last call ==
 
== Last call ==
−
Typically, when [[shellcode]] is being executed at the time of overflow, assuming that the nop sled does not modify the stack, the pointer to the beginning of the executing code is at -0x8(%rsp), or -0x4(%esp), because it was just ''returned to''.  In many cases, this can be used in place of a '''getPc''' for [[Shellcode/Self-modifying|polymorphic code]].
+
Typically, when [[shellcode]] is being executed at the time of a [[buffer overflow]], assuming that the nop sled does not modify the stack, the [[memory addresses|pointer]] to the beginning of the executing code is at -0x8(%rsp), or -0x4(%esp), because it was just ''[[return oriented programming|returned to]]'' as a result of the [[call stack]] being overwritten during the overflow process.  In many cases, this can be used in place of a '''[[#GetPc|GetPc]]''' for [[Shellcode/Self-modifying|polymorphic shellcode]].  The [[Shellcode/Alphanumeric#Last_call|alphanumeric last call]] for x64 systems comes out to 13 bytes.
  
 
=== 32-bit ===
 
=== 32-bit ===
 +
==== Null-free ====
 
{{code|text=<source lang="asm">
 
{{code|text=<source lang="asm">
 
   mov -0x4(%esp), %eax
 
   mov -0x4(%esp), %eax
 
</source>}}
 
</source>}}
−
 
  
 
=== 64-bit ===
 
=== 64-bit ===
 +
==== Null-free ====
 
{{code|text=<source lang="asm">
 
{{code|text=<source lang="asm">
 
   mov -0x8(%rsp), %rax
 
   mov -0x8(%rsp), %rax
 
</source>}}
 
</source>}}
  
−
=== Alphanumeric ===
+
== int3 breakpoints ==
−
* Assembled ''x64'':
+
Int3 breakpoints can be detected during out-of-line code execution when the code in question is being debugged by an in-line debugger.  
−
  XTX4e4uHcp4H3p4H30
+
−
{{code|text=<source lang="asm">
+
−
.text
+
−
.global _start
+
−
_start:
+
−
  pop %rax
+
−
  push %rsp
+
−
  pop %rax
+
−
  xor $0x65, %al
+
−
  xor $0x75, %al
+
−
  movslq 0x34(%rax), %rsi
+
−
  xor 0x34(%rax), %rsi
+
−
  xor (%rax), %rsi
+
−
</source>}}
+
  
−
== int3 breakpoints ==
 
 
{{code|text=<source lang="asm">
 
{{code|text=<source lang="asm">
 
.text
 
.text
Line 222: Line 75:
 
   nop
 
   nop
 
</source>}}
 
</source>}}
 +
 +
The relevant code in this snippet is:
 +
 +
{{code|text=<source lang="asm">
 +
push $0x3458686a
 +
push $0x0975c084
 +
</source>}}
 +
 +
When the code jumps to the code directly after the first ''push'' (0x68), it gets read by the CPU as:
 +
 +
  0: 6a 68                pushq  $0x68
 +
  2: 58                  pop    %rax
 +
  3: 34 68                xor    $0x68,%al
 +
  5: 85 c0                test  %eax,%eax
 +
  7: 75 09                jne    0x09
 +
 +
However, it is read by an inline disassembler as:
 +
 +
    d:    68 6a 68 58 34      pushq  $0x3458686a
 +
    12:    68 84 c0 75 09      pushq  $0x975c084
 +
    17:    90                  nop
 +
 +
This is because an inline disassembler does not recognize code based on how it is executed but on how it looks in memory; however, because the first ''0x68'' is skipped completely, the code is executed differently than what appears in memory. What this code actually does is detect breakpoints. First, it moves ''0x68'' into ''%rax''. Then, if a breakpoint has been set on the second push instruction, the ''xor $0x68,%al'' instruction will become ''xor $0xcc,%al'' (0xcc is the breakpoint instruction), and instead of ''%rax'' being nulled (0x68 xor 0x68 becomes 0), it will become 0xa4. The test instruction checks if ''%rax'' is zero: if it is not zero the code then ''jmp''s 0x09 bytes forward (this behaviour can be adjusted to act however the programmer desires). This code allows arbitrary shellcode to detect breakpoints and act differently depending on whether or not they exist.
 +
 +
The following is a demonstration of this specific code in use. In the first demonstration, a breakpoint is set on the ''nop'' instruction and the breakpoint is hit. In the second, the breakpoint is set on the second ''push'' instruction, and the breakpoint is skipped.
  
 
   {} shellcode gdb loaders/loader-64                                                                       
 
   {} shellcode gdb loaders/loader-64                                                                       
Line 227: Line 105:
 
   (gdb) break ret_to_shellcode  
 
   (gdb) break ret_to_shellcode  
 
   Breakpoint 1 at 0x4000b1
 
   Breakpoint 1 at 0x4000b1
−
 
+
 
 
   (gdb) run "$(generators/shellcode-generator.py --file=int3 --raw)"
 
   (gdb) run "$(generators/shellcode-generator.py --file=int3 --raw)"
 
   Starting program: /home/user/loaders/loader-64 "$(generators/shellcode-generator.py --file=int3 --raw)"
 
   Starting program: /home/user/loaders/loader-64 "$(generators/shellcode-generator.py --file=int3 --raw)"
Line 247: Line 125:
 
   Continuing.
 
   Continuing.
 
    
 
    
−
   Breakpoint 2, 0x00007ffff7fbe017 in ?? ()
+
   '''Breakpoint 2, 0x00007ffff7fbe017 in ?? ()'''
−
   (gdb) quit
+
   '''(gdb) quit'''
 
   A debugging session is active.
 
   A debugging session is active.
 
    
 
    
−
Inferior 1 [process 9760] will be killed.
+
      Inferior 1 [process 9760] will be killed.
 
    
 
    
 
   Quit anyway? (y or n) y
 
   Quit anyway? (y or n) y
Line 271: Line 149:
 
   0x7ffff7fbe008: callq  0x7ffff7fbe002
 
   0x7ffff7fbe008: callq  0x7ffff7fbe002
 
   0x7ffff7fbe00d: pushq  $0x3458686a
 
   0x7ffff7fbe00d: pushq  $0x3458686a
−
   0x7ffff7fbe012: pushq  $0x975c084
+
   '''0x7ffff7fbe012''':       '''pushq  $0x975c084'''
−
   0x7ffff7fbe017:     nop
+
   0x7ffff7fbe017:       nop
 
   '''...'''
 
   '''...'''
−
   (gdb) break *0x7ffff7fbe012
+
   (gdb) break '''*0x7ffff7fbe012'''
−
   Breakpoint 2 at 0x7ffff7fbe012
+
   Breakpoint 2 at '''0x7ffff7fbe012'''
 
   (gdb) c
 
   (gdb) c
−
   Continuing.
+
   '''Continuing.'''
−
   [Inferior 1 (process 9778) exited normally]
+
   '''[Inferior 1 (process 9778) exited normally]'''
−
   (gdb)
+
   '''(gdb)'''
 +
 
 +
{{social}}

Latest revision as of 03:32, 25 April 2013

It is possible use shellcode to determine instruction set architecture, the process counter, the location last returned to, or bypass and detect int3 breakpoints within the current execution environment.

c3el4.png
The code and ideas discussed here are part of an all-encompassing shellcode portal. Everything described here and the full source of any given code is available in the appendix, as well as in the downloadable shellcodecs package.


GetPc

The GetPc technique is implementation of code which obtains the current instruction pointer. This can be useful when writing self-modifying shellcode, or other code that must become aware of its environment, as environment information cannot be supplied prior to execution of the code.

x86 (32 bit)

 
jmp startup
getpc:
   mov (%esp), %eax
   ret
startup:
call getpc       ; the %eax register now contains %eip on the next line 
 

x64

 
jmp startup
getpc:
   mov (%rsp), %rax
   ret
startup:
call getpc       ; the %rax register now contains %rip on the next line 
 
  • Alternatively:
 
jmp startup
pc:
  nop
startup:
  lea -1(%rip), %rax  ; the %rax register now contains the address of `pc'.
 

Last call

Typically, when shellcode is being executed at the time of a buffer overflow, assuming that the nop sled does not modify the stack, the pointer to the beginning of the executing code is at -0x8(%rsp), or -0x4(%esp), because it was just returned to as a result of the call stack being overwritten during the overflow process. In many cases, this can be used in place of a GetPc for polymorphic shellcode. The alphanumeric last call for x64 systems comes out to 13 bytes.

32-bit

Null-free

 
  mov -0x4(%esp), %eax
 

64-bit

Null-free

 
  mov -0x8(%rsp), %rax
 

int3 breakpoints

Int3 breakpoints can be detected during out-of-line code execution when the code in question is being debugged by an in-line debugger. 

 
.text
.global _start
_start:
 
  jmp startup
 
go_retro:
  pop %rcx
  inc %rcx
  jmp *%rcx
 
startup:
  call go_retro
 
volatile_segment:
  push $0x3458686a
  push $0x0975c084
  nop
 

The relevant code in this snippet is: 

 
push $0x3458686a
push $0x0975c084
 

When the code jumps to the code directly after the first push (0x68), it gets read by the CPU as: 

  0:	6a 68                	pushq  $0x68
  2:	58                   	pop    %rax
  3:	34 68                	xor    $0x68,%al
  5:	85 c0                	test   %eax,%eax
  7:	75 09                	jne    0x09

However, it is read by an inline disassembler as: 

    d:    68 6a 68 58 34       	pushq  $0x3458686a
   12:    68 84 c0 75 09       	pushq  $0x975c084
   17:    90                   	nop

This is because an inline disassembler does not recognize code based on how it is executed but on how it looks in memory; however, because the first 0x68 is skipped completely, the code is executed differently than what appears in memory. What this code actually does is detect breakpoints. First, it moves 0x68 into %rax. Then, if a breakpoint has been set on the second push instruction, the xor $0x68,%al instruction will become xor $0xcc,%al (0xcc is the breakpoint instruction), and instead of %rax being nulled (0x68 xor 0x68 becomes 0), it will become 0xa4. The test instruction checks if %rax is zero: if it is not zero the code then jmps 0x09 bytes forward (this behaviour can be adjusted to act however the programmer desires). This code allows arbitrary shellcode to detect breakpoints and act differently depending on whether or not they exist.

The following is a demonstration of this specific code in use. In the first demonstration, a breakpoint is set on the nop instruction and the breakpoint is hit. In the second, the breakpoint is set on the second push instruction, and the breakpoint is skipped. 

 {} shellcode gdb loaders/loader-64                                                                       
 Reading symbols from /home/user/loaders/loader-64...(no debugging symbols found)...done.
 (gdb) break ret_to_shellcode 
 Breakpoint 1 at 0x4000b1
 
 (gdb) run "$(generators/shellcode-generator.py --file=int3 --raw)"
 Starting program: /home/user/loaders/loader-64 "$(generators/shellcode-generator.py --file=int3 --raw)"
 
 Breakpoint 1, 0x00000000004000b1 in ret_to_shellcode ()
 (gdb) x/24i $rax
  0x7ffff7fbe000:	jmp    0x7ffff7fbe008
  0x7ffff7fbe002:	pop    %rcx
  0x7ffff7fbe003:	inc    %rcx
  0x7ffff7fbe006:	jmpq   *%rcx
  0x7ffff7fbe008:	callq  0x7ffff7fbe002
  0x7ffff7fbe00d:	pushq  $0x3458686a
  0x7ffff7fbe012:	pushq  $0x975c084
  0x7ffff7fbe017:       nop
  ...
 (gdb) break *0x7ffff7fbe017
 Breakpoint 2 at 0x7ffff7fbe017
 (gdb) c
 Continuing.
 
 Breakpoint 2, 0x00007ffff7fbe017 in ?? ()
 (gdb) quit
 A debugging session is active.
 
     Inferior 1 [process 9760] will be killed.
 
 Quit anyway? (y or n) y



 {} shellcode gdb loaders/loader-64
 Reading symbols from /home/user/loaders/loader-64...(no debugging symbols found)...done.
 (gdb) break ret_to_shellcode 
 Breakpoint 1 at 0x4000b1
 (gdb) run "$(generators/shellcode-generator.py --file=int3 --raw)"
 Starting program: /home/user/loaders/loader-64 "$(generators/shellcode-generator.py --file=int3 --raw)"
 Breakpoint 1, 0x00000000004000b1 in ret_to_shellcode ()
 (gdb) x/24i $rax
  0x7ffff7fbe000:	jmp    0x7ffff7fbe008
  0x7ffff7fbe002:	pop    %rcx
  0x7ffff7fbe003:	inc    %rcx
  0x7ffff7fbe006:	jmpq   *%rcx
  0x7ffff7fbe008:	callq  0x7ffff7fbe002
  0x7ffff7fbe00d:	pushq  $0x3458686a
  0x7ffff7fbe012:       pushq  $0x975c084
  0x7ffff7fbe017:       nop
  ...
 (gdb) break *0x7ffff7fbe012
 Breakpoint 2 at 0x7ffff7fbe012
 (gdb) c
 Continuing.
 [Inferior 1 (process 9778) exited normally]
 (gdb)
Retrieved from "http://nets.ec/index.php?title=Shellcode/Environment&oldid=10807"