Keyboard shortcuts

Press ← or → to navigate between chapters

Press S or / to search in the book

Press ? to show this help

Press Esc to hide this help

Findings and CVE hints

Findings are derived from what a scan collected, so run it with --services (or --deep). They work on stored snapshots and never send traffic.

network-scope-cli findings ID --min-severity low

The desktop shows them in the Findings window (sortable, filterable by severity and text). Severities: info, low, medium, high, critical. Every finding has a page in the Finding reference that explains it in plain language, states exactly what the tool looked at and how to fix it.

Checks

  • Certificates: expired, not yet valid, soon expiring, self-signed, weak signature hashes, short RSA keys.
  • TLS: SSLv3, TLS 1.0/1.1; RC4/DES/3DES/export/anonymous suites; missing forward secrecy.
  • SSH: weak and legacy algorithms (including Terrapin, CVE-2023-48795), SSH protocol 1.
  • Cleartext and unauthenticated services: Telnet, FTP, VNC, cleartext mail, unauthenticated Redis/memcached/MQTT, HTTP Basic over plain HTTP, exposed Docker API, public SNMP.
  • Windows services: RDP without NLA, SMBv1, unsigned SMB, SMB without encryption, LDAP anonymous bind.
  • Industrial ports reachable from the scanner (ot-reachable).
  • PHP end of life, date-aware (table PHP_EOL in risk.rs; branches not in the table are never flagged).

Some findings carry an optional reference: a link to official documentation on the problem and how to fix it. Currently smb1-enabled and smb-signing (Microsoft Learn), rdp-no-nla (Microsoft Learn), telnet-open (CISA) and the weak-TLS rules tls-sslv3, tls-deprecated-protocol, tls-broken-cipher, tls-3des, tls-no-pfs, tls-weak-signature and tls-weak-key (Mozilla Server Side TLS). The link appears in the HTML report, in a Reference column of the Markdown summary, as reference in the JSON and JSONL exports (omitted when a finding has none) and in the Findings window. Only HTTPS links are shown. Exports written before this field existed still load.

CVE hints

CVE entries are version-based hints only. Distributions backport fixes without changing the version string, so confirm with the vendor advisory or an authenticated check. Network Scope is not a vulnerability scanner.

The rules live in data/cves.json (built in). A user file merges like probes.json: %LOCALAPPDATA%/NetworkScope/cves.json (or $XDG_CONFIG_HOME/NetworkScope/cves.json), or --cves FILE on any command, or the CVE rules file field in the GUI Settings (with a Browse button; the path is kept with the preferences and, like --cves FILE, replaces the default user file). A rule or CPE entry with the same id replaces the built-in one. In the GUI the file is loaded at start-up and when the field is changed; if it cannot be read or parsed, the error is shown under the field and the previous rules stay active.

Rule fields:

FieldMeaning
idRule id
productLower-case substring of the detected product (svc.<port>.product or the HTTP Server header name)
excludeOptional product substrings the rule does not apply to
min / maxOptional inclusive / exclusive dotted versions with optional pN (8.5p1)
severityinfo, low, medium, high, critical
cveList of CVE-YYYY-NNNN; the finding id is cve-<first cve>
titleFinding title

A broken file stops the command with a message naming the file and rule. A broken user file found at start-up is reported (CLI: stderr, desktop: error line) and the built-in rules are used.

Known exploited and EPSS (offline feeds)

Findings that carry CVE ids can be enriched with two public data sets, so the list shows what is being exploited right now instead of only what is severe on paper:

  • CISA KEV, the Known Exploited Vulnerabilities catalog: CVEs with evidence of exploitation in the wild.
  • FIRST EPSS, the Exploit Prediction Scoring System: a daily probability (0 to 1) that a CVE is exploited in the next 30 days, with a percentile.

Network Scope never downloads them. You fetch the two files yourself, on a machine that is allowed to, and import them from disk:

curl -L -o kev.json https://www.cisa.gov/sites/default/files/feeds/known_exploited_vulnerabilities.json
curl -L -o epss_scores-current.csv.gz https://epss.empiricalsecurity.com/epss_scores-current.csv.gz
gunzip epss_scores-current.csv.gz        # the importer reads plain CSV only
network-scope-cli feeds import --kev kev.json --epss epss_scores-current.csv
network-scope-cli feeds status

Either option may be given alone; the part not imported keeps its previous content. Repeat the import to refresh (EPSS changes daily, KEV several times a week). A file that cannot be parsed is rejected and the cache stays as it was. Gzip is not read directly because the project avoids extra dependencies; the importer detects a .gz file and says so.

Cache. The import writes feeds.json next to the user cves.json: %LOCALAPPDATA%/NetworkScope/feeds.json, or $XDG_CONFIG_HOME/NetworkScope/feeds.json; --feeds FILE selects another file for any command. It is a global lookup table, not part of a scan, so it is a file and not part of the SQLite inventory (--db is per inventory and would otherwise need one copy per database). It holds the KEV entries (date added, ransomware use) and about 300,000 EPSS scores kept with five decimals, roughly 10 MB. Saved scans are not modified: the data is looked up when findings are computed, so older scans also show current feed data.

What changes.

  • findings, export --format json and the other JSON output gain the optional fields kev, kev_added, kev_ransomware, epss and epss_percentile (highest values over the finding’s CVEs) on findings that match. Without an imported cache these fields are absent and the output is identical to before; exports written earlier still load.
  • Findings are ranked by in KEV first, then severity, then EPSS, then host, port and id. Without a cache the order is the usual severity order. findings ID --sort severity restores the usual order even with feeds; --sort exploited is the default.
  • The HTML report shows a “Known exploited” badge (with the date CISA added it and “Ransomware use” where KEV says so) and “EPSS NN %” next to the CVE links.

Limits. KEV and EPSS describe a CVE, not your host: a version-based hint that matches a known exploited CVE is still only a hint (see above). EPSS is a statistical estimate, not a prediction for one device. The desktop Findings window does not show these fields yet. Importing the NVD feed is a separate roadmap item and is not part of this.

Sources and terms: KEV is published by the US government (CISA); EPSS is published free of charge by the EPSS Special Interest Group at FIRST. See data/README.md. The EPSS download address was checked on FIRST’s data page (first.org/epss/data) on 2026-11-19.

CPE names

cpe entries (id, exact lower-case products, template with {version}, {base}, {update}) produce svc.<port>.cpe such as cpe:2.3:a:openbsd:openssh:7.4:p1:*:*:*:*:*:*; distribution suffixes are dropped. The CPE vendor/product names were written from memory of the NVD dictionary and have not been checked against it; spot-check them before relying on them.

Contributing rules

New CVE rules are welcome. Keep them version-based, cite the CVE ids, and add a test for the version boundaries. See CONTRIBUTING.md.