-
Notifications
You must be signed in to change notification settings - Fork 30
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
Unexpected severity result using CVSSv4 #48
Comments
@jobiewinserapck can you please have a look? |
Sure thing, I'll take a look |
Here's the PR: #50 I've fixed both of the issues encountered in the screenshot (details in the commit message). I've added additional tests for these too, hopefully the tests aren't getting too intense as they are currently take 3x as long for cvss4 vs cvss3 |
@jobiewinserapck more tests++ 😄 . @falcochu thanks for reporting the issue. Can you please check if the problem was resolved? |
Hey @skontar and @jobiewinserapck can confirm it is working for me as expected now. Thanks so much for the quick fix and again for the tool :) |
Thanks for the tool and adding support for CVSSv4.
Just doing some testing and got an unexpected result. Using the CVSSv4 update it was able to calculate the base score for the vector "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:L/SI:L/SA:L" as 6.9 correctly but not the correct severity.
Please see code snippet below and in the screenshot.
Actual Results:
Screenshot to compare to CVSSv4 Website
Expected Results:
The text was updated successfully, but these errors were encountered: