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.11-alpine to 3.13.0a4-alpine #119

Closed
wants to merge 1 commit into from

Conversation

zencircle
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

  • Dockerfile

We recommend upgrading to python:3.13.0a4-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
medium severity 514 Improper Restriction of Recursive Entity References in DTDs ('XML Entity Expansion')
SNYK-ALPINE319-EXPAT-6241037
No Known Exploit
high severity 614 Resource Exhaustion
SNYK-ALPINE319-EXPAT-6241038
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:

🦉 Resource Exhaustion

Copy link

Coverage report

This PR does not seem to contain any modification to coverable code.

Copy link
Contributor

@jcadam14 jcadam14 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actually, python 3.13 is still in development. Looking to see if python3.12.2-alpine image takes care of these vulnerabilities.

@hkeeler
Copy link
Member

hkeeler commented Mar 15, 2024

Yeah, we should definitely not be upgrading past Python 3.12.x.

Also, I'm a little confused about how this PR was generated. @zencircle, do you have a Snyk account that's setup to interact with our repos?

@hkeeler
Copy link
Member

hkeeler commented May 6, 2024

Closing this. We are not upgrading to Python 3.13 anytime soon.

@hkeeler hkeeler closed this May 6, 2024
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.

4 participants