chore: bump Go to 1.20 to resolve CVE-2023-29405, CVE-2023-29404 #99
Conversation
This file contains 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
|
Kudos, SonarCloud Quality Gate passed!
|
|
@spark2ignite I would appreciate a +1 here if you think this is acceptable. The 9.8 CVE score as |
spark2ignite
approved these changes
Jul 7, 2023
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.
This PR aims to resolve two recent CVEs that are related and each has a score of 9.8.
Both publications indicate that updating to Go 1.20.5 or later will resolve the vulnerability finding in our container scanning solution. I have updated the
Dockerfileandgo.modto reflect this change. Runningmake testandmake imagelocally yields no test failures or build issues.I have also taken the opportunity to bump the
build.ymlGH Action to utilize the newer Ubuntu 22.04 LTS image over the older Ubuntu 20.04 option to keep things fresh.