Professor Franklin
Accessibility settings

Preferences are saved in this browser when storage is available.

Chapter 5 · Reading 3 of 5

Understanding CVSS and CVEs

Security+ SY0-801 · Objectives 4.3

A dispatcher hears that the portal is affected by a “critical CVE.” That phrase combines two pieces of information and leaves out a third. Which issue is it, how severe are its technical consequences, and can those consequences occur in this deployment?

Read the identifier before reading the score

A CVE ID names a vulnerability so a supplier advisory, inventory finding and remediation ticket can refer to the same issue. Its syntax is CVE-YYYY- followed by four or more decimal digits. Preserve leading zeros. Both CVE-2014-0160 and CVE-2021-44228 are valid examples. The year can reflect reservation or public disclosure. Read the record and advisory for actual publication and remediation dates. The suffix carries no severity information.

CISA sponsors the CVE Program. MITRE operates the Secretariat and supports program infrastructure. Participating CVE Numbering Authorities (CNAs) assign identifiers and publish records within their scopes. The program’s November 2026 report counted 568 CNAs plus three CNAs of Last Resort. A reserved ID may have no public technical description yet. A rejected record remains visible so consumers can correct old references. Check the record state, affected versions and vendor references before assigning work. CVE Program partner report

Read a CVSS v4.0 vector

FIRST’s Common Vulnerability Scoring System expresses severity. Keep the version, vector, source and assessment date with the number. Consider this illustrative Base vector.

CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

Attack Vector describes required proximity. Attack Complexity describes the need to overcome security-enhancing conditions. Attack Requirements identifies prerequisite deployment or execution conditions, such as a specific race condition. Here AV:N means network reach, AC:L means low complexity and AT:P means a prerequisite is present. PR:N requires no prior privileges. User Interaction distinguishes None, Passive and Active. UI:P indicates limited, involuntary interaction by someone other than the attacker.

Version 4.0 removed the Scope metric. Score confidentiality, integrity and availability separately on the vulnerable system (VC, VI, VA) and subsequent systems (SC, SI, SA). Here only the vulnerable system’s confidentiality has high impact. Establish the system boundary and trace actual consequences before assigning downstream impact. A network dependency alone does not establish harm.

From severity to a remediation queue

Base represents intrinsic characteristics. Threat adds Exploit Maturity (E). Environmental metrics express local security requirements and modified characteristics. Supplemental metrics describe Safety, Automatable, Recovery, Value Density, Response Effort and Provider Urgency without changing the numeric score. Report the groups used as CVSS-B, CVSS-BT, CVSS-BE or CVSS-BTE. Use the v4.0 calculator for the numeric result. Arithmetic averages of the individual metrics give misleading answers. FIRST specification · CVSS v4.0 calculator

In triage, compare the affected version with the deployed build, check reachability and look for credible exploitation evidence. Record the business owner, temporary protection, remediation deadline and verification test. Two installations can share an identifier and Base vector while needing different response times.

What the owner needs at the maintenance meeting

Bring the advisory, an inventory record and a short explanation of the relevant deployment conditions. If a vendor has supplied a fixed build, record how your team will identify that build in the running service. If the owner proposes temporary isolation, specify the business traffic that must continue and how the team will verify the boundary. Keep the versioned severity vector with the ticket so a later reviewer can understand the original assessment. The resulting decision remains intelligible even if threat activity or service exposure changes.

Severity versus reach

Inspect the three records, then use the evidence to answer the question.

1. CVE

Identifies a disclosed vulnerability.

A / base score 9.8 / service disabled

2. CVSS

Describes its technical severity.

B / base score 8.1 / exposed and actively targeted

3. Local priority

Adds asset criticality and exposure.

Both findings have vendor fixes

Apply the reading

Two assets share one CVE and severity score. Why might their remediation deadlines differ?

Compare your reasoning

One may be publicly reachable or support a critical service. Document those environmental differences alongside the identifier and score.