Metasploit mailing list archives
another payload execution failure
From: security at vahle.de (Thomas Werth)
Date: Thu, 12 Jun 2008 15:37:22 +0200
thx, but even with this payload aborts program like other msf-payloads, too. I just like to mention nopsled with infinite loop runs fine without any exception. Well that is enough to prove remote code execution is possible. I'm just curios why msf payloads fail . Application is a simple test prog where in nestled func a wrong for statement is vulnerable. H D Moore schrieb:
The command line needs to be: "cmd /c echo test2 > c:\\test.txt" -HD On Thursday 12 June 2008, Thomas Werth wrote:Program is running on a winXP Prof with SP3 . Well WinExec is processed but cmd isn't executed. I have CMD echo test2 > c:\test.txt as command, but there is no file created. I've created small perl poc, which contains infinitve loop via $attackstring .= "\xeb\xfe"; This one is correct processed and program loops forever. So i guess problem indeed seems to be closy related to payloads..._______________________________________________ http://spool.metasploit.com/mailman/listinfo/framework
Current thread:
- MSF and Windows SP3 (solved), (continued)
- MSF and Windows SP3 (solved) mmiller at hick.org (Jun 05)
- MSF and Windows SP3 (solved) Thomas Werth (Jun 05)
- another payload execution failure Thomas Werth (Jun 11)
- another payload execution failure H D Moore (Jun 11)
- another payload execution failure Thomas Werth (Jun 11)
- another payload execution failure Patrick Webster (Jun 11)
- Message not available
- another payload execution failure Thomas Werth (Jun 11)
- another payload execution failure mmiller at hick.org (Jun 11)
- another payload execution failure Thomas Werth (Jun 11)
- another payload execution failure H D Moore (Jun 12)
- another payload execution failure Thomas Werth (Jun 12)
- another payload execution failure H D Moore (Jun 12)