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-slim to 3.13.0a3-slim #24

Closed
wants to merge 1 commit into from

Conversation

mjanez
Copy link
Owner

@mjanez mjanez commented Feb 2, 2024

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

  • ckan-ogc/Dockerfile

We recommend upgrading to python:3.13.0a3-slim, as this image has only 45 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 **** CVE-2023-6779
SNYK-DEBIAN12-GLIBC-6210088
No Known Exploit
low severity **** CVE-2023-6779
SNYK-DEBIAN12-GLIBC-6210088
No Known Exploit
low severity **** CVE-2023-6246
SNYK-DEBIAN12-GLIBC-6210098
No Known Exploit
low severity **** CVE-2023-6780
SNYK-DEBIAN12-GLIBC-6210099
No Known Exploit
critical severity 500 Integer Overflow or Wraparound
SNYK-DEBIAN12-ZLIB-6008963
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.

@mjanez mjanez closed this Feb 8, 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.

2 participants