Open andresriancho opened 9 years ago
:+1: for cvss, :-1: for removing severity
@m0sth8 any special case where you see that CVSS could be, for example, 1.0 and the severity would be "high" ? I'm trying to understand why you want to keep severity and at the same time add CVSS
Severity field might be useful for tools, that are going to integrate vulndb in their solution, but already use severity.
I want to remove the severity from the JSON data, but have the SDKs (for example python-sdk) calculate it based on CVSS. Would that be ok?
Yes, It's ok :+1:
Idea
Add a CVSS field.
Problems
We already have a severity field with info/low/med/high which is an alternate representation of risk (which is what CVSS scores). Maybe we could:
get_cvss
Tasks