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.18 to 3 #684

Closed
wants to merge 1 commit into from

Conversation

ankurdotb
Copy link
Contributor

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

  • docker/Dockerfile

We recommend upgrading to alpine:3, as this image has only 2 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
low severity 586 CVE-2023-6129
SNYK-ALPINE318-OPENSSL-6152404
No Known Exploit
low severity 586 CVE-2023-6129
SNYK-ALPINE318-OPENSSL-6152404
No Known Exploit
low severity 436 CVE-2023-6237
SNYK-ALPINE318-OPENSSL-6160000
No Known Exploit
low severity 436 CVE-2023-6237
SNYK-ALPINE318-OPENSSL-6160000
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.

@ankurdotb
Copy link
Contributor Author

Superseded by #682

@ankurdotb ankurdotb closed this Apr 9, 2024
@ankurdotb ankurdotb deleted the snyk-fix-ac425c11055be38c702d66388f95e22f branch April 9, 2024 12:04
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.

2 participants