Skip to main content
Be Bitwise

The CVE Process & CVSS Scoring

Responsible Disclosure & UK Law · Zero-Day Research track

6 min read

In this module

What Is a CVE?

A CVE (Common Vulnerabilities and Exposures) is a unique identifier for a publicly known vulnerability. MITRE maintains the system, and it functions as the shared reference language for vulnerability management. When an advisory, a patch note, or a news article mentions a flaw, the CVE ID is what anchors everyone to the same specific issue.

CVE identifiers follow the format CVE-YYYY-NNNN+, where YYYY is the year the ID was assigned (not necessarily the year the vulnerability was discovered or published) and NNNN is a sequential number with at least four digits (expanding to five or more when needed):

c
CVE-2024-12345
CVE-2021-44228 (Log4Shell)
CVE-2014-0160 (Heartbleed)

A CVE entry holds a description, references to advisories and patches, and the affected software. No exploit code, no deep technical write-up — it's a catalogue entry, a pointer, not the full story.

The CNA Hierarchy

CVE IDs are not all assigned by MITRE directly. The CVE Programme operates through a federated system of CVE Numbering Authorities (CNAs) - organisations authorised to assign CVE IDs to vulnerabilities within their defined scope.

The hierarchy has three working tiers:

  • Top-Level Roots: MITRE and CISA. Each oversees a set of Roots and CNAs, and handles disputes and escalations that can't be settled lower down. MITRE also acts as the CNA of Last Resort, assigning IDs when no other CNA's scope covers a vulnerability.
  • Roots: Organisations that recruit, train and manage CNAs in a region or sector. JPCERT/CC (Japan), INCIBE (Spain) and Red Hat are Roots under MITRE; CISA ICS is a Root under CISA.
  • CNAs: Organisations that assign CVE IDs for vulnerabilities in their own products or within their defined scope. Major vendors like Microsoft, Google, Apple, and Red Hat are CNAs for their own software, and a single organisation can hold more than one role.

Requesting a CVE as an Individual Researcher

If you discover a vulnerability and want a CVE assigned, follow this process:

  1. Check for an existing CVE. Search the CVE database at cve.org to ensure the vulnerability has not already been catalogued.
  2. Determine whether the vendor is a CNA. If the affected vendor is a CNA (most large software companies are), report the vulnerability directly to them. They will assign a CVE as part of their response process.
  3. If no CNA covers the product, submit a request through the CVE request form at cveform.mitre.org. You will need to provide the affected product, version, vulnerability type, and a description of the impact.
  4. Wait for processing. CVE assignment typically takes approximately 30 days, though complex or disputed cases may take longer.
Who Assigns the CVE?

Always report to the vendor first if they are a CNA. The vendor assigns the CVE as part of their coordinated response. Only use cveform.mitre.org when the vendor is not a CNA, is unresponsive, or the product falls outside any existing CNA's scope. MITRE acts as the authority of last resort, not the first point of contact.

CVSS v4.0

The Common Vulnerability Scoring System (CVSS) provides a standardised method for rating the severity of vulnerabilities. Version 4.0 was released in November 2023 by FIRST (the Forum of Incident Response and Security Teams) and introduces significant improvements over v3.1.

CVSS v4.0 organises metrics into four groups:

Base Metrics

These capture the intrinsic characteristics of a vulnerability that do not change over time or across environments.

Exploitability metrics:

MetricDescription
Attack Vector (AV)How the attacker reaches the vulnerable component: Network, Adjacent, Local, or Physical
Attack Complexity (AC)Conditions beyond the attacker's control that must exist: Low or High
Attack Requirements (AT)New in v4.0. Prerequisites for the attack, such as specific configurations or race conditions: None or Present
Privileges Required (PR)Level of access needed before exploitation: None, Low, or High
User Interaction (UI)Expanded in v4.0. Whether a user must take action: None, Passive (the user is exposed without active involvement), or Active (the user must perform a specific action)

Impact metrics are now split into two categories:

  • Vulnerable System Impact: Confidentiality, Integrity, and Availability impact on the system that contains the vulnerability.
  • Subsequent System Impact: Confidentiality, Integrity, and Availability impact on systems beyond the vulnerable component (e.g., a web server vulnerability that exposes a backend database).

Threat Metrics

Renamed from "Temporal" in v3.1, this group is simplified to a single metric:

  • Exploit Maturity: Reflects the current state of exploit techniques - Unreported, Proof-of-Concept, or Attacked.

Environmental Metrics

These allow organisations to customise the score based on their specific deployment. Environmental metrics are modified versions of the Base metrics, adjusted to reflect the importance of the affected system within a particular environment and any mitigations already in place.

Supplemental Metrics (New in v4.0)

These provide additional context that does not affect the numerical score but informs risk assessment:

MetricDescription
SafetyWhether exploitation could impact human safety
AutomatableWhether exploitation can be automated at scale
RecoveryHow well the system can recover after exploitation
Value DensityWhether the target contains concentrated high-value assets
Vulnerability Response EffortThe effort required to respond to the vulnerability
Provider UrgencyThe urgency rating assigned by the vendor

CVSS v4.0 Scoring Nomenclature

CVSS v4.0 introduces explicit notation to indicate which metric groups were used to produce a score:

NotationMeaning
CVSS-BBase metrics only
CVSS-BTBase + Threat metrics
CVSS-BEBase + Environmental metrics
CVSS-BTEBase + Threat + Environmental metrics

This makes it immediately clear how a score was calculated. A CVSS-B score of 9.1 means only base metrics were considered. A CVSS-BTE score of 7.3 for the same vulnerability means threat intelligence and environmental context were factored in, potentially lowering the score because, for example, no public exploit exists and the organisation has compensating controls.

CVSS Is Not a Risk Score

CVSS measures the technical severity of a vulnerability, not the risk it poses to your specific organisation. Risk depends on additional factors: the value of the asset, existing compensating controls, threat intelligence, and business context. A CVSS 10.0 vulnerability in a system that is air-gapped and handles no sensitive data may pose less organisational risk than a CVSS 7.0 flaw in a public-facing payment system. Use CVSS as one input to risk assessment, not as the final word.