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

x/vuln: request govulncheck mark CVE's with severity level #70289

Closed
aep-sunlife opened this issue Nov 11, 2024 · 2 comments
Closed

x/vuln: request govulncheck mark CVE's with severity level #70289

aep-sunlife opened this issue Nov 11, 2024 · 2 comments
Labels
vulncheck or vulndb Issues for the x/vuln or x/vulndb repo

Comments

@aep-sunlife
Copy link

Hi,

I enjoy using govulncheck to scan for vulnerabilities in Go projects.

I would like govulncheck to denote the severity level of each vulnerability, in order to help users prioritize resolution.

Large, complex projects often have hundreds of CVE's, so from a security perspective it makes sense to patch vulnerabilities in descending order of severity.

For comparison, other common SCA tools note severity levels like Critical, High, Medium, Low, Info for each CVE reported.

@gopherbot gopherbot added the vulncheck or vulndb Issues for the x/vuln or x/vulndb repo label Nov 11, 2024
@gopherbot gopherbot modified the milestones: Unreleased, vuln/unplanned Nov 11, 2024
@gabyhelp
Copy link

Related Documentation

(Emoji vote if this was helpful or unhelpful; more detailed feedback welcome in this discussion.)

@seankhliao
Copy link
Member

please see the faq

@seankhliao seankhliao closed this as not planned Won't fix, can't repro, duplicate, stale Nov 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
vulncheck or vulndb Issues for the x/vuln or x/vulndb repo
Projects
None yet
Development

No branches or pull requests

4 participants