Skip to content
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

fix(sec): upgrade k8s.io/kube-proxy to 1.18.4 #3480

Closed

Conversation

chncaption
Copy link

What happened?

There are 1 security vulnerabilities found in k8s.io/kube-proxy v0.25.6

What did I do?

Upgrade k8s.io/kube-proxy from v0.25.6 to 1.18.4 for vulnerability fix

What did you expect to happen?

Ideally, no insecure libs should be used.

The specification of the pull request

PR Specification from OSCS

@cla-assistant
Copy link

cla-assistant bot commented Jul 7, 2023

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
You have signed the CLA already but the status is still pending? Let us recheck it.

@sealos-ci-robot
Copy link
Member

🤖 Generated by lychee action

Summary

Status Count
🔍 Total 846
✅ Successful 323
⏳ Timeouts 0
🔀 Redirected 0
👻 Excluded 522
❓ Unknown 0
🚫 Errors 0

Full action output

Full Github Actions output

@fengxsong
Copy link
Collaborator

#3385 #3364

@cuisongliu
Copy link
Collaborator

This upgrade needs to be more cautious and needs to be tested.

@cuisongliu
Copy link
Collaborator

https://m.freebuf.com/vuls/245955.html
This vulnerability seems to have no impact on us. We use kube-proxy to use the ipvs module, and the rest is to call template rendering.

@cuisongliu cuisongliu closed this Jul 7, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants