Vulscan is a module which enhances nmap to a vulnerability scanner.
The nmap option -sV enables version detection per service which is used to determine potential flaws
according to the identified product.
The data is looked up in an offline version of VulDB.
This repo is a fork of the original vulscan script: https://github.com/scipag/vulscan
This fork uses the NIST National Vulnerability Database
to link CVEs and CVSS scores to identified service versions.
This script was tested with nmap version 7.8 - it may not work with older versions.
Please install the files into the following folder of your Nmap installation:
Nmap\scripts\vulscan\*
Clone the GitHub repository like this:
cd /tmp
git clone [email protected]:awei82/vulscan.git
sudo ln -s /tmp/vulscan /usr/share/nmap/scripts/vulscan
You may execute vulscan with the following argument to use a single database:
nmap -sV --script=vulscan/vulscan.nse --script-args vulscandb=[DB Name].csv [scan target]
nmap -sV --script=vulscan/vulscan.nse --script-args vulscandb=nvd_latest.csv www.example.com
It is also possible to create and reference your own databases. This requires to create a database file, which has the following structure:
<id>;<title>;<vulnerability_score>
Run the following script to get the latest CVE db for Vulnscan
python nist_nvd_download.py
If the version detection was able to identify the software version and the vulnerability database is providing such details, also this data is matched.
Disabling this feature might introduce false-positive but might also eliminate false-negatives and increase performance slighty. If you want to disable additional version matching, use the following argument:
--script-args vulscanversiondetection=0
Version detection of vulscan is only as good as Nmap version detection and the vulnerability database entries are. Some databases do not provide conclusive version information, which may lead to a lot of false-positives (as can be seen for Apache servers).
The script is trying to identify the best matches only. If no positive match could been found, the best possible match (with might be a false-positive) is put on display.
If you want to show all matches, which might introduce a lot of false-positives but might be useful for further investigation, use the following argument:
--script-args vulscanshowall=1
The interactive mode helps you to override version detection results for every port. Use the following argument to enable the interactive mode:
--script-args vulscaninteractive=1
All matching results are printed one by line. The default layout for this is:
[{id}] {cvss} - {title}\n
It is possible to use another pre-defined report structure with the following argument:
--script-args vulscanoutput=details
--script-args vulscanoutput=listid
--script-args vulscanoutput=listlink
--script-args vulscanoutput=listtitle
You may enforce your own report structure by using the following argument (some examples):
--script-args vulscanoutput='{link}\n{title}\n\n'
--script-args vulscanoutput='ID: {id} - Title: {title} ({matches})\n'
--script-args vulscanoutput='{id} | {product} | {version}\n'
Supported are the following elements for a dynamic report template:
- {id} - ID of the vulnerability
- {title} - Title of the vulnerability
- {matches} - Count of matches
- {product} - Matched product string(s)
- {version} - Matched version string(s)
- {link} - Link to the vulnerability database entry
- \n - Newline
- \t - Tab
Every default database comes with an url and a link, which is used during the scanning and might be accessed as {link} within the customized report template. To use custom database links, use the following argument:
--script-args "vulscandblink=http://example.org/{id}"
Simply run make docker to build the docker container for vulscan.
Note - the Dockerfile is currently customized with a wrapper script - update this as needed for your use case.
Keep in mind that this kind of derivative vulnerability scanning heavily relies on the confidence of the version detection of nmap, the amount of documented vulnerabilities and the accuracy of pattern matching. The existence of potential flaws is not verified with additional scanning nor exploiting techniques.