Reading CVE records and CVSS vectors
What a CVE record does and does not contain, who writes it, and how to read CVSS v3.1 and v4.0 vector strings metric by metric, so you can judge a score instead of copying it, and adjust it for your environment.
01What a CVE record is
- Read a CVE record: description, affected versions, references, CWE and scores
- Decode a CVSS v3.1 vector and see why a score is what it is
- Read the CVSS v4.0 changes: attack requirements, subsequent systems, threat and environmental groups
- Know why a base score is not risk, and what to add
A CVE (Common Vulnerabilities and Exposures) ID is a name for one publicly disclosed vulnerability, such as CVE-2024-3400. IDs are assigned by CNAs (CVE Numbering Authorities): vendors like Microsoft or Palo Alto Networks for their own products, plus coordinators such as MITRE and CERT/CC. The CNA writes the record; downstream databases such as the US NVD (National Vulnerability Database) and vendors' own advisories add analysis on top.
| Part of the record | What it tells you | Watch out for |
|---|---|---|
| Description | The flaw, the component and the impact in one or two sentences | Vague wording such as "may allow" hides whether exploitation is remote or needs authentication |
| Affected products and versions | Which versions are vulnerable and where the fix starts | Version ranges are often incomplete early on; the vendor advisory is authoritative |
| References | Vendor advisory, patch, write-ups, sometimes exploit code | The vendor advisory usually carries workarounds and detection guidance the record lacks |
| CWE | The weakness class, for example CWE-78 OS command injection | Useful for trends; says nothing about exploitability |
| CVSS | Severity vectors from the CNA, NVD or CISA's ADP container | Different sources can score the same CVE differently; record which one you used |
| State | Published, Reserved or Rejected | A Reserved ID with no details is common during coordinated disclosure |
Since early 2024 NVD has had a large backlog of unanalysed CVEs, so many records carry only the CNA's score, or none. CISA's Vulnrichment programme adds CVSS, CWE and SSVC data to many records through the ADP container. Build your process so a missing NVD score does not mean a missing priority.
02CVSS v3.1, metric by metric
CVSS (Common Vulnerability Scoring System, maintained by FIRST) scores the severity of a vulnerability from 0.0 to 10.0. The vector string is more useful than the number, because it shows the reasoning. In v3.1 the base metrics describe exploitability (how hard it is to attack) and impact (what an attacker gets).
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H -> 9.8 Critical
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H -> 10.0 Critical
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H -> 8.8 High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H -> 7.8 High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N -> 6.1 Medium (typical reflected XSS)| Metric | Values | Plain reading |
|---|---|---|
| AV Attack Vector | N network, A adjacent, L local, P physical | Where the attacker must be. N means over the internet if the service is exposed |
| AC Attack Complexity | L low, H high | Does success depend on conditions outside the attacker's control (a race, a specific configuration)? |
| PR Privileges Required | N none, L low, H high | Does the attacker need an account first? |
| UI User Interaction | N none, R required | Does a victim have to click or open something? |
| S Scope | U unchanged, C changed | Can the impact reach beyond the vulnerable component, such as a VM escape or XSS reaching the browser? |
| C / I / A | H high, L low, N none | Confidentiality, integrity and availability impact |
Severity bands are the same in v3.1 and v4.0: 0.1-3.9 Low, 4.0-6.9 Medium, 7.0-8.9 High, 9.0-10.0 Critical. Read the vector first: AV:N/PR:N/UI:N (remote, unauthenticated, no click) is the shape of mass exploitation, whatever the impact metrics say. AV:L means the attacker already needs code execution on the box, which makes it a privilege-escalation step, not a front door.
CVSS base scores assume a reasonable worst-case deployment. A 9.8 in a library you ship but never call, or on a server with no network path from anywhere untrusted, is not a 9.8 for you. That is what the temporal or threat metrics and the environmental metrics are for, and most tools ignore them.
03What changed in CVSS v4.0
CVSS v4.0 was published by FIRST in November 2023. It keeps the 0 to 10 scale but restructures the metrics and, importantly, names scores by which groups were used, so nobody mistakes a base score for a risk score.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N -> 9.3 (CVSS-B)
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:U -> lower (CVSS-BT): no known exploitation or PoC
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:H/VI:L/VA:N/SC:L/SI:L/SA:N -> needs attack requirements and passive user interaction| Change | v3.1 | v4.0 |
|---|---|---|
| Attack conditions | AC folds everything into low or high | AC (defences the attacker must bypass) plus new AT Attack Requirements (deployment conditions such as a race or a non-default setting) |
| User interaction | N or R | N, P passive (victim just views something), A active (victim must take specific steps) |
| Scope | S:U or S:C | Removed. Impact is split into the vulnerable system (VC/VI/VA) and subsequent systems (SC/SI/SA) |
| Temporal / threat | Exploit maturity, remediation level, report confidence | Only E Exploit Maturity: Attacked, POC, Unreported |
| Supplemental | None | Safety, Automatable, Recovery, Value Density, Response Effort, Provider Urgency: context that does not change the score |
| Naming | One number called the CVSS score | CVSS-B base, CVSS-BT base and threat, CVSS-BE base and environmental, CVSS-BTE all three |
The E metric in v4.0 is the one most worth filling in yourself, because it pulls threat intelligence into the number: E:A (attacked) leaves the score as high as it goes, while E:U (no known exploitation or proof of concept) brings it down. Feed it from the KEV catalogue and EPSS, covered in the next lessons. The environmental group lets you raise or lower the required confidentiality, integrity and availability for the specific asset.
04From record to advisory to your estate
The CVE record names the problem; the vendor advisory tells you what to do. For every vulnerability you triage, collect the same few facts so the decision is repeatable.
cve: CVE-2024-3400
product: Palo Alto Networks PAN-OS GlobalProtect
weakness: CWE-77 command injection (via arbitrary file creation)
vector_cna: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:A # 10.0 in the vendor advisory
affected: specific PAN-OS 10.2, 11.0 and 11.1 releases with GlobalProtect gateway or portal configured
fixed_in: hotfix releases listed in the vendor advisory
workaround: vendor threat prevention signature (where subscribed); configuration-based mitigation was later withdrawn as ineffective
exploited: yes; listed in CISA KEV in April 2024
our_exposure: 2 internet-facing firewalls run 11.1 with GlobalProtect portal enabled
decision: emergency change, patch within 24h, hunt for indicators from the vendor advisory- Configuration matters: CVE-2024-3400 affected firewalls only with GlobalProtect configured. A version match without the vulnerable feature enabled is a lower priority, but confirm the configuration, do not assume it.
- Workarounds change: vendors revise mitigations as they learn more. Re-read the advisory when you schedule the change, not only when you first triage.
- Scanners match versions, not configurations: expect false positives (backported fixes on Linux distributions) and false negatives (software installed outside the package manager).
A scanner reports a 9.8 (`AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`) on a library inside an internal batch application that has no network listener. What is the right next step?
05Putting it into practice
"I read the vector before the number: network-reachable, no privileges, no user interaction is the shape of mass exploitation. Then I check the vendor advisory for affected configurations and workarounds, add threat context, and adjust for the asset. In v4.0 that is the difference between a CVSS-B score from the CNA and a CVSS-BTE score that reflects us."
Expect to decode a vector string aloud and explain why a 9.8 might not be your top priority. Knowing that v4.0 dropped Scope for subsequent-system impacts, added Attack Requirements, and labels scores B, BT, BE and BTE shows you have kept up.
Q1Why do CNA and NVD scores differ?+
They score from different information and assumptions. The CNA knows the product; NVD often has only the public description. Record which source you used and prefer the one with the clearer rationale.
Q2What is CWE useful for in triage?+
Mostly trends and root-cause work: if half your findings are CWE-79 or CWE-89, invest in framework-level fixes. It does not change the priority of one finding.
Q3What does a Rejected CVE mean?+
The ID was withdrawn: a duplicate, not a vulnerability, or never used. Scanners occasionally keep reporting rejected IDs; close them with a note.