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

Version-based CVE hint

Finding idcve-cve-YYYY-NNNN, for example cve-cve-2021-41773
SeverityAs set by the rule (Info to Critical)
Applies toAny service whose product and version were detected

What it means

The detected product and version match a rule from the CVE list that ships with the program (or your own list), which names a known vulnerability in that version range. The finding id is cve- followed by the first CVE id of the rule in lower case, which is why it reads cve-cve-.... The title is the one given by the rule.

Why it matters

Old versions of software often contain flaws with public exploits. The finding points you to the version that should be checked. It is a hint, not a confirmed vulnerability.

How it is detected

For each open port, the tool takes the product and version from the service banner (and, for web servers, the Server header) and compares them with the rules in data/cves.json (plus a user file, see Findings and CVE hints). A rule matches when its product text occurs in the detected product, the product is not on the rule’s exclusion list, and the version lies in the rule’s range. Each CVE is reported once per port. Severity and title come from the rule. The evidence is “product version” followed by a note that this is a version-based hint only.

The SMBGhost hint (cve-cve-2020-0796) and the Heartbleed hint (heartbleed) are separate, built-in rules with their own pages.

Possible false positives

  • Backports. Linux distributions and vendors fix flaws without changing the version number, so a patched system can still be flagged. The version text alone cannot settle this.
  • Version strings in banners can be missing, edited or from a different component.
  • The rule may not apply to the way the software is configured (a vulnerable module that is not loaded).

How to fix

  • Check the vendor advisory for the CVE and your product (the NVD entry links to it).
  • On Linux look at the package changelog (apt changelog PACKAGE, rpm -q --changelog PACKAGE) or the distribution’s security tracker to see whether the fix is included in your package version.
  • Update to a fixed release, or apply the vendor’s mitigation, and re-scan.
  • Embedded and industrial devices: ask the vendor for a fixed firmware and a statement whether your model is affected; apply in a planned change window.
  • The finding goes away when the detected version leaves the rule’s range. If you confirmed that the vendor backported the fix, the version text does not change and the finding stays; keep the result of your check as the record.

References

All findings