Closed oilbeater closed 6 months ago
Looks like in response to #1019, release artifacts for 1.4.1 were rebuilt (see https://github.com/containernetworking/plugins/issues/1019#issuecomment-2110423038) with a more recent version of Go (1.22.3), so the binaries should no longer be "affected" by these CVEs.
I personally don't think that mutating release artifacts is a good idea (see also https://github.com/containernetworking/plugins/issues/1038), as now there are 2 distinct versions of the "1.4.1" binaries out there. A lot of dependent build processes may rightfully assume that for a given tag, the binaries won't change. But it's done now...
So this issue can probably be closed given that the current binaries were built with Go 1.22.3.
Looks like v1.5.0 has already resolve this issue, thanks!
The binaries for plugins v1.4.1 were built with Go 1.21.7, which has been found to have 1 HIGH CVE and 5 MEDIUM CVEs. A newer version of Go 1.21.9 or 1.22.2 can resolve these CVEs.
I think there is no need to change the code, the action code here: https://github.com/containernetworking/plugins/blob/670139cffa3075aa42f08c8f1dc2257396205a54/.github/workflows/release.yaml#L19 will automatically use the Go with version v1.21.9 when a new build is triggered.