mailing list archives
How payloads (shellcodes) used in exploiting
From: jerome.athias at free.fr (Jerome Athias)
Date: Thu, 29 Mar 2007 11:33:10 +0200
it is due to the fact of the Metasploit Framework uses kind of magic and
After joking, yes the shellcode has to be sent to the target to having
To avoid badchars and for ID/PS evasion reasons, the base code of the
shellcode (called payload) will me modified by the Framework before to
be sent to the target. (ie: XORed)
So yes it could be different every time.
A way to retrieve it in your packets is to attach a debugger to the
target application/service and see what it receives, and then compare
this with your capture.
Note that in the version 2 of the MSF, you can view the shellcodes's
codes (:p) in
I hope it helps
Rawal, Rajesh a ?crit :
I am using metasploit framework 3, exploiting windows and linux
I have captured packets using ethereal, but I didn't find the payload
(position) used during the exploittation.
Exploit used was "windows/smb/ms06_040_netapi" and used
payload "windows/shell_bind_tcp" and it successfully exploited remote
host and got command of remote host machine. Also taken packet capture
during this process.
I m not able to find payload of "windows/shell_bind_tcp" in packet
1. Can I know where this payload exist (where it comes during this
sesion) in packet capture?
2. Does these payloads (shellcodes) differs in every new exploit attemts?
waiting for positive response
**NSEZ Noida | India
"DISCLAIMER: This message is proprietary to iPolicy Networks Pvt. Ltd. and is intended solely for the use of the
individuals to whom it is addressed. It may contain privileged or confidential information and should not be
circulated or used for any purpose other than for what is intended. If you have received this message in error,
please notify the originator immediately. If you are not the intended recipient, you are notified that you are
strictly prohibited from using, copying, altering, or disclosing the contents of this message. iPolicy Networks
accepts no responsibility for loss or damage arising from the use of the information transmitted by this email
including damage from virus."....IPF 5K