-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Update github.com/gogo/protobuf (CVE-2021-3121) #1066
Conversation
👋 Thanks for contributing to Viper! You are awesome! 🎉 A maintainer will take a look at your pull request shortly. 👀 In the meantime: We are working on Viper v2 and we would love to hear your thoughts about what you like or don't like about Viper, so we can improve or fix those issues. ⏰ If you have a couple minutes, please take some time and share your thoughts: https://forms.gle/R6faU74qPRPAzchZ9 📣 If you've already given us your feedback, you can still help by spreading the news, https://twitter.com/sagikazarmark/status/1306904078967074816 Thank you! ❤️ |
f04f0c5
to
90ed4cf
Compare
I am also eager to have this fix in 👍 |
You will also need to upgrade github.com/prometheus/client_golang as the current dependency version is also using a bad version of protobuf |
90ed4cf
to
eac3f5e
Compare
Our CI fails because of [CVE-2021-3121] in gogo/protobuf, which is a dependency in Viper -> Prometheus common -> Go Kit -> ... There is a 3 month old PR in viper: spf13/viper#1066 Viper is used to read configs, maybe it's safe to ignore it.
Is there an update on getting this merged? Maybe @sagikazarmark can help as he is the latest committer. I can open a new PR that is good to merge if needed. |
Hey guys, is there any update on this? Would love to see this merged. |
Update github.com/gogo/protobuf to v1.3.2 in response to CVE-2021-3121