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 redhat/ubi8-minimal from latest to 8.9-1108 #910

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

svetasmirnova
Copy link
Contributor

@svetasmirnova svetasmirnova commented Jan 11, 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

  • percona-server-mongodb-4.4/Dockerfile.k8s

We recommend upgrading to redhat/ubi8-minimal:8.9-1108, as this image has only 88 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 Memory Leak
SNYK-RHEL8-LIBCAP-5660406
No Known Exploit
medium severity 514 Integer Overflow or Wraparound
SNYK-RHEL8-LIBCAP-5660413
No Known Exploit
low severity 364 Resource Exhaustion
SNYK-RHEL8-OPENSSLLIBS-5804834
No Known Exploit
medium severity 371 Heap-based Buffer Overflow
SNYK-RHEL8-SQLITELIBS-6140699
No Known Exploit
medium severity 371 Man-in-the-Middle (MitM)
SNYK-RHEL8-SYSTEMDLIBS-6137227
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:

🦉 Memory Leak
🦉 Resource Exhaustion

@it-percona-cla
Copy link

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
You have signed the CLA already but the status is still pending? Let us recheck it.

@@ -1,4 +1,4 @@
FROM redhat/ubi8-minimal
FROM redhat/ubi8-minimal:8.9-1108
Copy link
Collaborator

Choose a reason for hiding this comment

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

shouldn't be the versioned changes also merged into latest?
As for the best practices:

Best Practices:
For Development and Testing: Using latest can be beneficial for staying up-to-date with the newest features and fixes. However, be mindful of potential instability.
For Production: It's generally recommended to use specific version tags. This approach ensures stability and predictability. You should have a process in place to regularly update the version, ideally after testing the new version in a non-production environment.

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