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.10.4-alpine3.16 to 3.10.11-alpine3.16 #1

Closed

Conversation

rubelhassan
Copy link

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

  • images/keripy.dockerfile

We recommend upgrading to python:3.10.11-alpine3.16, as this image has only 4 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
high severity 614 Use After Free
SNYK-ALPINE316-BUSYBOX-2953070
No Known Exploit
high severity 614 Use After Free
SNYK-ALPINE316-BUSYBOX-2953070
No Known Exploit
high severity 614 Double Free
SNYK-ALPINE316-OPENSSL-3314624
No Known Exploit
high severity 614 Access of Resource Using Incompatible Type ('Type Confusion')
SNYK-ALPINE316-OPENSSL-3314641
No Known Exploit
critical severity 714 Out-of-bounds Write
SNYK-ALPINE316-ZLIB-2976176
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:

🦉 Access of Resource Using Incompatible Type ('Type Confusion')
🦉 Use After Free

@clackwork
Copy link

Please do not merge this for the moment. I'm working on the same thing, but with a different fix. Also, it isn't clear whether the target merge branch is appropriate.

Copy link

@clackwork clackwork left a comment

Choose a reason for hiding this comment

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

Please do not merge this for the moment. I'm working on the same thing, but with a different fix. Also, it isn't clear whether the target merge branch is appropriate.

@s-a-tanjim
Copy link
Member

We should not make any changes to production branch before wallet migration. Our production wallets depend on this. I'm closing this PR for now.

@s-a-tanjim s-a-tanjim closed this Feb 7, 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