Severity Assessment and CVSS Scoring
What you'll learn: How bug bounty programs and security teams objectively measure vulnerability severity and assign rewards based on standardized scoring systems.
When a security researcher submits a vulnerability, the first question everyone asks is: "How bad is it?" Not all bugs are created equal—a typo on a help page versus remote code execution demand very different responses and rewards.
What is CVSS?
The Common Vulnerability Scoring System (CVSS) is the industry-standard framework for rating vulnerability severity on a scale from 0.0 to 10.0. Think of it like a nutritional label—it breaks down a vulnerability into measurable components:
- Attack Vector: Can it be exploited remotely or does it require local access?
- Attack Complexity: Is exploitation straightforward or does it need rare conditions?
- Privileges Required: Does the attacker need authentication?
- User Interaction: Must a victim take action (like clicking a link)?
- Impact: What damage occurs to confidentiality, integrity, or availability?
A SQL injection accessible from the internet with no authentication might score 9.8 (Critical), while a minor information disclosure requiring admin access might score 3.1 (Low).
Custom Scoring in Bounty Programs
Many bug bounty programs combine CVSS with custom factors:
- Asset criticality: A vulnerability in your payment system trumps one in a test environment
- Exploitability: Theoretical versus weaponized exploits
- Data sensitivity: Access to PII versus public marketing pages
- Business impact: Actual harm potential to operations or users
This is why two "High" CVSS bugs might receive 5,000 rewards respectively—the scoring guides triage, but context determines the payout.
Key Takeaway: CVSS provides objective, reproducible severity scoring that guides both security prioritization and bounty rewards, but programs layer additional context-specific factors to determine final assessments and payouts.