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.

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

Severity lowered by @advisory-database[bot] #491

Closed
Geolim4 opened this issue Jul 8, 2022 · 5 comments
Closed

Severity lowered by @advisory-database[bot] #491

Geolim4 opened this issue Jul 8, 2022 · 5 comments

Comments

@Geolim4
Copy link

Geolim4 commented Jul 8, 2022

For some reason, the bot has lowered the priority of GHSA-484f-743f-6jx2: 2e8e721

I don't understand why, since it has been validated with "HIGH" severity initially: GHSA-484f-743f-6jx2

@Geolim4 Geolim4 changed the title Severity lowered by @advisory-database advisory-database[bot] Severity lowered by @advisory-database[bot] Jul 8, 2022
@darakian
Copy link
Contributor

darakian commented Jul 8, 2022

@Geolim4 Looks like github was the assigning CNA for that CVE and the score given was medium
https://nvd.nist.gov/vuln/detail/CVE-2019-16774

It's unclear to me why this popped back up, but we reset our ghsa score to align with the score sent to mitre.

@Geolim4
Copy link
Author

Geolim4 commented Jul 8, 2022

@darakian weird, does it looks like a bug to you ?

@darakian
Copy link
Contributor

darakian commented Jul 8, 2022

No, I don't see any bug behavior here. Maybe we didn't score the initial issue properly and that's a conversation we can have if you feel strongly about the severity level, but given the values the behavior seems correct to me.

@Geolim4
Copy link
Author

Geolim4 commented Jul 8, 2022

It's not that bad, I was just wondering why the severity was recalculated wrongly based on the CVSS score I calculated originally, but if it's ok on your POV, that's fine for me despite it can looks weird for repo maintainers.

@darakian
Copy link
Contributor

darakian commented Jul 8, 2022

Cool. Sorry about the confusion and thanks for the feedback 👍

@darakian darakian closed this as completed Jul 8, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants