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 alpine from 3.4 to 3.13 #1

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

Conversation

alikhil
Copy link

@alikhil alikhil commented Jul 21, 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

  • Dockerfile

We recommend upgrading to alpine:3.13, 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
medium severity 300 Use of a Broken or Risky Cryptographic Algorithm
SNYK-ALPINE34-OPENSSL-373420
No Known Exploit
high severity 400 Key Management Errors
SNYK-ALPINE34-OPENSSL-374005
No Known Exploit
high severity 400 Key Management Errors
SNYK-ALPINE34-OPENSSL-374005
No Known Exploit
medium severity 471 Information Exposure
SNYK-ALPINE34-OPENSSL-374450
Mature
medium severity 471 Information Exposure
SNYK-ALPINE34-OPENSSL-374450
Mature

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