-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
CVE in v1.0.0 #1209
Comments
Running
|
Hmm it seems that the viper dependency moved into the cobra/cobra directory so the vulnerability still exists on master. Looks like viper is also working on a fix: spf13/viper#961 |
Thanks for bringing this up! I've checked out the v1.0.0 branch and I've confirmed that cobra itself does not need or use any of these dependencies. They appear to be indirect dependencies primarily from the viper library. coreos/etcd:
Usage in viper:
gorilla/websocket:
Usage in viper:
golang.org/x/crypto
This one's a bit trickier, but looks like several of viper and pflag's dependencies rely on the These CVE's also appear to all be networking / web server related. So i'm not worried about exposing cobra users to these vulnerabilities. And yes, until etcd adds proper go mod support, there isn't really a way to add a replace statement. But for now, this doesn't directly affect cobra. |
Hello we recently ran a CVE scan on a project that requires [email protected] and it seems like it is the result of this dependency:
It looks like it is related to CVE-2020-15114 The current go.mod on master doesn't require [email protected] anymore and I was wondering if it would be possible to do a patch release.
EDIT: Used JIRA linking syntax instead of markdown
The text was updated successfully, but these errors were encountered: