[Snyk] Security upgrade alpine from 3.18.3 to 3.22.1#43
[Snyk] Security upgrade alpine from 3.18.3 to 3.22.1#43
Conversation
The following vulnerabilities are fixed with an upgrade: - https://snyk.io/vuln/SNYK-ALPINE318-OPENSSL-6032386 - https://snyk.io/vuln/SNYK-ALPINE318-OPENSSL-6032386 - https://snyk.io/vuln/SNYK-ALPINE318-OPENSSL-7895535 - https://snyk.io/vuln/SNYK-ALPINE318-OPENSSL-7895535 - https://snyk.io/vuln/SNYK-ALPINE318-OPENSSL-6055795
Code Review Agent Run #04b430Actionable Suggestions - 0Additional Suggestions - 1
Review Details
Bito Usage GuideCommands Type the following command in the pull request comment and save the comment.
Refer to the documentation for additional commands. Configuration This repository uses Documentation & Help |
Changelist by BitoThis pull request implements the following key changes.
|
Snyk has created this PR to fix 3 vulnerabilities in the dockerfile dependencies of this project.
Keeping your Docker base image up-to-date means you’ll benefit from security fixes in the latest version of your chosen image.
Snyk changed the following file(s):
DockerfileWe recommend upgrading to
alpine:3.22.1, as this image has only 0 known vulnerabilities. To do this, merge this pull request, then verify your application still works as expected.Vulnerabilities that will be fixed with an upgrade:
SNYK-ALPINE318-OPENSSL-6032386
SNYK-ALPINE318-OPENSSL-6032386
SNYK-ALPINE318-OPENSSL-7895535
SNYK-ALPINE318-OPENSSL-7895535
SNYK-ALPINE318-OPENSSL-6055795
Important
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
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic
Learn how to fix vulnerabilities with free interactive lessons:
🦉 Access of Resource Using Incompatible Type ('Type Confusion')
Summary by Bito
This PR upgrades Alpine from version 3.18.3 to 3.22.1 in the Dockerfile to address multiple security vulnerabilities. The update spans across various build stages to maintain consistency throughout the container setup. This change strengthens the overall security posture and follows containerization best practices.