Nmap ssl-cert NSE Script


This page contains detailed information about how to use the ssl-cert 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/ssl-cert.nse
Script categories: default, safe, discovery
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: -

Script Description

The ssl-cert.nse script retrieves a server's SSL certificate. The amount of information printed about the certificate depends on the verbosity level. With no extra verbosity, the script prints the validity period and the commonName, organizationName, stateOrProvinceName, and countryName of the subject. 

443/tcp open  https
| ssl-cert: Subject: commonName=www.paypal.com/organizationName=PayPal, Inc.\
/stateOrProvinceName=California/countryName=US
| Not valid before: 2011-03-23 00:00:00
|_Not valid after:  2013-04-01 23:59:59

With -v it adds the issuer name and fingerprints. 

443/tcp open  https
| ssl-cert: Subject: commonName=www.paypal.com/organizationName=PayPal, Inc.\
/stateOrProvinceName=California/countryName=US
| Issuer: commonName=VeriSign Class 3 Extended Validation SSL CA\
/organizationName=VeriSign, Inc./countryName=US
| Public Key type: rsa
| Public Key bits: 2048
| Signature Algorithm: sha1WithRSAEncryption
| Not valid before: 2011-03-23 00:00:00
| Not valid after:  2013-04-01 23:59:59
| MD5:   bf47 ceca d861 efa7 7d14 88ad 4a73 cb5b
|_SHA-1: d846 5221 467a 0d15 3df0 9f2e af6d 4390 0213 9a68

With -vv it adds the PEM-encoded contents of the entire certificate. 

443/tcp open  https
| ssl-cert: Subject: commonName=www.paypal.com/organizationName=PayPal, Inc.\
/stateOrProvinceName=California/countryName=US/1.3.6.1.4.1.311.60.2.1.2=Delaware\
/postalCode=95131-2021/localityName=San Jose/serialNumber=3014267\
/streetAddress=2211 N 1st St/1.3.6.1.4.1.311.60.2.1.3=US\
/organizationalUnitName=PayPal Production/businessCategory=Private Organization
| Issuer: commonName=VeriSign Class 3 Extended Validation SSL CA\
/organizationName=VeriSign, Inc./countryName=US\
/organizationalUnitName=Terms of use at https://www.verisign.com/rpa (c)06
| Public Key type: rsa
| Public Key bits: 2048
| Signature Algorithm: sha1WithRSAEncryption
| Not valid before: 2011-03-23 00:00:00
| Not valid after:  2013-04-01 23:59:59
| MD5:   bf47 ceca d861 efa7 7d14 88ad 4a73 cb5b
| SHA-1: d846 5221 467a 0d15 3df0 9f2e af6d 4390 0213 9a68
| -----BEGIN CERTIFICATE-----
| MIIGSzCCBTOgAwIBAgIQLjOHT2/i1B7T//819qTJGDANBgkqhkiG9w0BAQUFADCB
...
| 9YDR12XLZeQjO1uiunCsJkDIf9/5Mqpu57pw8v1QNA==
|_-----END CERTIFICATE-----

Ssl-cert NSE Script Arguments

This is a full list of arguments supported by the ssl-cert.nse script:

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.

- - -
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=ssl-cert --script-args smbdomain=value,smbhash=value <target>

Ssl-cert NSE Script Example Usage

Here's an example of how to use the ssl-cert.nse script:

nmap --script=ssl-cert <target>

Ssl-cert NSE Script Example Output

Here's a sample output from the ssl-cert.nse script:

443/tcp open  https
| ssl-cert: Subject: commonName=www.paypal.com/organizationName=PayPal, Inc.\
/stateOrProvinceName=California/countryName=US
| Not valid before: 2011-03-23 00:00:00
|_Not valid after:  2013-04-01 23:59:59

Ssl-cert NSE Script Example XML Output

Here's a sample XML output from the ssl-cert.nse script produced by providing the -oX <file> Nmap option:

 <table key="subject">
   <elem key="1.3.6.1.4.1.311.60.2.1.2">Delaware</elem>
   <elem key="1.3.6.1.4.1.311.60.2.1.3">US</elem>
   <elem key="postalCode">95131-2021</elem>
   <elem key="localityName">San Jose</elem>
   <elem key="serialNumber">3014267</elem>
   <elem key="countryName">US</elem>
   <elem key="stateOrProvinceName">California</elem>
   <elem key="streetAddress">2211 N 1st St</elem>
   <elem key="organizationalUnitName">PayPal Production</elem>
   <elem key="commonName">www.paypal.com</elem>
   <elem key="organizationName">PayPal, Inc.</elem>
   <elem key="businessCategory">Private Organization</elem>
 </table>
 <table key="issuer">
   <elem key="organizationalUnitName">Terms of use at https://www.verisign.com/rpa (c)06</elem>
   <elem key="organizationName">VeriSign, Inc.</elem>
   <elem key="commonName">VeriSign Class 3 Extended Validation SSL CA</elem>
   <elem key="countryName">US</elem>
 </table>
 <table key="pubkey">
   <elem key="type">rsa</elem>
   <elem key="bits">2048</elem>
   <elem key="modulus">DF40CCF2C50A0D65....35B5927DF25D4DE5</elem>
   <elem key="exponent">65537</elem>
 </table>
 <elem key="sig_algo">sha1WithRSAEncryption</elem>
 <table key="validity">
   <elem key="notBefore">2011-03-23T00:00:00+00:00</elem>
   <elem key="notAfter">2013-04-01T23:59:59+00:00</elem>
 </table>
 <elem key="md5">bf47cecad861efa77d1488ad4a73cb5b</elem>
 <elem key="sha1">d8465221467a0d153df09f2eaf6d439002139a68</elem>
 <elem key="pem">-----BEGIN CERTIFICATE-----
 MIIGSzCCBTOgAwIBAgIQLjOHT2/i1B7T//819qTJGDANBgkqhkiG9w0BAQUFADCB
 ...
 9YDR12XLZeQjO1uiunCsJkDIf9/5Mqpu57pw8v1QNA==
 -----END CERTIFICATE-----
 </elem>

Author

  • David Fifield

References

See Also

Related NSE scripts to the ssl-cert.nse script:

Visit Nmap NSE Library for more scripts.

The ssl-cert.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.

getCertificate error: %s

Here is a relevant code snippet related to the "getCertificate error: %s" error message:

307:	
308:	action = function(host, port)
309:	  host.targetname = tls.servername(host)
310:	  local status, cert = sslcert.getCertificate(host, port)
311:	  if ( not(status) ) then
312:	    stdnse.debug1("getCertificate error: %s", cert or "unknown")
313:	    return
314:	  end
315:	
316:	  return output_tab(cert), output_str(cert)
317:	end

Version

This page has been created based on Nmap version 7.92.

Go back to menu.