You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When tried to upgrade to Go 1.21 (although I am not that familiar with Go), the build of the binary went through with compile-with-docker command and grype aws-lambda-rie reported not vulnerabilities.
Hi. Thanks for the report. We recently updated to the latest version in Go 1.20, but we might have to update to 1.21 like you mention. We'll take a look.
> grype version Application: grype Version: 0.74.7 BuildDate: 2024-02-26T18:24:14Z GitCommit: 987238519b8d6e302130ab715f20daed6634da68 GitDescription: v0.74.7 Platform: darwin/amd64 GoVersion: go1.21.7 Compiler: gc Syft Version: v0.105.1 Supported DB Schema: 5
> grype aws-lambda-rie NAME INSTALLED FIXED-IN TYPE VULNERABILITY SEVERITY stdlib go1.20.14 go-module CVE-2024-24785 Unknown stdlib go1.20.14 go-module CVE-2024-24784 Unknown stdlib go1.20.14 go-module CVE-2024-24783 Unknown stdlib go1.20.14 go-module CVE-2023-45290 Unknown stdlib go1.20.14 go-module CVE-2023-45289 Unknown
When tried to upgrade to Go 1.21 (although I am not that familiar with Go), the build of the binary went through with
compile-with-docker
command andgrype aws-lambda-rie
reported not vulnerabilities.Here is the diff:
The text was updated successfully, but these errors were encountered: