JIT spraying: Difference between revisions
wrong tech |
Rbrightwell (talk | contribs) BHDC10 Reference link no longer valid, so removed. 404 Page not found. |
||
| Line 4: | Line 4: | ||
A [[Just-in-time compiler]] (JIT) by definition produces code as its data. Since the purpose is to produce executable data, a JIT compiler is one of the few types of programs that cannot be run in a no-executable-data environment. Because of this, JIT compilers are normally exempt from data execution prevention. A JIT spray attack does [[heap spraying]] with the generated code. |
A [[Just-in-time compiler]] (JIT) by definition produces code as its data. Since the purpose is to produce executable data, a JIT compiler is one of the few types of programs that cannot be run in a no-executable-data environment. Because of this, JIT compilers are normally exempt from data execution prevention. A JIT spray attack does [[heap spraying]] with the generated code. |
||
To produce exploit code from JIT, an idea from Dion Blazakis (BHDC-2010 |
To produce exploit code from JIT, an idea from Dion Blazakis (BHDC-2010) is used. The input program, typically [[Javascript]] or [[ActionScript]], typically contains numerous constant values that can be erroneously executed as code. For example, the [[XOR]] operation could be used:<ref name="dsecrg">[http://dsecrg.com/pages/pub/show.php?id=22 Writing JIT-Spray Shellcode for fun and profit], Alexey Sintsov, (pdf)</ref> |
||
var a=(0x11223344^0x44332211^0x44332211^ ...) |
var a=(0x11223344^0x44332211^0x44332211^ ...) |
||
| Line 25: | Line 25: | ||
Computer hardware that allows jumping into the middle of an instruction includes [[x86]], [[x86-64]], and [[ARM]]. Although especially effective on this type of hardware, JIT spraying works on other systems as well. |
Computer hardware that allows jumping into the middle of an instruction includes [[x86]], [[x86-64]], and [[ARM]]. Although especially effective on this type of hardware, JIT spraying works on other systems as well. |
||
To protect against JIT spraying, the JIT code can be disabled or made less predictable for the attacker. |
To protect against JIT spraying, the JIT code can be disabled or made less predictable for the attacker. |
||
== References == |
== References == |
||
Revision as of 03:33, 26 January 2013
JIT spraying is a class of computer security exploit that circumvents the protection of address space randomization (ASLR) and data execution prevention (DEP) by exploiting the behavior of just-in-time compilation.[1] It has been reported to have been used to penetrate security features in the PDF format [2] and Adobe's Flash technology.[3]
A Just-in-time compiler (JIT) by definition produces code as its data. Since the purpose is to produce executable data, a JIT compiler is one of the few types of programs that cannot be run in a no-executable-data environment. Because of this, JIT compilers are normally exempt from data execution prevention. A JIT spray attack does heap spraying with the generated code.
To produce exploit code from JIT, an idea from Dion Blazakis (BHDC-2010) is used. The input program, typically Javascript or ActionScript, typically contains numerous constant values that can be erroneously executed as code. For example, the XOR operation could be used:[4]
var a=(0x11223344^0x44332211^0x44332211^ ...)
JIT then will transform bytecode to native x86 code like:
0: b8 44 33 22 11 mov $0x11223344,%eax mov eax,0x11223344 5: 35 11 22 33 44 xor $0x44332211,%eax xor eax,0x44332211 a: 35 11 22 33 44 xor $0x44332211,%eax xor eax,0x44332211
The attacker then uses a suitable bug to redirect code execution into the newly generated code. For example, a buffer overflow or use after free bug could allow the attack to modify a function pointer or return address.
This causes the CPU to execute instructions in a way that was unintended by the JIT authors. The attacker is usually not even limited to the expected instruction boundries; it is possible to jump into the middle of an intended instruction to have the CPU interpret it as something else. As with non-JIT ROP attacks, this may be enough operations to usefully take control of the computer. Continuing the above example, jumping to the second byte of the "mov" instruction results in an "inc" instruction:
1: 44 inc %esp inc esp 2: 33 22 xor (%edx),%esp xor esp,DWORD PTR [edx] 4: 11 35 11 22 33 44 adc %esi,0x44332211 adc DWORD PTR ds:0x44332211,esi a: 35 11 22 33 44 xor $0x44332211,%eax xor eax,0x44332211
Computer hardware that allows jumping into the middle of an instruction includes x86, x86-64, and ARM. Although especially effective on this type of hardware, JIT spraying works on other systems as well.
To protect against JIT spraying, the JIT code can be disabled or made less predictable for the attacker.
References
- ^ Jürgen Schmidt (20 January 2011). "Return of the sprayer -- JIT Spraying: Exploits to beat DEP and ASLR". The H. Retrieved 22 January 2011.
- ^ Haifei Li (10 February 2010). "JIT Spraying in PDF". Fortinet blog. Retrieved 22 January 2011.
- ^ Larry Seltzer (4 February 2010). "New "JIT Spray" Penetrates Best Windows Defenses". PCmag.com. Retrieved 22 January 2011.
- ^ Writing JIT-Spray Shellcode for fun and profit, Alexey Sintsov, (pdf)
 | This computer security article is a stub. You can help Wikipedia by expanding it. |