1.17 - CVE bitnami/kubernetes and Go bump #9684
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Bump pinned go version and bitnami/kubectl image to resolve CVEs
Context
Routine Trivy scans identified CVE-2024-24790 in our images, with issues opened including #9669
Issues were opened for all GA LTS branches, but not 1.18 and 1.17 as they are not yet in GA
Nevertheless, we should resolve the CVE in all versions, and it's simplest to start from
main
and work backwardWhile validating the existence of the CVE identified in LTS versions, we also found that CVE-2024-24788 is present in scans of v1.17.0-rc6
#9679 has been opened to add pre-releases to our scans moving forward
Interesting decisions
We bump bitnami/kubectl to the minor version that matches k8s dependencies in order to keep these in sync
Testing steps
I manually tested the latest released images as follows:
Results:
I then rebuilt images locally from this branch and scanned them:
Results:
I also tested the images published for the PR:
Results:
I also did these steps for
-distroless
imagesChecklist: