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

Vulnerability in rack 2.2.8, openssl 3.1.0 #132

Closed
2 of 3 tasks
milda-a opened this issue Feb 27, 2024 · 1 comment · Fixed by #133
Closed
2 of 3 tasks

Vulnerability in rack 2.2.8, openssl 3.1.0 #132

milda-a opened this issue Feb 27, 2024 · 1 comment · Fixed by #133

Comments

@milda-a
Copy link

milda-a commented Feb 27, 2024

Pre issue-raising checklist

I have already (please mark the applicable with an x):

  • Upgraded to the latest version of the relevant libraries
  • Checked to see if the issue has already been raised
  • Created an executable example that demonstrates the issue using either:

Software versions

  • pact-ruby-standalone: eg 2.4.1

Expected behaviour

Vulnerabilities fixed by updating the used rack version. Current version: 2.2.8 Versions with fix: 2.2.8.1, 3.0.9.1
Vulnerabilities fixed by updating the used openssl version. Current version 3.1.0 Versions with fix: 3.1.5, 3.2.1

Actual behaviour

High vulnerabilities raised in /home/builder/deps/pact/lib/vendor/ruby/3.2.0/specifications/rack-2.2.8.gemspec
Warn vulnerabilities raised in /home/builder/deps/pact/lib/ruby/lib/ruby/gems/3.2.0/specifications/default/openssl-3.1.0.gemspec

Steps to reproduce

Run software as normal. Vulnerabilities spotted through internal image scanning which includes the pact standalone binaries.

@YOU54F
Copy link
Member

YOU54F commented Feb 27, 2024

Hey, thanks for raising.

Unfortunately openssl 3.1.0 gem is a default gem installed with Ruby so we would need a 3.2.4 release of Ruby containing the updated default gem

https://www.ruby-lang.org/en/news/2022/12/25/ruby-3-2-0-released/

Same news for 3.3.0 - as it contains openssl 3.2.0 default gem.

You may wish to raise a separate issue upstream with the ruby team, if one hasn't already been raised. Once a release is out, we can package it with traveling-ruby and consume it in this project.

I've updated the rack gem. We would need to check the upstream pact ruby project's rack deps, update and test if required, before we can unpin from v2.x in pact-ruby-standalone

You may want to raise a separate issue to track the openssl issue, as this one will be closed with the rack release.

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 a pull request may close this issue.

2 participants