Skip to content
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

Jump to bottom

Change the scoring method to be based on vendor (first priority) and NVD (second). #310

Closed
knqyf263 opened this issue Dec 11, 2019 · 0 comments
Closed

Change the scoring method to be based on vendor (first priority) and NVD (second). #310

knqyf263 opened this issue Dec 11, 2019 · 0 comments
Labels
kind/deprecation Categorizes issue or PR as related to a feature/enhancement marked for deprecation.

Comments

@knqyf263
Copy link
Collaborator

Currently Trivy uses the NVD score.
There are cases where vendor (e.g. Redhat) says that vulnerability is medium, while NVD says it is critical.
We should prefer Vendor's verdict as our primary source of truth.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/deprecation Categorizes issue or PR as related to a feature/enhancement marked for deprecation.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@knqyf263