chore: bump versions to fix CVE#244
Conversation
|
letFunny
left a comment
There was a problem hiding this comment.
Thanks James for working on this so proactively! Only a few minor questions.
| module github.com/canonical/chisel | ||
|
|
||
| go 1.23.8 | ||
| go 1.24.6 |
There was a problem hiding this comment.
Why not go for 1.25 now that we are updating. The last time we discussed this (Gustavo & me) the problem is that only the last two major versions are supported officially by the Go team, so if we could update to the latest that would mean we don't have to upgrade as often.
Not saying we have to do it, just asking.
There was a problem hiding this comment.
That's a good consideration. The major reason pushing us away from doing this is that go 1.25 is still on the edge channel of the go snap. A minor reason is that we cannot necessarily save the efforts of bumping versions, as vulnerabilities can also exist in newer minor versions with older patch version numbers.
There was a problem hiding this comment.
The major reason pushing us away from doing this is that go 1.25 is still on the edge channel of the go snap.
This is enough reason for me. Thanks for the context
letFunny
left a comment
There was a problem hiding this comment.
Thanks for this James, greatly appreciated!
Famous last words. ;-) |
The minimal required Go version is bumped to
1.24.6to fix GO-2025-3956/CVE-2025-47906. The Go version1.23.12cannot be used due to the unavailability in the snapstore.The version of package
github.com/ulikunitz/xzis bumped tov0.5.15to fix GO-2025-3922/CVE-2025-58058.A complete
govulncheckbefore the fix goes as follows:There are no vulnerabilities found after this version bump.