-
Notifications
You must be signed in to change notification settings - Fork 4k
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
Image scan has detect CVE-2021-3538 #4715
Comments
I've made a little research about this bug and want to add more context into this issue
So we need to update I can make a PR to update |
/assign |
The v1.21.2 image (EKS 1.21 is the last version available atm on AWS) and v1.22.2 also have the CVE-2021-3538
|
@IrisIris pls follow it up. |
According to our Trivy scans, the latest image for 1.24 is also affected. |
Hi, is there a chance we could get a new minor release + image generated with the vulnerability fix? |
@IrisIris ping here. |
/assign @bskiba @MaciekPytel @mwielgus PTAL |
Useless ping, but since this has been opened more than 5 months ago... |
I fixed this issue, but still need some time to do full tests. I'll do my best to PR no later than next Wednesday. |
This CVE is the only one as all others have been fixed, it would be great if this one can be crossed of the list. |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle rotten |
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. This bot triages issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /close not-planned |
@k8s-triage-robot: Closing this issue, marking it as "Not Planned". 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. |
Hi, trivy image scanner has detect 1 critical vulnerability in the latest version:
Could you please fix this?
Which component are you using?:
cluster-autoscaler
What version of the component are you using?:
Component version:
image-tag: v1.23.0
Chart-Version: 9.15.0
What k8s version are you using (
kubectl version
)?:AWS EKS 1.21
What environment is this in?:
AWS EKS
What did you expect to happen?:
No critical vulnerabilites
What happened instead?:
1 critical vulnerability
How to reproduce it (as minimally and precisely as possible):
trivy image k8s.gcr.io/autoscaling/cluster-autoscaler:v1.23.0
The text was updated successfully, but these errors were encountered: