> For the complete documentation index, see [llms.txt](https://docs.netcap.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.netcap.io/enrichment/vulnerability-analysis.md).

# Vulnerability applicability

Netcap compares the software and versions it sees in traffic with the local NVD data and lists the CVEs that could apply. A listed CVE is a candidate: confirm the real version and configuration on the host before you act on it. A capture without software banners produces no vulnerability records.

## Run the check

```sh
net util -download-dbs
net capture -read traffic.pcap -out vulnerability-audit -dpi=false
```

Use the same `NC_CONFIG_ROOT` for the download and the capture. Keep `RELEASE_MANIFEST.json`, the installed database hash, the hash of the pcap and the capture version next to your findings. Updating the databases does not change an existing capture. Run the capture again to apply new data.

List the fields and read the records:

```sh
net dump -read vulnerability-audit/Software.ncap.gz -fields
net dump -read vulnerability-audit/Software.ncap.gz -json
net dump -read vulnerability-audit/Vulnerability.ncap.gz -fields
net dump -read vulnerability-audit/Vulnerability.ncap.gz -json
```

For a quick overview, print selected columns:

```sh
net dump -read vulnerability-audit/Software.ncap.gz -csv -select Product,Version,DetectionMethod,ConfidenceLevel
net dump -read vulnerability-audit/Vulnerability.ncap.gz -csv -select ObservedHost,ID,Severity,MatchStatus
```

## Example: an SSH banner

Your capture contains a server that answers with `SSH-2.0-OpenSSH_8.9p1`. Netcap records the product and version in `Software`, then lists CVEs whose affected range includes that version in `Vulnerability`.

OpenSSH 8.9p1 falls inside the range of CVE-2024-6387 ("regreSSHion", OpenSSH 8.5p1 up to 9.8p1). Many Linux distributions patch OpenSSH without changing the version string, so the banner alone cannot tell you whether this server is exposed. Check the installed package version on the host.

## Review a result

For each record, check:

* **Software and source.** Is the version from a parsed banner, a user-agent or another fingerprint? Does it belong to the right host?
* **`MatchStatus`.** It tells you whether the match used structured CPE data or only a text candidate. Record the value.
* **CPE conditions.** Are the OS, edition and target conditions met, unknown or contradicted?
* **Version bounds.** Are the bounds inclusive or exclusive? Can Netcap order the observed version without guessing what its suffix means?
* **Reference links.** What does the advisory say about configuration and fixes?

Conditions that Netcap cannot evaluate stay marked as unknown. A missing row can mean that no software was identified, that enrichment was off or that the database has no entry. The [matching rules](https://github.com/dreadl0ck/netcap/blob/master/internal/vulndb/SCHEMA.md#queries) describe how structured CPE matching differs from text and version search.

## Browser and MCP

In the web UI, open Software, then Vulnerabilities, and follow the links to the host and the supporting records. The MCP tools `list_software` and `list_vulnerabilities` show the same local data. Their arguments are in the [tool reference](https://docs.netcap.io/integrations-and-operations/tools.md). `lookup_cve` queries NVD over the network and needs `-allow-fetch`. It does not check whether the CVE applies to your capture.

The UI looks up references in the database installed today, not the one you had at capture time, so note the database date in exported reports. Community databases do not include Exploit-DB, so the exploit table is empty.

## Report the result

Write down the software and version, the host, the source record, the capture time, the match status, the open conditions, the advisory revision and what you verified on the host. A CVSS score says nothing about whether a host was compromised.
