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.18-bullseye to 1.19-bullseye #95

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

Conversation

teeohhem
Copy link

@teeohhem teeohhem commented Mar 8, 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

  • Dockerfile

We recommend upgrading to golang:1.19-bullseye, as this image has only 113 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 714 Exposure of Resource to Wrong Sphere
SNYK-DEBIAN11-CURL-3065656
No Known Exploit
high severity 614 Allocation of Resources Without Limits or Throttling
SNYK-DEBIAN11-CURL-3320498
No Known Exploit
critical severity 714 Integer Overflow or Wraparound
SNYK-DEBIAN11-GIT-3232722
No Known Exploit
critical severity 714 Integer Overflow or Wraparound
SNYK-DEBIAN11-GIT-3232724
No Known Exploit
high severity 678 Access of Resource Using Incompatible Type ('Type Confusion')
SNYK-DEBIAN11-OPENSSL-3314584
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:

🦉 Allocation of Resources Without Limits or Throttling

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