Is there a tool in MHS to do this? All I am seeing are tools to do codecaves.
I want to inject say
push 0
push 1
call 0xXXXXXXXX
and execute it.
Would make playing around with a programs functions very easy.
Inject/Execute code?
Moderators: g3nuin3, SpeedWing, WhiteHat, mezzo
9 posts • Page 1 of 1
Inject/Execute code?
by high6 » Tue Jun 16, 2009 5:09 am
- high6
- Sir Hacks-A-Lot
- Posts: 34
- Joined: Sat Aug 05, 2006 7:06 am
by spunge » Tue Jun 16, 2009 5:33 am
Allocate some memory.
Write in the allocated memory:
Call CreateThread at the allocated memory.
You should be able to do this with LSS.
Write in the allocated memory:
- Code: Select all
push 0
push 1
call XXXXXXXX
push 0
call ExitThread
Call CreateThread at the allocated memory.
You should be able to do this with LSS.
- spunge
- NULL
- Posts: 121
- Joined: Sun Jul 27, 2008 4:58 am
- Location: VEH callback
by L. Spiro » Tue Jun 16, 2009 12:51 pm
Of course.
You would do well to read the function reference in the help file.
Everything is sorted by group, and you would have quickly seen the MHSAssembly section, clicked it, and noticed the first function, AutoAssemble(), which provides the full functionality of the Auto-Assembler in MHS.
L. Spiro
You would do well to read the function reference in the help file.
Everything is sorted by group, and you would have quickly seen the MHSAssembly section, clicked it, and noticed the first function, AutoAssemble(), which provides the full functionality of the Auto-Assembler in MHS.
L. Spiro
Our songs remind you of songs you’ve never heard.
-
L. Spiro - L. Spiro
- Posts: 3129
- Joined: Mon Jul 17, 2006 10:14 pm
- Location: Tokyo, Japan
by L. Spiro » Tue Jun 16, 2009 5:57 pm
No.
For the same reason why the preview window (Next button in the Auto-Assembler) shows multiple lists. There is no convenient way to show the byte code; it can be any number of arrays and each array can be any length.
Working with this from scripts would mean manually querying the number of arrays needed (which would require MHS to compile the code), then allocating that many arrays, then querying the lengths of each array (which requires another recompile of the code), then allocating each array, then filling the arrays (another recompile of the code), using it however you want, deallocating each array, then deallocating the array of arrays.
Not only would such a feature be slow but also very tedious to use.
L. Spiro
For the same reason why the preview window (Next button in the Auto-Assembler) shows multiple lists. There is no convenient way to show the byte code; it can be any number of arrays and each array can be any length.
Working with this from scripts would mean manually querying the number of arrays needed (which would require MHS to compile the code), then allocating that many arrays, then querying the lengths of each array (which requires another recompile of the code), then allocating each array, then filling the arrays (another recompile of the code), using it however you want, deallocating each array, then deallocating the array of arrays.
Not only would such a feature be slow but also very tedious to use.
L. Spiro
Our songs remind you of songs you’ve never heard.
-
L. Spiro - L. Spiro
- Posts: 3129
- Joined: Mon Jul 17, 2006 10:14 pm
- Location: Tokyo, Japan
9 posts • Page 1 of 1
Who is online
Users browsing this forum: No registered users and 0 guests