Image
 
Latest Additions
 
EH-Net Login
Welcome Guest.






Lost Password?
No account yet? Register
Who's Online
We have 23 guests and 5 members online
EH-Net Donations

Enter Amount:
$

Google Ads
EH-Net News Feeds
Latest Additions
Book Recommendations





 
Advertisement

You are here: Home arrow Forum arrow Ethical Hacking Discussions and Related Certificationsarrow Network Pen Testingarrow Metasploit: forward/backward porting
Ethical Hacker Community Forums
January 09, 2009, 08:06:51 PM *
Welcome, Guest. Please login or register.
Did you miss your activation email?

Login with username, password and session length
News: ChicagoCon 2009 - May 4 - 9. Boot Camps & an Ethical Hacking Conf. www.chicagocon.com
 
   Home   Help Calendar Login Register  
Pages: [1]   Go Down
  Print  
Author Topic: Metasploit: forward/backward porting  (Read 890 times)
0 Members and 1 Guest are viewing this topic.
RoleReversal
Hero Member
*****
Offline Offline

Posts: 508


View Profile WWW
« on: December 04, 2008, 10:54:51 AM »

Guys, looking for some advice from those more knowledgeable than myself. Without giving too much away I'm trying to prove a vulnerability and determine how a bad guy broke into a server.

I believe the entry point to be a vulnerable FTP service/daemon, I've got a PoC for metasploit (.pm) which appears to be successful but framework 2 doesn't have any valid shellcode modules for my system architecture. I believe I've got a few options to go down and was hoping someone could either advise on the best route, or point out something simple that I've missed.

Possible options:
  • Hard-code shellcode into framework 2 module
  • Port PoC exploit to Framework 3's ruby
  • Port a shellcode module from framework3 to framework 2
  • Take PoC  as guide and create custom exploit for my own testing
  • .....

Each looks theoretically possible, but each also looks like it would take some time. Whilst I don't mind putting in the effort to learn something new (workload permitting I may try each for learning purposes) but I'm on a schedule to get the vulnerability cleaned up and accounted for so could do with some advice.

Thanks in advance,
RR
Logged

A little bit of sanity:
http://www.infosanity.co.uk
apollo
Jr. Member
**
Offline Offline

Posts: 51


View Profile WWW
« Reply #1 on: December 04, 2008, 11:18:29 AM »

I would say it depends on the size and complexity of the exploit.  If it an extremely complex module, I'd backport shellcode from msf3, if it is a pretty simple one I'd port the exploit, or if you think you are going to use this exploit again in the future I'd port to msf3 since the options for things you can do seem to keep getting larger under the msf3 platform.

Also, in theory, you could hardcode your payload into the exploit with the perl output from msfpayload and then just use the handler capabilities of the module that you borrowed from msf3 with the closet things that mach in the msf2 framework. 
Logged
Pages: [1]   Go Up
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.7 | SMF © 2006-2007, Simple Machines LLC
Joomla Bridge by JoomlaHacks.com
Valid XHTML 1.0! Valid CSS!
Page created in 0.05 seconds with 22 queries.
 
Sponsors

cwnp_moto__120x90.gif

Polls
How many security events including conferences and training do you attend a year:
 
Support EH-Net


Support EH-Net by
Buying all of your
Amazon items using
the search bar above.

cbtnuggets_logo_125.jpg
Try CBT Nuggets Free!
Recent Forum Topics
Vote For EH-Net

progenic.com
Click here to Vote!

binarica.com
Binarica Logo

Add to Technorati Favorites
technorati fave

 
         
Advertisement

© 2009 The Ethical Hacker Network
Joomla! is Free Software released under the GNU/GPL License.