0

The webserver is configured to redirect all HTTP request traffic to HTTPS. And there seems to be different application running on 80 and 443.

443 is not vulnerable but there are lot of vulnerability exists on 80. When I am trying to browse http://example.com through browser it redirects me to https://example.com.

Now when I use nikto to scan the site at port 80 it list a lot of vulnerable links. Please suggest.

closed as unclear what you're asking by Arminius, Steffen Ullrich, Serge Ballesta, Rory Alsop May 27 '17 at 14:22

Please clarify your specific problem or add additional details to highlight exactly what you need. As it's currently written, it’s hard to tell exactly what you're asking. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.

  • 5
    I find it unclear what you are asking. Why would the redirect matter if you are scanning for vulnerabilities? – Arminius May 25 '17 at 11:41
  • I cannot access any resource that is running on port 80 though browser, 302 redirect is enabled. But tried Nikto to scan and it shows a lot of links it scans on port 80. Now when I want to access those links in browser it re-directs to 443 with a different website/ application running. – LionKing May 29 '17 at 10:38
1

A redirect (to https, or anywhere else) is a "302" return code from the server

https://en.wikipedia.org/wiki/List_of_HTTP_status_codes

which your browser honors, and then re-requests the redirected page.

If "nikto [...scans...] the site at port 80 [and] list a lot of vulnerable links"

then the server is still returning a page. You would need to use a modified web client which doesn't follow the "302" redirect, the way nikto apparently isn't.

That still seems odd though, as most web serves which send a redirect do not also send the original/old page. You may want to be sure nikto isn't just showing you the contents of the page after silently following the redirect to the https site.

Finally, the software running port 80 and 443 might be the same. A single web server can handle both http and https connections, and serve out the same or different pages in response

0

I think the site may have HSTS enabled, in which case your browser doesn't even do the HTTP request. You can remove the HSTS flag from the site in your browser, but it will get set again when you visit the HTTPS site.

Not the answer you're looking for? Browse other questions tagged or ask your own question.