Support Ignoring Results Without CVSS Scores and Configurable CVSS Threshold in config.toml

[dpanic]

Description:

Currently, OSV-Scanner does not provide an option to filter vulnerabilities by their CVSS score directly in the configuration file (config.toml). This feature would greatly enhance usability by allowing users to focus on critical vulnerabilities and ignore those without CVSS scores or below a specified threshold.

---

Proposed Feature:

Add support in the osv-scanner.toml configuration file to:

1. Ignore vulnerabilities without a CVSS score:

   • Allow a boolean flag (e.g., ignoreNoCVSS = true) to exclude results where no CVSS score is provided.

2. Set a minimum CVSS score threshold:

   • Add an option like minCVSS = X.X to only display vulnerabilities with a CVSS score equal to or above the defined threshold.

---

Example Configuration:

# Ignore vulnerabilities without a CVSS score
ignoreNoCVSS = true

# Set minimum CVSS score threshold
minCVSS = 5.0

Expected Behavior:

• When ignoreNoCVSS = true, all vulnerabilities without a CVSS score are excluded from the scan results.
• When minCVSS is set, only vulnerabilities with a CVSS score >= the specified threshold are included in the output.

---

Benefits:

• Reduces noise in scan results, enabling teams to focus on critical vulnerabilities.
• Streamlines vulnerability management workflows by providing better customization options.

---

Let me know if you’d like further details or examples to assist in implementation. Thank you!

[cuixq]

@G-Rath is this something that you can take a look?

[G-Rath]

@cuixq tbh I wondered if this was something we wanted to support at all, given the known issues with the scoring system, but I guess it's probably useful so long as frameworks like SOC and ISO continue to use the scoring system as a factor in setting reaction times and whatnot 🤔

[cuixq]

@G-Rath Thanks for you insights! Sounds like this is not a thing we are going to work on soon.

[github-actions]

This issue has not had any activity for 60 days and will be automatically closed in two weeks

See https://github.com/google/osv-scanner/blob/main/CONTRIBUTING.md for how to contribute a PR if you're interested in helping out.

[github-actions]

Automatically closing stale issue