-
Notifications
You must be signed in to change notification settings - Fork 641
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-8558 for k8s.io/kubernetes v1.14.6 #742
Comments
This would be resolved by #706 once merged. |
It'd be great if someone helped me on that PR. I got lost and don't know why tests are failing. Since almost months passed from submitting, now I have to update all the deps again to match with upstream k8s repo. Feel free to ping me. Or, we can submit a particular PR to remediate this specific vulnerability. |
I agree about the need to bump dependencies. |
Hey! Thanks for the interest. At PR #706, I couldn't able to make CI pass after lots of work. And I decided to abandon it. So let me ping the maintainer, maybe @vteratipally got a thought on this. |
Hey @Dentrax, I've created a branch which cherry picks the changes you made in order to tackle the CVE mentioned in the issue. Thank you for the work you've done in #706, it was crucial for allowing me to create this change. |
I've created PR #761 to address the CVE this issue discusses. Please take a look. |
I made a CVE-free version of node-problem-detector! Check this out: https://github.com/chainguard-images/images/tree/main/images/node-problem-detector
|
This should be fixed by #806. |
@hakman: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Our security scanner is identifying CVE-2020-8558 for node-problem-detector due to k8s.io/kubernetes version 1.14.6.
Are their plans to update this module or node-problem-detector somehow confirmed as not vulnerable?
The text was updated successfully, but these errors were encountered: