CVE-2018-1000076: RubyGems Improper Verification of Cryptographic Signature vulnerability

CVE-2018-1000076 · Severity: low · CVSS 3 · Published 2022-05-14

RubyGems Improper Verification of Cryptographic Signature vulnerability

Technologies: org.jruby:jruby-stdlib (Maven), rubygems-update (RubyGems). Vendors: Maven, RubyGems.

Quick answers

Is CVE-2018-1000076 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2018-1000076 being exploited in the wild.
How severe is CVE-2018-1000076?
Low severity, with a CVSS score of 3, published 14 May 2022.
Which products and versions are affected?
org.jruby:jruby-stdlib (Maven) ECOSYSTEM:introduced=0,fixed=9.1.16.0; rubygems-update (RubyGems) ECOSYSTEM:introduced=2.2.0,fixed=2.7.6.
Is there a fix for CVE-2018-1000076?
Yes. org.jruby:jruby-stdlib (Maven): upgrade to 9.1.16.0 or later; rubygems-update (RubyGems): upgrade to 2.7.6 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2018-1000076?
Check whether you run org.jruby:jruby-stdlib (Maven) or rubygems-update (RubyGems) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • org.jruby:jruby-stdlib (Maven): upgrade to 9.1.16.0 or later
    # set org.jruby:jruby-stdlib to 9.1.16.0 in your pom.xml or build.gradle
  • rubygems-update (RubyGems): upgrade to 2.7.6 or later
    bundle update rubygems-update

Affected products

  • org.jruby:jruby-stdlib (Maven) ECOSYSTEM:introduced=0,fixed=9.1.16.0
  • rubygems-update (RubyGems) ECOSYSTEM:introduced=2.2.0,fixed=2.7.6

Identifiers

  • CVE-2018-1000076
  • GHSA-mc6j-h948-v2p6

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.