Fixed Go Vulns due to istioctl and rootless docker kit #579
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Vulnerability Summary
Vulnerabilities Fixed ✅
1. istioctl (FIXED)
Location:
usr/local/bin/istioctlVulnerabilities:
istio.io/istio- CVE-2019-14993, CVE-2021-39155, CVE-2021-39156, CVE-2022-23635github.com/go-viper/mapstructure/v2v2.2.1 → needs v2.3.0 or v2.4.0stdlibv1.24.4 → needs v1.24.6Fix Applied: Updated from version 1.28.0 to 1.28.1 (released Dec 3, 2025)
ENV ISTIO_VERSION=1.28.1Why it can be fixed: Istio releases are frequent and the latest stable version (1.28.1) contains the necessary security patches.
2. rootlesskit (FIXED)
Location:
usr/bin/rootlesskitandusr/bin/rootlesskit-docker-proxyVulnerabilities:
stdlibv1.24.3 → needs v1.24.4 or v1.24.6Fix Applied: Pinned to explicit version v2.3.5 (latest stable, released May 2025)
ROOTLESSKIT_VERSION=v2.3.5Why it can be fixed: The latest stable release v2.3.5 should be compiled with a newer Go version that addresses the stdlib vulnerabilities. By pinning the version, we ensure reproducible builds and can track when newer versions are available.
Summary Table