Skip to content

[Snyk] Security upgrade golang from 1.15.14 to 1.26rc2#116

Open
stevemac007 wants to merge 1 commit intomasterfrom
snyk-fix-1de55bb910f70ee593016d2822c8a8c8
Open

[Snyk] Security upgrade golang from 1.15.14 to 1.26rc2#116
stevemac007 wants to merge 1 commit intomasterfrom
snyk-fix-1de55bb910f70ee593016d2822c8a8c8

Conversation

@stevemac007
Copy link
Copy Markdown

snyk-top-banner

Snyk has created this PR to fix 4 vulnerabilities in the dockerfile dependencies of this project.

Keeping your Docker base image up-to-date means you’ll benefit from security fixes in the latest version of your chosen image.

Snyk changed the following file(s):

  • Dockerfile.build

We recommend upgrading to golang:1.26rc2, as this image has only 109 known vulnerabilities. To do this, merge this pull request, then verify your application still works as expected.

Vulnerabilities that will be fixed with an upgrade:

Issue Score
high severity CVE-2023-44487
SNYK-DEBIAN10-NGHTTP2-5953390
  829  
critical severity Link Following
SNYK-DEBIAN10-GIT-6846202
  821  
critical severity Link Following
SNYK-DEBIAN10-GIT-6846202
  821  
critical severity Unquoted Search Path or Element
SNYK-DEBIAN10-OPENSSH-5788320
  821  
high severity CVE-2023-26604
SNYK-DEBIAN10-SYSTEMD-3339153
  786  

Important

  • Check the changes in this PR to ensure they won't cause issues with your project.
  • Max score is 1000. Note that the real score may have changed since the PR was raised.
  • This PR was automatically created by Snyk using the credentials of a real user.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.

For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic


Learn how to fix vulnerabilities with free interactive lessons:

🦉 Learn about vulnerability in an interactive lesson of Snyk Learn.

Copy link
Copy Markdown

@amazon-q-developer amazon-q-developer bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Security Upgrade Review

This PR upgrades the Go base image from 1.15.14 to 1.26rc2 to address critical security vulnerabilities. However, there are significant concerns:

Critical Issues:

  1. Release Candidate Risk: Using golang:1.26rc2 (a release candidate) in production is highly risky. Release candidates may contain bugs, incomplete features, or breaking changes that could cause application failures.

  2. Version Availability: Go 1.26 has not been officially released yet. The latest stable Go version is 1.22.x.

Recommendations:

  • Immediate Action: Replace golang:1.26rc2 with golang:1.22 (latest stable version)
  • Security Benefits: Go 1.22 will still provide significant security improvements over 1.15.14 while maintaining stability
  • Testing: Thoroughly test the application with the new Go version, as there may be breaking changes between 1.15 and 1.22

Alternative Approach:

If you need the absolute latest security patches, consider golang:1.22-alpine for a smaller attack surface, or wait for Go 1.26 to be officially released before upgrading.

The security vulnerabilities mentioned in the PR description are valid concerns, but using a stable Go version is the safer approach for production environments.


You can now have the agent implement changes and create commits directly on your pull request's source branch. Simply comment with /q followed by your request in natural language to ask the agent to make changes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants