Bump Go to 1.20.11 to mitigate against insecure Windows path parsing #12690
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
This change address CVE-2023-45283. There have been no reported issues with Packer but we are bumping given its usage of the path/filepath pkg.
nywilken
added
security
|
Hi Team, we are seeing other vulnerabilities CVE-2023-39318, CVE-2023-39319 because of go version 1.20.7 in the packer current release 1.9.4 . I could see this MR got merged with the go version updated to 1.20.11. I request you to please provide a new release with all these new changes on top of 1.9.4 so that we can use these new code changes and unblock our self. Thanks in advance |
|
I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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 change address CVE-2023-45283. There have been no reported issues
with Packer but we are bumping given its usage of the path/filepath pkg.