Nmap tls-ticketbleed NSE Script


This page contains detailed information about how to use the tls-ticketbleed NSE script. For list of all NSE scripts, visit the Nmap NSE Library.

Select:
Overview
Error Messages

Script Overview

Script source code: https://github.com/nmap/nmap/tree/master/scripts/tls-ticketbleed.nse
Script categories: vuln, safe
Target service / protocol: ssl
Target network port(s): 261, 271, 324, 443, 465, 563, 585, 636, 853, 989, 990, 992, 993, 994, 995, 2221, 2252, 2376, 3269, 3389, 4911, 5061, 5986, 6679, 6697, 8443, 9001, 8883
List of CVEs: CVE-2016-9244

Script Description

The tls-ticketbleed.nse script detects whether a server is vulnerable to the F5 Ticketbleed bug (CVE-2016-9244).

For additional information:

Tls-ticketbleed NSE Script Arguments

This is a full list of arguments supported by the tls-ticketbleed.nse script:

tls-ticketbleed.protocols

(default tries all) TLSv1.0, TLSv1.1, or TLSv1.2

smbdomain

The domain to log in with. If you aren't in a domain environment, then anything will (should?) be accepted by the server.

smbhash

A password hash to use when logging in. This is given as a single hex string (32 characters) or a pair of hex strings (both 32 characters, optionally separated by a single character). These hashes are the LanMan or NTLM hash of the user's password, and are stored on disk or in memory. They can be retrieved from memory using the fgdump or pwdump tools.

smbnoguest

Use to disable usage of the 'guest' account.

smbpassword

The password to connect with. Be cautious with this, since some servers will lock accounts if the incorrect password is given. Although it's rare that the Administrator account can be locked out, in the off chance that it can, you could get yourself in trouble. To use a blank password, leave this parameter off altogether.

smbtype

The type of SMB authentication to use. These are the possible options:

  • v1: Sends LMv1 and NTLMv1.
  • LMv1: Sends LMv1 only.
  • NTLMv1: Sends NTLMv1 only (default).
  • v2: Sends LMv2 and NTLMv2.
  • LMv2: Sends LMv2 only.
  • NTLMv2: Doesn't exist; the protocol doesn't support NTLMv2 alone. The default, NTLMv1, is a pretty decent compromise between security and compatibility. If you are paranoid, you might want to use v2 or lmv2 for this. (Actually, if you're paranoid, you should be avoiding this protocol altogether!). If you're using an extremely old system, you might need to set this to v1 or lm, which are less secure but more compatible. For information, see smbauth.lua.

smbusername

The SMB username to log in with. The forms "DOMAIN\username" and "username@DOMAIN" are not understood. To set a domain, use the smbdomain argument.

randomseed

Set to a value to change the filenames/service names that are randomly generated.

smbbasic

Forces the authentication to use basic security, as opposed to "extended security". Against most modern systems, extended security should work, but there may be cases where you want to force basic. There's a chance that you'll get better results for enumerating users if you turn on basic authentication.

smbport

Override the default port choice. If smbport is open, it's used. It's assumed to be the same protocol as port 445, not port 139. Since it probably isn't possible to change Windows' ports normally, this is mostly useful if you're bouncing through a relay or something.

smbsign

Controls whether or not server signatures are checked in SMB packets. By default, on Windows, server signatures aren't enabled or required. By default, this library will always sign packets if it knows how, and will check signatures if the server says to. Possible values are:

  • force: Always check server signatures, even if server says it doesn't support them (will Probably fail, but is technically more secure).
  • negotiate: [default] Use signatures if server supports them.
  • ignore: Never check server signatures. Not recommended.
  • disable: Don't send signatures, at all, and don't check the server's. not recommended. More information on signatures can be found in smbauth.lua.

mssql.domain

The domain against which to perform integrated authentication. When set, the scripts assume integrated authentication should be performed, rather than the default sql login.

mssql.instance-all

Targets all SQL server instances discovered through the browser service.

mssql.instance-name

The name of the instance to connect to.

mssql.instance-port

The port of the instance to connect to.

mssql.password

The password for mssql.username. If this argument is not given but mssql.username, a blank password is used.

mssql.protocol

The protocol to use to connect to the instance. The protocol may be either NP,Named Pipes or TCP.

mssql.scanned-ports-only

If set, the script will only connect to ports that were included in the Nmap scan. This may result in instances not being discovered, particularly if UDP port 1434 is not included. Additionally, instances that are found to be running on ports that were not scanned (e.g. if 1434/udp is in the scan and the SQL Server Browser service on that port reports an instance listening on 43210/tcp, which was not scanned) will be reported but will not be stored for use by other ms-sql-* scripts.

mssql.timeout

How long to wait for SQL responses. This is a number followed by ms for milliseconds, s for seconds, m for minutes, or h for hours. Default: 30s.

mssql.username

The username to use to connect to SQL Server instances. This username is used by scripts taking actions that require authentication (e.g. ms-sql-query) This username (and its associated password) takes precedence over any credentials discovered by the ms-sql-brute and ms-sql-empty-password scripts.

smtp.domain

The domain to be returned by get_domain, overriding the target's own domain name.

tls.servername

Hostname to use in the Server Name Indication (SNI) extension. Overrides the target name given on the command line and affects all targets.

vulns.short

If set, vulnerabilities will be output in short format, a single line consisting of the host's target name or IP, the state, and either the CVE ID or the title of the vulnerability. Does not affect XML output.

vulns.showall

If set, the library will show and report all the registered vulnerabilities which includes the NOT VULNERABLE ones. By default the library will only report the VULNERABLE entries: VULNERABLE, LIKELY VULNERABLE, VULNERABLE (DoS) and VULNERABLE (Exploitable). This argument affects the following functions: vulns.Report.make_output(): the default output function for portule/hostrule scripts. vulns.make_output(): the default output function for postrule scripts. vulns.format_vuln() and vulns.format_vuln_table() functions.

- - -
To use these script arguments, add them to the Nmap command line using the --script-args arg1=value,[arg2=value,..] syntax. For example:

nmap --script=tls-ticketbleed --script-args tls-ticketbleed.protocols=value,smbdomain=value <target>

Tls-ticketbleed NSE Script Example Usage

Here's an example of how to use the tls-ticketbleed.nse script:

nmap -p 443 --script tls-ticketbleed <target>

Tls-ticketbleed NSE Script Example Output

Here's a sample output from the tls-ticketbleed.nse script:

| tls-ticketbleed:
|   VULNERABLE:
|   Ticketbleed is a serious issue in products manufactured by F5, a popular
vendor of TLS load-balancers. The issue allows for stealing information from
the load balancer
|     State: VULNERABLE (Exploitable)
|     Risk factor: High
|       Ticketbleed is vulnerability in the implementation of the TLS
SessionTicket extension found in some F5 products. It allows the leakage
("bleeding") of up to 31 bytes of data from uninitialized memory. This is
caused by the TLS stack padding a Session ID, passed from the client, with
data to make it 32-bits long.
|     Exploit results:
|       2ab2ea6a4c167fbe8bf0b36c7d9ed6d3
|       *..jL......l}...
|     References:
|       https://filippo.io/Ticketbleed/
|       https://blog.filippo.io/finding-ticketbleed/
|_      https://support.f5.com/csp/article/K05121675

Tls-ticketbleed NSE Script Example XML Output

There is no sample XML output for this module. However, by providing the -oX <file> option, Nmap will produce a XML output and save it in the file.xml file.

Author

References

See Also

Related NSE scripts to the tls-ticketbleed.nse script:

Visit Nmap NSE Library for more scripts.

The tls-ticketbleed.nse script may fail with the following error messages. Check for the possible causes by using the code snippets highlighted below found in the script source code. This can often times help in identifying the root cause of the problem.

Not running: incompatible tls.lua. Get the latest from https://nmap.org/nsedoc/lib/tls.html

Here is a relevant code snippet related to the "Not running: incompatible tls.lua. Get the latest from https://nmap.org/nsedoc/lib/tls.html" error message:

50:	categories = {"vuln", "safe"}
51:	dependencies = {"https-redirect"}
52:	
53:	portrule = function(host, port)
54:	  if not tls.handshake_parse.NewSessionTicket then
55:	    stdnse.verbose1("Not running: incompatible tls.lua. Get the latest from https://nmap.org/nsedoc/lib/tls.html")
56:	    return false
57:	  end
58:	  -- Ensure we have the privileges necessary to run the PCAP operations this
59:	  -- script depends upon.
60:	  if not nmap.is_privileged() then

StartTLS connection to server failed: %s

Here is a relevant code snippet related to the "StartTLS connection to server failed: %s" error message:

