OSCP Report Writing: Vulnerability Severity Rating (CVSS Scoring)
1. What is CVSS?
Overview
CVSS (Common Vulnerability Scoring System) is the industry-standard framework for rating the severity of software vulnerabilities. It provides a consistent, quantitative way to communicate the severity of vulnerabilities across organizations, tools, and teams.
- Current version: CVSS v3.1 (v4.0 is available but v3.1 remains the standard for most reporting)
- Score range: 0.0 (None) to 10.0 (Critical)
- Maintained by: FIRST (Forum of Incident Response and Security Teams)
- Official website: https://www.first.org/cvss/
Why CVSS Matters for OSCP
- The OSCP report requires CVSS scores for each finding
- Consistent scoring demonstrates professional competence
- CVSS scores drive remediation prioritization
- Incorrect scoring can mislead stakeholders about risk
2. Severity Rating Scale
Standard Severity Bands
| Score Range | Severity | Color | Response Time | OSCP Context |
|---|---|---|---|---|
| 9.0 - 10.0 | Critical | Red | Immediate (24-48 hours) | RCE, full system compromise, domain admin access |
| 7.0 - 8.9 | High | Orange | Within 1 week | Local privilege escalation, authentication bypass, significant data exposure |
| 4.0 - 6.9 | Medium | Yellow | Within 1 month | XSS, information disclosure, misconfigurations |
| 0.1 - 3.9 | Low | Green | Within 3 months | Missing headers, verbose errors, minor issues |
| 0.0 | None | Gray | As scheduled | Informational findings, best practice recommendations |
Visual Severity Indicator
Critical ████████████████████ 9.0-10.0 RED
High ██████████████ 7.0-8.9 ORANGE
Medium ██████████ 4.0-6.9 YELLOW
Low ████ 0.1-3.9 GREEN
None 0.0 GRAY
3. CVSS v3.1 Metric Groups
CVSS v3.1 consists of three metric groups that contribute to the final score:
CVSS v3.1 Score
├── Base Metrics (Required - core severity)
│ ├── Attack Vector (AV)
│ ├── Attack Complexity (AC)
│ ├── Privileges Required (PR)
│ ├── User Interaction (UI)
│ ├── Scope (S)
│ ├── Confidentiality (C)
│ ├── Integrity (I)
│ └── Availability (A)
├── Temporal Metrics (Optional - time-sensitive)
│ ├── Exploit Code Maturity (E)
│ ├── Remediation Level (RL)
│ └── Report Confidence (RC)
└── Environmental Metrics (Optional - context-specific)
├── Confidentiality Requirement (CR)
├── Integrity Requirement (IR)
└── Availability Requirement (AR)
4. Base Metrics (Required)
The Base metrics represent the intrinsic characteristics of a vulnerability that are constant over time and across user environments. These are the most important metrics for OSCP reporting.
Attack Vector (AV)
Describes how the vulnerability is exploited.
| Value | Abbreviation | Description | Score Impact |
|---|---|---|---|
| Network | N | The vulnerability can be exploited remotely over a network | Highest impact |
| Adjacent | A | The attack requires access to the local network segment | High impact |
| Local | L | The attack requires local access (physical or console) | Medium impact |
| Physical | P | The attack requires physical access to the target | Lowest impact |
Examples:
- Web application SQL injection: AV:N (Network)
- Local privilege escalation: AV:L (Local)
- USB-based attack: AV:P (Physical)
- Wi-Fi deauthentication attack: AV:A (Adjacent)
Attack Complexity (AC)
Describes the conditions beyond the attacker’s control that must exist to exploit the vulnerability.
| Value | Abbreviation | Description | Score Impact |
|---|---|---|---|
| Low | L | Exploitation is straightforward, no special conditions required | Higher score |
| High | H | Exploitation requires specific conditions (race conditions, specific environment) | Lower score |
Examples:
- SQL injection with simple payload: AC:L (Low)
- Race condition requiring precise timing: AC:H (High)
- Buffer overflow with public exploit: AC:L (Low)
- Exploit requiring specific user activity: AC:H (High)
Privileges Required (PR)
Describes the level of privileges an attacker must have before exploiting the vulnerability.
| Value | Abbreviation | Description | Score Impact |
|---|---|---|---|
| None | N | No authentication required | Highest impact |
| Low | L | Requires authentication with low-impact privileges (regular user) | Medium impact |
| High | H | Requires authentication with high-impact privileges (admin) | Lower impact |
Examples:
- Unauthenticated RCE: PR:N (None)
- Authenticated SQL injection: PR:L (Low)
- Admin-only configuration change: PR:H (High)
- Public-facing login bypass: PR:N (None)
User Interaction (UI)
Describes whether the attack requires action from a user.
| Value | Abbreviation | Description | Score Impact |
|---|---|---|---|
| None | N | No user interaction required | Higher score |
| Required | R | Requires a user to perform some action (click link, open file) | Lower score |
Examples:
- Automated SQL injection: UI:N (None)
- Phishing-based XSS: UI:R (Required)
- Drive-by download exploit: UI:R (Required)
- Background service exploitation: UI:N (None)
Scope (S)
Describes whether the vulnerability can affect resources beyond the authorization intent.
| Value | Abbreviation | Description | Score Impact |
|---|---|---|---|
| Unchanged | U | The impact is limited to the vulnerable component | Lower score |
| Changed | C | The impact affects other components or systems | Higher score |
Examples:
- SQL injection affecting only the database: S:U (Unchanged)
- XSS that compromises the entire browser session: S:C (Changed)
- Privilege escalation from user to root: S:C (Changed)
- Buffer overflow crashing only the vulnerable service: S:U (Unchanged)
Impact Metrics (CIA Triad)
The Confidentiality, Integrity, and Availability metrics describe the impact of the vulnerability.
| Metric | Values | Description |
|---|---|---|
| Confidentiality (C) | N / L / H | Impact on data confidentiality |
| Integrity (I) | N / L / H | Impact on data integrity |
| Availability (A) | N / L / H | Impact on system availability |
Value Meanings:
- None (N): No impact
- Low (L): Some impact, but limited
- High (H): Complete impact (full data exposure, full data modification, complete system downtime)
Examples:
- SQL injection extracting all data: C:H, I:H, A:N
- Denial of service: C:N, I:N, A:H
- XSS stealing session cookie: C:L, I:L, A:N
- RCE with full system control: C:H, I:H, A:H
5. CVSS Vector String Format
Vector String Structure
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Vector String Abbreviations Reference
| Abbreviation | Full Name | Metric Group |
|---|---|---|
| AV:N | Attack Vector: Network | Base |
| AV:A | Attack Vector: Adjacent | Base |
| AV:L | Attack Vector: Local | Base |
| AV:P | Attack Vector: Physical | Base |
| AC:L | Attack Complexity: Low | Base |
| AC:H | Attack Complexity: High | Base |
| PR:N | Privileges Required: None | Base |
| PR:L | Privileges Required: Low | Base |
| PR:H | Privileges Required: High | Base |
| UI:N | User Interaction: None | Base |
| UI:R | User Interaction: Required | Base |
| S:U | Scope: Unchanged | Base |
| S:C | Scope: Changed | Base |
| C:N | Confidentiality: None | Impact |
| C:L | Confidentiality: Low | Impact |
| C:H | Confidentiality: High | Impact |
| I:N | Integrity: None | Impact |
| I:L | Integrity: Low | Impact |
| I:H | Integrity: High | Impact |
| A:N | Availability: None | Impact |
| A:L | Availability: Low | Impact |
| A:H | Availability: High | Impact |
6. CVSS Vector Examples
Common Vulnerability Scenarios
| Vulnerability | CVSS Vector | Score | Severity |
|---|---|---|---|
| Remote SQL Injection (unauthenticated) | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
9.8 | Critical |
| Remote Code Execution (unauthenticated) | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H |
10.0 | Critical |
| Authenticated SQL Injection | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N |
8.1 | High |
| Local Privilege Escalation | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
7.8 | High |
| Reflected XSS (requires click) | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N |
6.1 | Medium |
| Stored XSS (no interaction) | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N |
7.1 | High |
| Information Disclosure | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N |
5.3 | Medium |
| Brute Force (no rate limiting) | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H |
8.1 | High |
| Default Credentials | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
9.8 | Critical |
| Open Port (no known exploit) | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:N |
0.0 | None |
OSCP-Relevant Examples
| OSCP exam, you will commonly encounter these scenarios:
| OSCP Scenario | CVSS Vector | Score | Severity |
|---|---|---|---|
| Exploiting Apache Struts RCE | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H |
10.0 | Critical |
| Exploiting Exchange ProxyLogon | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H |
10.0 | Critical |
| Linux Kernel Privilege Escalation | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
7.8 | High |
| Windows Privilege Escalation (AlwaysInstallElevated) | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
7.8 | High |
| SSH Brute Force | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H |
8.1 | High |
| SMB Exploitation (EternalBlue) | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H |
8.8 | High |
| Web Shell Upload | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H |
9.0 | Critical |
| Credential Dumping (Mimikatz) | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N |
6.7 | Medium |
7. Temporal Metrics (Optional)
Temporal metrics reflect the current state of the vulnerability’s characteristics and exploit codes.
| Metric | Values | Description |
|---|---|---|
| Exploit Code Maturity (E) | X / P / H / P | Availability of exploit code |
| Remediation Level (RL) | X / O / T / W / U | Availability of remediation |
| Report Confidence (RC) | X / U / C | Confidence in the report |
Exploit Code Maturity (E)
| Value | Abbreviation | Description |
|---|---|---|
| Not Defined | X | No information available |
| Unproven | U | Exploit code exists but has not been demonstrated |
| Proof of Concept | P | Proof-of-concept code exists |
| Functional | F | Functional exploit code exists |
| High | H | Automated, reliable exploit code is widely available |
Remediation Level (RL)
| Value | Abbreviation | Description |
|---|---|---|
| Not Defined | X | No information available |
| Official Fix | O | Vendor-provided complete fix available |
| Temporary Fix | T | Vendor-provided workaround available |
| Workaround | W | Non-vendor workaround available |
| Unavailable | U | No fix or workaround available |
Report Confidence (RC)
| Value | Abbreviation | Description |
|---|---|---|
| Not Defined | X | No information available |
| Unconfirmed | U | Vulnerability is not yet verified |
| Uncorroborated | U | Vulnerability is verified but not confirmed by a third party |
| Confirmed | C | Vulnerability is confirmed by a third party |
8. Environmental Metrics (Optional)
Environmental metrics allow customization of the CVSS score based on the specific environment.
| Metric | Values | Description |
|---|---|---|
| Confidentiality Requirement (CR) | X / H / M | Importance of confidentiality to this user |
| Integrity Requirement (IR) | X / H / M | Importance of integrity to this user |
| Availability Requirement (AR) | X / H / M | Importance of availability to this user |
Note: Environmental metrics are rarely used in OSCP reporting. Focus on Base metrics.
9. Tools for CVSS Scoring
CVSS Calculators
| Tool | Type | URL | Notes |
|---|---|---|---|
| First.org CVSS Calculator | Official | https://www.first.org/cvss/calculator/3.1 | Recommended for OSCP |
| Snyk CVSS Calculator | Web | https://snyk.io/vuln/data/cvss-calculator | User-friendly interface |
| HackerOne CVSS Calculator | Web | https://www.hackerone.com/vulnerability-weight-scoring | Alternative interface |
Scanner-Integrated Scoring
| Tool | CVSS Support | Notes |
|---|---|---|
| Nessus | Yes | Auto-generates CVSS scores for findings |
| OpenVAS | Yes | Auto-generates CVSS scores for findings |
| Nuclei | Yes | Built-in CVSS scoring for templates |
| Burp Suite | Partial | Can reference CVSS for identified issues |
10. Practical Tips for OSCP
Tip 1: Always use the official First.org calculator. It provides the vector string automatically and ensures accuracy.
Tip 2: For OSCP, focus on Base Metrics. Temporal and Environmental metrics are rarely required.
Tip 3: If a vulnerability has a published CVE, use the official CVSS score as a starting point, then adjust based on your specific context.
Tip 4: Be consistent in your scoring methodology across all findings. Don’t score similar vulnerabilities differently.
Tip 5: When in doubt between two scores, err on the side of the lower score. Overstating severity is as problematic as understating it.
Tip 6: Document your scoring rationale. If your score differs from the published CVE score, explain why.
11. Common Scoring Mistakes
Mistake 1: Overstating Impact
Bad: Giving C:H/I:H/A:H for a vulnerability that only reads a single file.
Good: Giving C:L/I:N/A:N for a vulnerability that reads a single non-sensitive file.
Mistake 2: Ignoring Attack Vector
Bad: Giving AV:N for a local privilege escalation vulnerability.
Good: Giving AV:L for a vulnerability that requires local access.
Mistake 3: Confusing Privileges Required
Bad: Giving PR:N for a vulnerability that requires authenticated access.
Good: Giving PR:L for a vulnerability that requires a regular user account.
Mistake 4: Inconsistent Scoring
Bad: Scoring one SQL injection as 9.8 and another as 7.5 without justification.
Good: Using the same methodology for all similar vulnerabilities and documenting any differences.
12. Key Takeaways
- CVSS is the standard. Use CVSS v3.1 for all vulnerability scoring in your OSCP report.
- Base metrics are essential. Focus on AV, AC, PR, UI, S, C, I, A.
- Use the official calculator. First.org provides the authoritative CVSS calculator.
- Be consistent. Apply the same methodology across all findings.
- Justify your scores. Explain your scoring decisions, especially when they differ from published scores.
- Temporal and Environmental are optional. Focus on Base metrics for OSCP.
- Practice scoring. Use the calculator to practice scoring common vulnerability types.
13. Further Reading
- CVSS v3.1 Specification: https://www.first.org/cvss/v3.1/specification-document
- CVSS v3.1 Calculator: https://www.first.org/cvss/calculator/3.1
- NVD CVSS Guide: https://nvd.nist.gov/vuln-metrics/cvss/v3-calculator
- CVSS v4.0 Specification: https://www.first.org/cvss/v4.0/specification-document