mailing list archives
Re: inline meterpreter payload
From: Stephen Haywood <stephen () averagesecurityguy info>
Date: Tue, 11 Sep 2012 19:37:30 -0400
I've got a C program that does exactly that but have never been able
to get it to connect back to Metasploit after the second stage is
Information Security Consultant
On Sep 11, 2012, at 6:14 PM, "egypt () metasploit com"
<egypt () metasploit com> wrote:
On Tue, Sep 11, 2012 at 4:40 PM, Chip <jeffschips () gmail com> wrote:
On 9/11/2012 5:35 PM, egypt () metasploit com wrote:
On Tue, Sep 11, 2012 at 4:31 PM, Richard Miles
<richard.k.miles () googlemail com> wrote:
For example, if I use shellcodeexec and it's not detected by AV the first
stage will be loaded on memory and it will download the second stage (.dll)
and only run it from memory, right?
The executables that Metasploit creates do not contain meterpreter,
just a stager stub that reads a 4-byte length followed by that many
bytes of a second stage. In the case of meterpreter, the second stage
is a Reflective DLL. Anything that can connect to a Metasploit handler
and follow the same steps will accomplish the same thing.
I've been looking for this explanation for a long time. Is there a tutorial
on how to do exactly that -- connect a home-grown binary to the Metasploit
handler in the proper fashion so it works?
No tutorials that I know of, but here are the basic steps:
* connect to the handler
* read a 4-byte length
* allocate a length-byte buffer
* mark it as writable and executable (on Windows you'll need
VirtualProtect for this)
* read length bytes into that buffer
* jump to the buffer. easiest way to do this in C is cast it to a
function pointer and call it.
Hope this helped,
Re: inline meterpreter payload HD Moore (Sep 07)