enquire Posted December 18, 2019 Share Posted December 18, 2019 I'm working through the Metasploitable 3 vulnerabilities. One of the frequent ones I see mentioned is Elasticsearch on port 9200. I can't get nmap to identify that port as Elasticsearch. Even when I do a -A -sV --version-all (and a bunch of other noisy scans) the best it can do is say it's the default wap-wsp port. So, I have 2 questions: Will Elasticsearch always be running on that port? Can anything be preventing nmap from identifying it on 9200? I'm running through virtualbox - I've heard it can drop some packets when looking at wireshark, but I haven't heard whether the VM can affect the scan results. (I've tried running the script_mvel_rce exploit blind... it copies the file but can't execute it). Quote Link to comment Share on other sites More sharing options...
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.