Closed kadirtaskiran closed 1 year ago
@kadirtaskiran for the ca-certificate vuln in v2.4.6 we recognized it from our internal scanning and fixed it in v2.4.7. We will continue to address the vulns for future release.
I've updated the module dependencies in PR #3114 to fix the CVE.
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
Closing the issue as the Vulns have been addressed.
Describe the bug While scanning the v2.4.6 and v2.4.7 docker images of alb ingress controller we see following vulnerabilities.
Steps to reproduce Scan the image for vulnerabilities
Expected outcome No vulnerabilities
Environment
Additional Context:
Can someone please help me on how avoid this vulnerabilities Thanks, Kadir