Menu

πŸ“ CVSS 4.0 for Bug Reports: Score the Impact You Actually Proved
πŸ“°

πŸ“ CVSS 4.0 for Bug Reports: Score the Impact You Actually Proved

DEV Community: appsecΒ·Krishna KumarΒ·12 days ago
#l1gBBGci
#devtoappsec#devto#dev#cvss#score
Reading 0:00
15s threshold

Most severity arguments over a bug report are not really about the bug. They are about the gap between what the reporter showed and what the reporter scored. The proof says "I read another user's invoice". The score says Critical, because "this could lead to full account takeover". The triager rescores it, the reporter feels robbed, and both sides lose a week.

CVSS 4.0 has a rule for this, and it is the most useful sentence in the spec for anyone who writes reports. In short: score the impact you are confident an attacker can actually achieve, and score the end state, not the scariest thing you can imagine. That turns severity from a debate into a checklist. Every metric value should point at a piece of evidence in your report.

This post walks through the CVSS 4.0 base metrics from a web and API tester's point of view, shows how the same stand-in bug scores anywhere from 9.3 to 5.3 depending on what you proved, and ends with a report block you can copy.…

Continue reading β€” create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.