Skip to content
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

[Snyk] Security upgrade golang from 1.21.1-alpine to 1.21.6-alpine #92

Closed

Conversation

scribd-secbot
Copy link

This PR was automatically created by Snyk using the credentials of a real user.


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

Changes included in this PR

  • Dockerfile

We recommend upgrading to golang:1.21.6-alpine, as this image has only 1 known vulnerabilities. To do this, merge this pull request, then verify your application still works as expected.

Some of the most important vulnerabilities in your base image include:

Severity Priority Score / 1000 Issue Exploit Maturity
high severity 614 CVE-2023-5363
SNYK-ALPINE318-OPENSSL-6032386
No Known Exploit
high severity 614 CVE-2023-5363
SNYK-ALPINE318-OPENSSL-6032386
No Known Exploit
medium severity 514 Improper Check for Unusual or Exceptional Conditions
SNYK-ALPINE318-OPENSSL-6055795
No Known Exploit
medium severity 514 Improper Check for Unusual or Exceptional Conditions
SNYK-ALPINE318-OPENSSL-6055795
No Known Exploit

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

🛠 Adjust project settings


Learn how to fix vulnerabilities with free interactive lessons:

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

@scribd-secbot scribd-secbot requested a review from a team as a code owner January 10, 2024 19:51
@Neurostep Neurostep closed this Apr 8, 2024
@fotos fotos deleted the snyk-fix-742e625ada4cda15324357fa2182e589 branch September 20, 2024 14:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

3 participants