-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Go should be upgraded; currently using 1.20 which is EOL and has security issues #657
Comments
Acknowledged. It is our estimate that these are not exploitable either. Upgrading to Go is something we have planned, but I believe we hit some issues so we're still sorting through that. |
I ran go 1.22.3 is now being used, which addresses many findings. But, there are still some findings that would be addressed by using go 1.22.4.
|
Expected Behavior
This project currently uses go 1.20 which is EOL and unsupported, see https://go.dev/doc/devel/release It also has security vulnerabilities which scanners such as Trivy report.
Therefore, I believe that this project should upgrade go to 1.21 or better yet 1.22.
Current Behavior
Trivy reports some vulnerabilities, all of which can be addressed by using the latest version of
go
.Possible Solution
I suggest that the version of go be updated to the latest version (currently 1.22.3).
Steps to Reproduce
docker run -it aquasec/trivy:0.51.1 image gcr.io/paketo-buildpacks/bellsoft-liberica
Motivations
I don't think these vulnerabilities are exploitable, but they're still present which isn't great. And their presence causes a lot of trouble for those who use automated security scanning systems as such users must suppress these findings.
The text was updated successfully, but these errors were encountered: