Skip to content

[Snyk] Security upgrade golang from 1.13-alpine to 1.18.2-alpine#84

Open
tofarley wants to merge 1 commit intomasterfrom
snyk-fix-e1a3eeb380de0acb30dc08651b051f14
Open

[Snyk] Security upgrade golang from 1.13-alpine to 1.18.2-alpine#84
tofarley wants to merge 1 commit intomasterfrom
snyk-fix-e1a3eeb380de0acb30dc08651b051f14

Conversation

@tofarley
Copy link
Copy Markdown

@tofarley tofarley commented Jun 8, 2022

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

  • vendor/github.com/spotahome/kooper/docker/dev/Dockerfile

We recommend upgrading to golang:1.18.2-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 CVE-2022-28391
SNYK-ALPINE312-BUSYBOX-2440610
No Known Exploit
critical severity 500 Buffer Overflow
SNYK-ALPINE312-OPENSSL-1569452
No Known Exploit
critical severity 500 Buffer Overflow
SNYK-ALPINE312-OPENSSL-1569452
No Known Exploit
high severity 511 Loop with Unreachable Exit Condition ('Infinite Loop')
SNYK-ALPINE312-OPENSSL-2426332
No Known Exploit
high severity 511 Loop with Unreachable Exit Condition ('Infinite Loop')
SNYK-ALPINE312-OPENSSL-2426332
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.

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