Skip to content

Update jruby to 9.3.8.0 because of CVE-2022-25857 #7

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

Closed
wants to merge 2 commits into from

Conversation

ylecuyer
Copy link

Upgrade jruby because it transitively download jruby-stdlib which bundles a jar of snakeyaml containing CVE-2022-25857

Upgrade jruby because it transitively download jruby-stdlib which bundles a jar of snakeyaml containing CVE-2022-25857
@ylecuyer
Copy link
Author

ylecuyer commented Sep 16, 2022

Btw torquebox.org has been defaced and it breaks the CI pipeleine 🤷‍♂️

@ylecuyer
Copy link
Author

Found this tweet https://mobile.twitter.com/jruby/status/1216832621000282112 pointing at the alternative but it looks like it wasn't longterm in the end :(

Screenshot_2022-09-16_14-12-48

@headius headius added this to the 2.0 milestone Aug 2, 2023
@headius
Copy link
Member

headius commented Aug 2, 2023

I have an update happening in #9 to JRuby 9.4.3 so I think this is not an issue anymore.

The repository proxies will never go back up because mavengem works fine; #9 also updates it to use newer rubygems.org APIs.

@headius
Copy link
Member

headius commented Aug 8, 2023

Resolved via #9.

@headius headius closed this Aug 8, 2023
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