Skip to content

v0.5.0 — Accurate CVE matching

Latest

Choose a tag to compare

@TheSecuredAnalyst TheSecuredAnalyst released this 13 Oct 13:41
· 1 commit to main since this release
5c5523e

Accurate CVE matching

SecSuite's network scanner used to report CVEs for the wrong products. v0.5.0 fixes that at the source.

Before: an authorised scan of a production Ubuntu server reported 20 CVE matches, several at CVSS 10.0. None of them applied. They were for Authelia, zzcms, Pulpcore, NGINX Unit, WordPress plugins and UPnP routers, or for nginx and OpenSSH versions fixed years ago.

After: the same scan reports 7 matches, all for the software actually running.

Fixed

  • CVE lookup checks affected products and versions. NVD keyword search matches any CVE whose description mentions a product. Each result is now checked against its CPE configuration, NVD's own list of affected products and version ranges, and different-product or out-of-range matches are dropped. For recent CVEs that don't have CPE data yet, a match is kept only when the product is the subject of the description. Version comparison understands patch suffixes such as OpenSSH 9.6p1.
  • Port-number guesses no longer trigger CVE lookups. When nmap can't fingerprint a service, it names it after the port (5000 → upnp). Those names are now marked as guessed, skipped for CVE lookup, and labelled in the output.

Added

  • Native entity emission for scanners (#14). Scanners can emit their provenance graph directly; PortScanner is the first to do so.

Upgrading

No configuration changes. Expect fewer, more relevant CVE findings. If you relied on the old keyword results, review your saved scans: many of those findings were false.

Full changelog: v0.4.0...v0.5.0