How'd you do it?
This section should also tell us any relevant information about the
environment; for example, if an exploit that used to work is failing,
tell us the victim operating system and service versions.
launch cmd
nothing on client side
IE 11.0.9600.18015
Windows 7 (6.1.7601)
4.15.0
Community installer (from http://www.rapid7.com/products/metasploit/download.jsp)
ubuntu
It would be helpful to know what exploit you're attempting to use. Some details from the Internet Explorer version you're targeting would probably be nice as well, but I can't say what particular DLL's we'd need information from without first knowing which exploit module you're using.
Thanks for updating. I'll have a look at it later
I probably won't have a chance to focus on this until the weekend or next week. In the meantime, what operating system is the target running on?
There was a cumulative update earlier this year which added functionality to disable features of the VBScript language and/or the entire language itself. I'm still not positive on exactly what - I am no expert on VBScript (nor do I aspire to ever be such .... ever).
I'd guess at this time that you might be running the exploit against a target that has the vuln patched, in addition to possibly having the previously mentioned update, which results in this weird error versus the exploit just not doing anything at all. If that's not it, I'll just have to investigate.
I updated the OS version.
I am almost sure IE was not patched (last applied KB from 2015!)
Regarding the OS patch, i can check. Do you know which KB is related to this very fix? I was almost sure the system was vulnerable before trying (based on the KB date), but I can of course check again.
Thanks for your help anyway!
I wondered if the Antivirus could be the cause of the crash. So I tried on a new workstation with no antivirus at all, and it appears that I obtained the same result with the automation error related to the bl.A variable... Did you have any chance to have a look to the issue?
Hello,
Did you have any chance to have a look at the issue?
Thanks a lot!
Sorry, I've been on vacation for awhile and have been playing catch up this week. I probably should have mentioned that. I haven't had a chance to look at anything yet.
As far as the the cause, I wouldn't think AV would have anything to do with it. I'm still inclined to say its the major VBScript changes, as that error only makes sense in that context. We'll see though.