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 ruby from 3.2.2-slim-bullseye to slim-bullseye #79

Closed
wants to merge 1 commit into from

Conversation

jonasbn
Copy link
Owner

@jonasbn jonasbn commented Feb 22, 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

  • Dockerfile

We recommend upgrading to ruby:slim-bullseye, as this image has only 61 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 400 Improper Verification of Cryptographic Signature
SNYK-DEBIAN11-GNUTLS28-6159417
No Known Exploit
high severity 614 Out-of-bounds Write
SNYK-DEBIAN11-PERL-6085272
No Known Exploit
medium severity 514 Out-of-bounds Read
SNYK-DEBIAN11-TAR-3253527
No Known Exploit
critical severity 500 Integer Overflow or Wraparound
SNYK-DEBIAN11-ZLIB-6008961
No Known Exploit
critical severity 500 Integer Overflow or Wraparound
SNYK-DEBIAN11-ZLIB-6008961
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.

Copy link
Owner Author

@jonasbn jonasbn left a comment

Choose a reason for hiding this comment

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

This is not going work, I prefer to have the version mentioned in the dependency outline

@jonasbn jonasbn closed this Jul 18, 2024
@jonasbn jonasbn self-assigned this Jul 18, 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