Fix CWE 330 #144
Merged
Fix CWE 330 #144
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
Signed-off-by: Kennelly, Martin <[email protected]>
Upgrade sprig to ver.3 which updates CWE-330 vulnerable goutils to 1.1.1. Sprig ver.3 retains the same Go API as ver.2. Signed-off-by: Martin Kennelly <[email protected]>
|
/lgtm |
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.
Upgraded sprig from v2 to v3 which states no Go API changes for v3 major release upgrade in order to upgrade vulnerable dependency goutils to 1.1.1.
Snyk report: https://snyk.io/vuln/SNYK-GOLANG-GITHUBCOMMASTERMINDSGOUTILS-1296313
This operator doesn't seem vulnerable to this packages vulnerability, but I am trying to maintain a clean snyk scan.
Steps taken to reproduce and fix: