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

vulnerabilities due to using older go version #534

Open
GabiKalaora opened this issue Jan 9, 2024 · 4 comments
Open

vulnerabilities due to using older go version #534

GabiKalaora opened this issue Jan 9, 2024 · 4 comments

Comments

@GabiKalaora
Copy link

What steps did you take and what happened:
we see vulnerabilities in protecode and whitesource(MEND) scans, these vulnerabilities can be resolved by using go version 1.21.4

What did you expect to happen:
scans retun clean results

Anything else you would like to add:
I see that in the last few version upgrades you didnt upgrade go, is it planned for the following version?

Environment:

  • helm version v1.12.2
  • helm chart version and app version 5.2.0
  • Kubernetes version (use kubectl version):
  • Kubernetes installer & version:
  • Cloud provider or hardware configuration:
  • OS (e.g. from /etc/os-release):
@jenting
Copy link
Collaborator

jenting commented Jan 10, 2024

This is the helm chart repo which generally would not include the Go.
Are you referring to the velero container image and it's related plugin images? If yes, could you please file the issue to https://github.com/vmware-tanzu/velero/issues? Thank you.

@jenting
Copy link
Collaborator

jenting commented Feb 20, 2024

@qiuming-best could you please check this issue in Velero core code?

@qiuming-best
Copy link
Collaborator

qiuming-best commented Feb 21, 2024

@GabiKalaora we'll upgrade the Golang version in each Velero release, and we will do it in a later Velero version

@blackpiglet
Copy link
Collaborator

@GabiKalaora
Velero hasn't used the scanner you mentioned.
Could you post the found CVEs here?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants