-
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-2020-26160 vulnerability #1386
Comments
Thanks for surfacing this. I would call this non-critical since this is not a possible code path in cobra. Dependency tree in spf13/viper:
Does cobra use the spf13/viper/remote module?
Doesn't look like it. While (of course) we want to get this CVE fix in, users of cobra are not directly affected by it since the viper/remote package is not used in cobra. |
There also many CVEs found, can refer to ticket: #1421 |
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem? Please describe.
Viper has dgrijalva/jwt-go (actually v 3.2.0) as a dependency. This library has a known vulnerability CVE-2020-26160.
dgrijalva/jwt-go seem to have a fix for this issue in version release-4.0.0 but it's been abandoned since January 2020.
This issue intends to ensure that go.sum does not have any entries on github.com/dgrijalva/jwt-go once spf13/viper#1115 is merged
The text was updated successfully, but these errors were encountered: