CVSS v3.1 Base Metrics
What you'll learn: How CVSS base metrics quantify vulnerability severity through exploitability and impact dimensions.
Understanding Base Metrics
CVSS v3.1 (Common Vulnerability Scoring System) base metrics measure the intrinsic, unchanging characteristics of a vulnerability. Think of them as a vulnerability's "DNA"—they describe fundamental properties that don't change based on your environment or over time.
The base metrics divide into two categories:
Exploitability Metrics
These answer: "How easy is it to exploit this vulnerability?"
- Attack Vector (AV): Where must the attacker be? (Network, Adjacent, Local, Physical)
- Attack Complexity (AC): Are special conditions required? (Low/High)
- Privileges Required (PR): Does the attacker need existing access? (None, Low, High)
- User Interaction (UI): Must a user do something? (None/Required)
Impact Metrics
These answer: "What damage occurs if exploited?"
- Confidentiality (C): Is data exposed? (None, Low, High)
- Integrity (I): Can data be modified? (None, Low, High)
- Availability (A): Are services disrupted? (None, Low, High)
Plus one overarching metric:
- Scope (S): Does impact extend beyond the vulnerable component? (Unchanged/Changed)
Real-World Application
A remotely exploitable web vulnerability (AV:Network) requiring no authentication (PR:None) with no user interaction (UI:None) and high confidentiality impact (C:High) scores significantly higher than a local vulnerability requiring admin privileges. These metrics combine algorithmically to produce the familiar 0-10 CVSS score.
Key Takeaway: CVSS base metrics provide standardized, objective measurement of vulnerability severity by separately quantifying how easily a flaw can be exploited and what damage results—enabling consistent risk prioritization across your vulnerability management program.