85:	  local starttls = sslcert.getPrepareTLSWithoutReconnect(port)
86:	  if starttls then
87:	    local status
88:	    status, socket = starttls(host, port)
89:	    if not status then
90:	      stdnse.debug3("StartTLS connection to server failed: %s", socket)
91:	      return
92:	    end
93:	  else
94:	    socket = nmap.new_socket()
95:	    local status, err = socket:connect(host, port, "tcp")

Connection to server failed: %s

Here is a relevant code snippet related to the "Connection to server failed: %s" error message:

92:	    end
93:	  else
94:	    socket = nmap.new_socket()
95:	    local status, err = socket:connect(host, port, "tcp")
96:	    if not status then
97:	      stdnse.debug3("Connection to server failed: %s", err)
98:	      return
99:	    end
100:	  end
101:	
102:	  socket:set_timeout(5000)

Failed to retrieve local port used by socket.

Here is a relevant code snippet related to the "Failed to retrieve local port used by socket." error message:

102:	  socket:set_timeout(5000)
103:	
104:	  -- Find out the port we'll be using in our TLS negotiation.
105:	  local status, _, lport = socket:get_info()
106:	  if( not(status) ) then
107:	    stdnse.debug3("Failed to retrieve local port used by socket.")
108:	    return
109:	  end
110:	
111:	  -- We are only interested in capturing the TLS responses from the
112:	  -- server, not our traffic. We need to set the snaplen to be fairly

Failed to create packet from captured data.

Here is a relevant code snippet related to the "Failed to create packet from captured data." error message:

135:	    end
136:	
137:	    -- Parse captured packet and extract data.
138:	    local pkt = packet.Packet:new(layer3, #layer3)
139:	    if not pkt then
140:	      stdnse.debug3("Failed to create packet from captured data.")
141:	      return
142:	    end
143:	
144:	    if not pkt:tcp_parse() then
145:	      stdnse.debug3("Failed to parse captured packet.")

Failed to parse captured packet.

Here is a relevant code snippet related to the "Failed to parse captured packet." error message:

140:	      stdnse.debug3("Failed to create packet from captured data.")
141:	      return
142:	    end
143:	
144:	    if not pkt:tcp_parse() then
145:	      stdnse.debug3("Failed to parse captured packet.")
146:	      return
147:	    end
148:	
149:	    local tls_data = pkt:raw(pkt.tcp_data_offset)
150:	    table.insert(buf, tls_data)

StartTLS connection to server failed: %s

Here is a relevant code snippet related to the "StartTLS connection to server failed: %s" error message:

226:	  -- Connect the socket so that it is ready to start a TLS session.
227:	  if starttls then
228:	    local status
229:	    status, socket = starttls(host, port)
230:	    if not status then
231:	      stdnse.debug3("StartTLS connection to server failed: %s", socket)
232:	      return
233:	    end
234:	  else
235:	    socket = nmap.new_socket()
236:	    local status, err = socket:connect(host, port, "tcp")

Connection to server failed: %s

Here is a relevant code snippet related to the "Connection to server failed: %s" error message:

233:	    end
234:	  else
235:	    socket = nmap.new_socket()
236:	    local status, err = socket:connect(host, port, "tcp")
237:	    if not status then
238:	      stdnse.debug3("Connection to server failed: %s", err)
239:	      return
240:	    end
241:	  end
242:	
243:	  -- Send Client Hello to the target server.

Server failed to respond with a handshake record: %s

Here is a relevant code snippet related to the "Server failed to respond with a handshake record: %s" error message:

270:	  if record.protocol ~= version then
271:	    stdnse.debug1("Server responded with a different protocol than we requested: %s", record.protocol)
272:	    return
273:	  end
274:	  if record.type ~= "handshake" then
275:	    stdnse.debug1("Server failed to respond with a handshake record: %s", record.type)
276:	    return
277:	  end
278:	
279:	  -- Search for the ServerHello record, which contains the Session ID
280:	  -- we want.

Failed to receive a Server Hello record.

Here is a relevant code snippet related to the "Failed to receive a Server Hello record." error message:

284:	      sid_new = body.session_id
285:	    end
286:	  end
287:	
288:	  if not sid_new then
289:	    stdnse.debug1("Failed to receive a Server Hello record.")
290:	    return
291:	  end
292:	
293:	  if sid_new == "" then
294:	    stdnse.debug1("Server did not respond with a session ID.")

Version

This page has been created based on Nmap version 7.92.

Go back to menu.