Course contentsShow
← Security
Lesson 1637 of 3,05233. Container SecurityFree lesson

Interpreting Scan Results and Severity

Understanding CVSS scores, exploitability metrics, and prioritizing vulnerabilities based on context and exposure.

Interpreting Scan Results and Severity

What you'll learn: How to read vulnerability scan reports, understand CVSS scores, and prioritize fixes based on real-world risk rather than just numbers.

Understanding CVSS Scores

When your container image scanner completes, it dumps a list of vulnerabilities with scores. The Common Vulnerability Scoring System (CVSS) rates each flaw from 0.0 to 10.0:

  • 0.0-3.9: Low severity
  • 4.0-6.9: Medium severity
  • 7.0-8.9: High severity
  • 9.0-10.0: Critical severity

Think of CVSS like a nutritionist's calorie count—it's useful information, but context matters. A 9.5 vulnerability in a library your container doesn't actually use is less urgent than a 6.5 flaw in your exposed API endpoint.

Exploitability Metrics

CVSS includes exploitability sub-scores that tell you how easy it is to exploit:

  • Attack Vector: Network (worst), Adjacent, Local, Physical (least concern)
  • Attack Complexity: Low (easily exploitable) vs. High (requires specific conditions)
  • Privileges Required: None (anyone can try) vs. High (attacker needs admin access first)

A remotely exploitable vulnerability requiring no authentication demands immediate attention, even if the base score isn't the highest.

Context-Based Prioritization

Scanner results need your judgment:

  • Is the vulnerable component reachable? A flaw in a debug library stripped from production doesn't matter.
  • Does your container expose the attack surface? A network vulnerability in a container with no exposed ports is low-risk.
  • Is there a known exploit in the wild? Check if proof-of-concept code exists.

Key Takeaway: CVSS scores provide a starting point, but effective vulnerability management requires combining severity ratings with exploitability metrics, your container's actual exposure, and operational context to prioritize what truly threatens your environment.