Difference between revisions of "Code injection"
Jump to navigation
Jump to search
Ibrahimj44 (talk | contribs) m |
m (very minor copyediting) |
||
| Line 1: | Line 1: | ||
| − | + | '''Code injection''' is the act of injecting code and causing it to be executed, either automatically (with the [http://resources.infosecinstitute.com/using-createremotethread-for-dll-injection-on-windows/ CreateRemoteThread Windows function]) or by jumping to there from the target process after modifying the code. | |
| − | Code injection is the act of injecting code and causing it to be executed | ||
| − | There are multiple ways of injecting code into a target process. The most common | + | There are multiple ways of injecting code into a target process. The most common methods are DLL injection and assembly injection. |
| − | One use of code injection is for finding dynamic addresses that tend to change each time the game is run. By placing a code injection on a routine that accesses that address, like a | + | One use of code injection is for finding dynamic addresses that tend to change each time the game is run. By placing a code injection on a routine that accesses that address, like a user interface update routine, you can find the address of that specific variable. |
Revision as of 01:38, 22 January 2016
Code injection is the act of injecting code and causing it to be executed, either automatically (with the CreateRemoteThread Windows function) or by jumping to there from the target process after modifying the code.
There are multiple ways of injecting code into a target process. The most common methods are DLL injection and assembly injection.
One use of code injection is for finding dynamic addresses that tend to change each time the game is run. By placing a code injection on a routine that accesses that address, like a user interface update routine, you can find the address of that specific variable.
