-
Notifications
You must be signed in to change notification settings - Fork 18k
x/vuln: Cannot handle multiple "fixed" events on vulns.json #55035
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
Comments
cc @zpavlinovic |
Not really sure if it's a similar case, but also https://pkg.go.dev/vuln/GO-2022-0988 shows nothing for 1.18, but the announcement https://groups.google.com/g/golang-announce/c/x49AQzIVX-s reads like both (https://pkg.go.dev/vuln/GO-2022-0969 and https://pkg.go.dev/vuln/GO-2022-0988 ) were fixed in 1.18.6.
I created a separate issue: #55049 |
Thanks for reporting this! We are looking into the issue and should have a fix soon. |
|
Thanks for confirming. I will close it for now. We can reopen if the issue appears again. |
What version of Go are you using (
go version
)?Does this issue reproduce at the latest version of golang.org/x/vuln?
Yes
What operating system and processor architecture are you using (
go env
)?go env
OutputWhat did you do?
Running govulncheck, getting a false alarm for GO-2022-0969, which has more than one "fixed" events on vulns.json.
Snippets of /home/mrkschan/.gvm/pkgsets/go1.18.6/global/pkg/mod/cache/download/vulndb/vuln.go.dev/stdlib/vulns.json
What did you expect to see?
No vulnerability found on golang 1.18.6
What did you see instead?
The text was updated successfully, but these errors were encountered: