Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

[Snyk] Security upgrade golang from 1.13.0-alpine to 1.20.3-alpine #438

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

isp1r0
Copy link
Owner

@isp1r0 isp1r0 commented Apr 5, 2023

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

  • examples/profiles/service1/Dockerfile

We recommend upgrading to golang:1.20.3-alpine, as this image has only 0 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
critical severity 500 Out-of-bounds Read
SNYK-ALPINE310-APKTOOLS-1534688
No Known Exploit
high severity 400 Integer Overflow or Wraparound
SNYK-ALPINE310-OPENSSL-1075741
No Known Exploit
high severity 400 Improper Certificate Validation
SNYK-ALPINE310-OPENSSL-1089244
No Known Exploit
high severity 400 Improper Certificate Validation
SNYK-ALPINE310-OPENSSL-1089244
No Known Exploit
high severity 400 NULL Pointer Dereference
SNYK-ALPINE310-OPENSSL-587954
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:

🦉 NULL Pointer Dereference

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants