phor3nsic / opmonster

2 stars 0 forks source link

NSE: failed to initialize the script engine: #1

Closed an0th3rhuman closed 4 years ago

an0th3rhuman commented 4 years ago

While running the script, i got the below error:

NSE: failed to initialize the script engine:

I did googling and found https://stackoverflow.com/questions/56871370/nse-failed-to-initialize-the-script-engine. But still couldn't fix the issue

phor3nsic commented 4 years ago

Hello, thanks for your contact, I will analyze and respond soon

phor3nsic commented 4 years ago

Hi @an0th3rhuman, I was able to confirm the same error you got, and I realized that when I received this response it was due to the server having the version that is no longer vulnerable.

I will organize a response instead of this error message, to facilitate the usability of xpl.

phor3nsic commented 4 years ago

Hi @an0th3rhuman, I decided to debug the exploit, and I saw that it is also possible that the vulnerable server does not resolve external connections, uncomment line 64 and run the exploit as follows:

python opmonster.py https://TARGET/ google.com 80 "whoami" | grep "Failed to resolve"

If you confirm the grep response, it is possible that the target will not resolve external services

phor3nsic commented 4 years ago

I made an update, which brings a message regarding the resolution of external services, as mentioned earlier, could you confirm if your problem was solved?

Regards @phor3nsic

phor3nsic commented 4 years ago

As there are no further questions, this problem will be closed as resolved, anything will be opened again