Skip to content

docs: note Scout prefers CVSS v4 but uses the same severity bands #25831

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
locker95 wants to merge 1 commit into from
+5 −3
Closed

docs: note Scout prefers CVSS v4 but uses the same severity bands #25831

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 5 additions & 3 deletions content/manuals/scout/explore/analysis.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -205,9 +205,11 @@ categorized as **Unspecified** (U).

Docker Scout doesn't implement a proprietary vulnerability metrics system. All
metrics are inherited from security advisories that Docker Scout integrates
with. Advisories may use different thresholds for classifying vulnerabilities,
but most of them adhere to the CVSS v3.0 specification, which maps CVSS scores
to severity ratings according to the following table:
with. After Scout picks an advisory source, it [prefers CVSS v4 over
v3](/manuals/scout/deep-dive/advisory-db-sources.md) when both scores exist.
Most sources still publish a 0–10 score, and Scout maps that score to a
severity rating with the same bands used by CVSS v3.0 (v4 uses the same
qualitative ranges):

| CVSS score | Severity rating |
| ---------- | ---------------- |
Expand Down