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 python from 3.12.0b1-alpine to 3.12.0rc2-alpine #202

Closed

Conversation

thehappydinoa
Copy link
Member

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 python:3.12.0rc2-alpine, 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
critical severity 786 Out-of-bounds Write
SNYK-ALPINE318-BUSYBOX-5890990
No Known Exploit
critical severity 786 Out-of-bounds Write
SNYK-ALPINE318-BUSYBOX-5890990
No Known Exploit
critical severity 786 Out-of-bounds Write
SNYK-ALPINE318-BUSYBOX-5890990
No Known Exploit
medium severity 514 Allocation of Resources Without Limits or Throttling
SNYK-ALPINE318-OPENSSL-5661572
No Known Exploit
medium severity 514 Excessive Iteration
SNYK-ALPINE318-OPENSSL-5821142
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

Copy link

stale bot commented Dec 15, 2023

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants