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 2.5.3-alpine to 2.5.8-alpine #414

Merged
merged 1 commit into from
Apr 9, 2021

Conversation

snyk-bot
Copy link
Contributor

@snyk-bot snyk-bot commented Apr 6, 2021

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

  • issue-reproduction/Dockerfile-pact-broker

We recommend upgrading to ruby:2.5.8-alpine, as this image has only 1 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 571 Improper Certificate Validation
SNYK-ALPINE39-OPENSSL-1089232
No Known Exploit
high severity 571 Improper Certificate Validation
SNYK-ALPINE39-OPENSSL-1089232
No Known Exploit
high severity 500 Integer Overflow or Wraparound
SNYK-ALPINE39-OPENSSL-1089235
No Known Exploit
high severity 500 Cryptographic Issues
SNYK-ALPINE39-OPENSSL-340660
No Known Exploit
high severity 500 NULL Pointer Dereference
SNYK-ALPINE39-OPENSSL-588029
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

@bethesque bethesque merged commit 34c7098 into master Apr 9, 2021
@bethesque bethesque deleted the snyk-fix-734d6998ca4d68661bfa5aed4b192b2e branch April 9, 2021 03:31
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