Skip to content

Rubygems critical CVE #3246

May 7, 2022 · 1 comments · 1 reply
Discussion options

You must be logged in to vote

Thanks for the heads up. We lock our dependencies and review pull requests which make any updates.

Based on the advice mentioned in this advisory:

To audit your application history for possible past exploits, review your Gemfile.lock and look for gems whose platform changed when the version number did not change. For example, gemname-3.1.2 updating to gemname-3.1.2-java could indicate a possible abuse of this vulnerability.

We have not seen this happen to any of our Gemfile.lock files.

Replies: 1 comment 1 reply

Comment options

You must be logged in to vote
1 reply
@pcjmfranken
Comment options

Answer selected by pcjmfranken
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
2 participants