Grype filtering through CVSS vector
- Dominant language
- Go
- Stars
- 12.9k
- Forks
- 883
- Avg merge
- 3d 6h
- Merged PRs (30d)
- 25
Description
**What would you like to be added**:
Grype currently ouputs a CVSS vector. Grype also has the ability to set a config file describing the kind of components that should be filtered from the output. It would be great if we can filter grype outputs based on certain parts of the CVSS vector (for eg. network exploitable vuln.)
**Why is this needed**:
Allows users to create filters for CVEs that actually affect their runtime env.
**Additional context**:
https://www.first.org/cvss/calculator/3.0
TODO: How to express the filter string/configuration.
Contributor guide
Research direction
Review Grype's existing configuration-based component filtering and how CVSS vectors are produced, then consult the linked CVSS 3.0 calculator context. The open design question is how a filter string or configuration should express selected CVSS attributes; done means users can configure those filters and Grype excludes matching vulnerabilities from its output.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100