CyberKit

Common Vulnerabilities and Exposures

Also called CVE.

The universal ID scheme that assigns a unique identifier to each public vulnerability.

What it is

A program, run by MITRE under U.S. government sponsorship, that assigns a unique identifier (such as CVE-2024-12345) to each publicly disclosed security flaw. A CVE entry is a stable reference, not a severity rating or a fix.

Why it matters

CVE IDs give the whole industry one common name for a vulnerability, so advisories, scanners, patches, and threat reports can all point at the same flaw without ambiguity, which is what makes coordinated vulnerability handling possible.

In practice

Tracking remediation of a specific CVE across scanners and vendor advisories because every tool references the same identifier.

What to look for

  • CVE IDs on affected products and versions.
  • Records marked rejected or disputed.
  • Vendor advisories that map to the CVE.

Common mistake

Treating a CVE ID as a risk rating. It only names the flaw.

Use it in CyberKit

In the field

Well-known tools where this shows up on the job. They are listed to show the landscape, not as a recommendation.

  • Nessus Commercial

    A vulnerability scanner that checks hosts for known flaws and missing patches.

  • Qualys VMDR Commercial

    A cloud platform that scans assets and ranks vulnerabilities for patching.

  • OpenVAS Open source

    An open source vulnerability scanner with a large set of checks.

  • Nuclei Open source

    Runs community templates that test for specific, newly published flaws.

Read next

Sources