Re: heartbleed script only seems to work on known SSL ports in 6.46 for windows

[Kent Fritz <kfritz () wolfman devio us>]

On Wed, Apr 23, 2014 at 10:52:44AM -0400, Patrik Karlsson wrote:
> It will work fine in most cases. It looks like there may be a problem for
> this script and other scripts relying on SSL when a port responds in both
> http and https.
>
> -Patrik
I did a quick modification on my nmap-service-probes, and changed the first
nginx match line on ~5589 to a softmatch, and it works.  Of course this is
not the real fix -- I think it requires the match lines to be re-written to
exclude the 400 response for nginx and apache (and any other server that has
a canned response to hitting ssl port with plain text.)

# nmap -p80,4444 -sV puffy1

Starting Nmap 6.45 ( http://nmap.org ) at 2014-04-23 08:39 PDT
Nmap scan report for puffy1 (10.57.3.34)
Host is up (0.00021s latency).
rDNS record for 10.57.3.34: puffy1.shoretel.com
PORT     STATE SERVICE  VERSION
80/tcp   open  http     nginx
4444/tcp open  ssl/http nginx
MAC Address: 00:50:04:88:21:00 (3com)

Service detection performed. Please report any incorrect results at http://nmap.org/submit/ .
Nmap done: 1 IP address (1 host up) scanned in 17.94 seconds

_______________________________________________
Sent through the dev mailing list
http://nmap.org/mailman/listinfo/dev
Archived at http://seclists.org/nmap-dev/