@mokrunka said:
Yeah, beating my head against a wall here.
Understandable. It is important to remember exploits are never guaranteed at the best of times.
It is not unusual to have to try an MSF exploit several times before it works. But it shouldn’t be hundreds if it is ever going to work.
I’ve tried several times, and I really think I’m putting in the right options and target/host info.
Ok, but really there are only a few possible scenarios here:
- You are using the wrong exploit
- You have used the wrong options
- Something on the box is broken
- Your system is preventing the reverse connection (Firewall or other security tool/privs)
If you are confident it is number 3, reset the box. If a reset doesn’t fix the problem it is one of the others.
Using a r******.t** shell,
I hope you are using a payload with a different name to that. Something along the lines of
//r_* for example.
I’m still getting an error of 'This exploit may require manual cleanup of ‘.********’ on the target. Maybe that file has been inadvertently modified somehow.
So, the easiest thing here is to read through the MSF Ruby file for the exploit to see what it does and what that message means. It may be irrelevant to the problem if it is generated under normal circumstances and if you haven’t got the exploit to work, you don’t know what “normal” looks like here.
If you read through the source code you can get an idea for what it is trying to do. It looks like the problem might be that it can’t write the file it wants to write, which is why it cant automatically delete it.
That implies the options aren’t correct.
tl;dr - reset the box, if that doesn’t work your options are wrong.