-
Notifications
You must be signed in to change notification settings - Fork 38
Adopt CVSS scoring system #956
Comments
Of course there's a calculator inline on HackerOne as well: That's on https://hackerone.com/reports/176396. @dmk246 Are you okay with adopting this? It's more complicated but more accurate as a result. |
@whit537 I just wanted our team to play around with CVSS, before coming to a conclusion. ;) |
Did you fudge the calculation to get it to come out "Medium," or was that a happy coincidence? :) |
Let's call it a happy coincidence. ;) In all seriousness, I am fairly confident that my calculation is correct. Feel free to check it and let me know if you find something wrong. |
@EdOverflow can you check out #165313 and see if it is rated correctly? @whit537 and I went through this one to help me understand it better. |
@dmk246 CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N is spot on! :) |
Thanks @EdOverflow!!! |
|
I don't find the slack link now, but @EdOverflow commented that "Everything is coming out medium" is a known problem with CVSS v3. If that's the case then it may be better to stick with the simple five-point scale instead of going with CVSS. |
Let's try and close this with #1018. @EdOverflow @dmk246 Can you go ahead and reclassify all triaged reports according to CVSS? That should give us enough info to decide on bounty amounts. We're leaning towards $0 for Medium, but it would be good to have a sense of how common High will be before committing to a revised amount there. |
I'm on to it. |
I would highly recommend we start using CVSS terminology and scores to classify security reports.
Here is a CVSS v3 calculator: https://nvd.nist.gov/CVSS/v3-calculator
The text was updated successfully, but these errors were encountered: