-
Notifications
You must be signed in to change notification settings - Fork 0
[Snyk] Security upgrade python from 3.7.12-slim to 3.13.0a2-slim #31
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
Conversation
The following vulnerabilities are fixed with an upgrade: - https://snyk.io/vuln/SNYK-DEBIAN11-GLIBC-5927133 - https://snyk.io/vuln/SNYK-DEBIAN11-OPENSSL-2807596 - https://snyk.io/vuln/SNYK-DEBIAN11-OPENSSL-2807596 - https://snyk.io/vuln/SNYK-DEBIAN11-OPENSSL-2933518 - https://snyk.io/vuln/SNYK-DEBIAN11-OPENSSL-2933518
Insecure Access Control (1)
More info on how to fix Insecure Access Control in Dockerfile. 👉 Go to the dashboard for detailed results. 📥 Happy? Share your feedback with us. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Prisma Cloud has found errors in this PR ⬇️
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LOW Healthcheck instructions have not been added to container images
Resource: /server/projects/login/Dockerfile. | Checkov ID: CKV_DOCKER_2
Description
We recommend that you add the HEALTHCHECK instruction to your Docker container images to ensure that health checks are executed against running containers.
An important security control is that of availability.
Adding the HEALTHCHECK instruction to your container image ensures that the Docker engine periodically checks the running container instances against that instruction to ensure that containers are still operational.
Based on the results of the health check, the Docker engine could terminate containers which are not responding correctly, and instantiate new ones.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LOW A user for the container has not been created
Resource: /server/projects/login/Dockerfile. | Checkov ID: CKV_DOCKER_3
Description
Containers should run as a non-root user.
It is good practice to run the container as a non-root user, where possible.
This can be done either via the USER directive in the Dockerfile or through gosu or similar where used as part of the CMD or ENTRYPOINT directives.
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
We recommend upgrading to
python:3.13.0a2-slim, as this image has only 36 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:
SNYK-DEBIAN11-GLIBC-5927133
SNYK-DEBIAN11-OPENSSL-2807596
SNYK-DEBIAN11-OPENSSL-2807596
SNYK-DEBIAN11-OPENSSL-2933518
SNYK-DEBIAN11-OPENSSL-2933518
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.