Course contentsShow
← Security
Lesson 1265 of 3,05226. Application Security - Supply ChainFree lesson

Evaluating Vulnerability Severity and Exploitability

Learn to assess CVSS scores, understand exploitability metrics, and prioritize vulnerabilities based on actual risk to your application.

Evaluating Vulnerability Severity and Exploitability

What you'll learn: How to assess vulnerability reports using CVSS scores and exploitability metrics to prioritize which dependency vulnerabilities truly threaten your application.

The Problem with All Vulnerabilities Looking Equal

After scanning your dependencies (as in the previous lesson), you might face 50+ vulnerability reports. Not all are equally dangerous. A critical-sounding CVE in a library you don't actually use is less urgent than a moderate vulnerability in code that handles user input directly.

Understanding CVSS Scores

The Common Vulnerability Scoring System (CVSS) provides a standardized 0-10 severity rating. It considers:

  • Attack Vector: Network-accessible (high risk) vs. requires local access (lower risk)
  • Attack Complexity: Easy to exploit vs. requires special conditions
  • Privileges Required: Anonymous attacker vs. authenticated admin needed
  • User Interaction: Automatic vs. requires victim action
  • Impact: Does it leak data, allow code execution, or just crash the app?

A CVSS 9.8 sounds terrifying, but context matters.

Contextual Risk Assessment

Ask these questions:

  1. Do you use the vulnerable code path? A critical XSS in a library's admin panel doesn't matter if you never import that module.
  2. Is it exploitable in your architecture? A server-side vulnerability might not apply if you only use the library client-side.
  3. Are exploits public? Known exploits in the wild dramatically increase urgency.
  4. What's your exposure? Internet-facing systems need faster patching than internal tools.

Think of CVSS as a car's maximum speed rating—important, but you also need to know the road conditions, traffic, and whether you're actually driving that route.

Prioritization Strategy

Rank vulnerabilities by: Severity × Exploitability × Your Exposure

Focus first on high CVSS scores in code paths you actively use, especially when public exploits exist.

Key Takeaway: CVSS scores are a starting point, not the final answer—prioritize vulnerabilities based on actual exploitability in your specific application context, not just the number on the report.