-
Notifications
You must be signed in to change notification settings - Fork 203
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.
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
Wrong CVSS3 V3.1 QR "MODERATE" #1186
Comments
mnonnenmacher
added a commit
to oss-review-toolkit/ort
that referenced
this issue
Apr 24, 2023
For vulnerability references that come from GitHub advisories VulnerableCode returns the severity as qualitative rating [1] as it is provided by GitHub [2]. For "MEDIUM" severities GitHub uses the term "MODERATE" which is is conflict with the specification. Therefore, map "MODERATE" to "MEDIUM" in such cases. [1]: https://www.first.org/cvss/v3.1/specification-document#Qualitative-Severity-Rating-Scale [2]: aboutcode-org/vulnerablecode#1186 Signed-off-by: Martin Nonnenmacher <[email protected]>
mnonnenmacher
added a commit
to oss-review-toolkit/ort
that referenced
this issue
Apr 24, 2023
For vulnerability references that come from GitHub advisories VulnerableCode returns the severity as qualitative rating [1] as it is provided by GitHub [2]. For "MEDIUM" severities GitHub uses the term "MODERATE" which is is conflict with the specification. Therefore, map "MODERATE" to "MEDIUM" in such cases. [1]: https://www.first.org/cvss/v3.1/specification-document#Qualitative-Severity-Rating-Scale [2]: aboutcode-org/vulnerablecode#1186 Signed-off-by: Martin Nonnenmacher <[email protected]>
I've also reported this upstream to GitHub: github/advisory-database#2189 |
mnonnenmacher
added a commit
to oss-review-toolkit/ort
that referenced
this issue
Apr 24, 2023
For vulnerability references that come from GitHub advisories VulnerableCode returns the severity as qualitative rating [1] as it is provided by GitHub [2]. For "MEDIUM" severities GitHub uses the term "MODERATE" which is is conflict with the specification. Therefore, map "MODERATE" to "MEDIUM" in such cases. [1]: https://www.first.org/cvss/v3.1/specification-document#Qualitative-Severity-Rating-Scale [2]: aboutcode-org/vulnerablecode#1186 Signed-off-by: Martin Nonnenmacher <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
GitHub advisories provide the severity "MODERATE" and as a result VulnerableCode does also provide this severity which according to the specification should be "MEDIUM" instead.
For example, this severity is classified as "MODERATE" by GitHub:
GHSA-c7mc-q43h-5672
It is reported by VulnerableCode as:
It would be good if VulnerableCode could map "MODERATE" to the correct "MEDIUM" in its API response.
The text was updated successfully, but these errors were encountered: