Nmap Security Scanner
*Intro
*Ref Guide
*Install Guide
*Download
*Changelog
*Book
*Docs
Security Lists
*Nmap Hackers
*Nmap Dev
*Bugtraq
*Full Disclosure
*Pen Test
*Basics
*More
Security Tools
*Pass crackers
*Sniffers
*Vuln Scanners
*Web scanners
*Wireless
*Exploitation
*Packet crafters
*More
Site News
Site Search:
Exploit World
Advertising
About/Contact
Credits
Sponsors:
edgeos



Vulnerability Development: Re: non-process-terminating shellcode

Re: non-process-terminating shellcode

From: H D Moore <sflist_at_digitaloffense.net>
Date: Tue, 12 Jun 2007 11:02:00 -0500

Many of the Metasploit Framework modules prevent the exploited process
from terminating by calling ExitThread() after the shellcode completes.
This can often allow you to exploit the same process, over and over
again, and not crash it as long as your shellcode cleans up properly.
Metasploit implements this by swapping out the function hash in the
payload at runtime. When EXITFUNC is set to "thread", it uses
ExitThread(), when it is "process", it uses ExitProcess(), and when it is
set to "seh", it forces an exception (call 0x0 iirc).

-HD

On Tuesday 12 June 2007 10:20, Sanjay R wrote:
> I am looking for some references for creating a shellcode that will
> not terminate the exploited application (process that being exploited)
> and on the same time, inject the payload that, for example, opens a
> shell. I shall be obliged for any help and further readings on this.
Received on Jun 12 2007

[ Nmap | Sec Tools | Mailing Lists | Site News | About/Contact | Advertising | Privacy ]
edgeos