Skip to content
Noroxi
CVE-2018-1000074· NVD / CVE Program· CNA mitre

RubyGems version Ruby 2.2 series: 2.2.9 and earlier, Ruby 2.3 series: 2.3.6 and earlier, Ruby 2.4 series: 2.4.3 and earlier, Ruby 2.5 series

Noroxi assessment

Priority: Monitor (action score 32/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 2.8% (FIRST EPSS); higher than 86.6% of all records.
  • Someone with local access to the system can trigger it. No account or password is required. A user must open a link or visit a page. No special conditions are required; it is repeatable.
  • Fixed version: n/a n/a 2.7.6.

Low priority for now. Upgrade to n/a n/a 2.7.6 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

RubyGems version Ruby 2.2 series: 2.2.9 and earlier, Ruby 2.3 series: 2.3.6 and earlier, Ruby 2.4 series: 2.4.3 and earlier, Ruby 2.5 series: 2.5.0 and earlier, prior to trunk revision 62422 contains a Deserialization of Untrusted Data vulnerability in owner command that can result in code execution. This attack appear to be exploitable via victim must run the `gem owner` command on a gem with a specially crafted YAML file. This vulnerability appears to have been fixed in 2.7.6.

HighCVSS 7.8 · v3.0—No exploit Fix available
Published
Mar 13, 2018
Updated
Jun 16, 2026
EPSS
2.8% · 86th percentile

Report tools

JSON

Action score

32

Monitor

Low priority for now.

CVSS
31 / 40 · 7.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
1 / 30 · 2.8%

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2018-1000074

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
rubygemsrubygems

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • rubygems rubygemsup to 2.2.9 inclusive
  • rubygems rubygemsup to 2.3.6 inclusive
  • rubygems rubygemsup to 2.4.3 inclusive
  • rubygems rubygemsup to 2.5.0 inclusive

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12jrubybefore 9.1.17.0-19.1.17.0-1
Debian:12rubygemsbefore 3.2.0~rc.1-13.2.0~rc.1-1
Debian:7jrubybefore 1.5.6-5+deb7u21.5.6-5+deb7u2
Debian:8jrubybefore 1.5.6-9+deb8u11.5.6-9+deb8u1
Debian:8ruby2.1before 2.1.5-2+deb8u52.1.5-2+deb8u5
Debian:9jrubybefore 1.7.26-1+deb9u11.7.26-1+deb9u1
Debian:9ruby2.3before 2.3.3-1+deb9u32.3.3-1+deb9u3
Mavenorg.jruby:jruby-stdlibbefore 9.1.16.09.1.16.0
Mavenorg.jruby:jruby-stdlibbefore 9.1.16.09.1.16.0
openSUSE:Leap 15.0ruby-bundled-gems-rpmhelperbefore 0.0.2-lp151.2.10.0.2-lp151.2.1
openSUSE:Leap 15.0ruby2.5before 2.5.5-lp151.4.3.12.5.5-lp151.4.3.1
Red Hat:enterprise_linux:7::clientrubybefore 0:2.0.0.648-36.el70:2.0.0.648-36.el7
Red Hat:enterprise_linux:7::clientruby-debuginfobefore 0:2.0.0.648-36.el70:2.0.0.648-36.el7
Red Hat:enterprise_linux:7::clientruby-develbefore 0:2.0.0.648-36.el70:2.0.0.648-36.el7
Red Hat:enterprise_linux:7::clientruby-docbefore 0:2.0.0.648-36.el70:2.0.0.648-36.el7
Red Hat:enterprise_linux:7::clientruby-irbbefore 0:2.0.0.648-36.el70:2.0.0.648-36.el7
Red Hat:enterprise_linux:7::clientruby-libsbefore 0:2.0.0.648-36.el70:2.0.0.648-36.el7
Red Hat:enterprise_linux:7::clientruby-tcltkbefore 0:2.0.0.648-36.el70:2.0.0.648-36.el7
Red Hat:enterprise_linux:7::clientrubygem-bigdecimalbefore 0:1.2.0-36.el70:1.2.0-36.el7
Red Hat:enterprise_linux:7::clientrubygem-io-consolebefore 0:0.4.2-36.el70:0.4.2-36.el7
Red Hat:enterprise_linux:7::clientrubygem-jsonbefore 0:1.7.7-36.el70:1.7.7-36.el7
Red Hat:enterprise_linux:7::clientrubygem-minitestbefore 0:4.3.2-36.el70:4.3.2-36.el7
Red Hat:enterprise_linux:7::clientrubygem-psychbefore 0:2.0.0-36.el70:2.0.0-36.el7
Red Hat:enterprise_linux:7::clientrubygem-rakebefore 0:0.9.6-36.el70:0.9.6-36.el7

+96

Other highest-scoring records for the same primary product.

  • CVE-2017-0903RubyGems versions between 2.0.0 and 2.6.13 are vulnerable to a possible remote code execution vulnerability.
    44Plan
  • CVE-2017-0899RubyGems version 2.6.12 and earlier is vulnerable to maliciously crafted gem specifications that include terminal escape characters.
    42Plan
  • CVE-2018-1000076RubyGems version Ruby 2.2 series: 2.2.9 and earlier, Ruby 2.3 series: 2.3.6 and earlier, Ruby 2.4 series: 2.4.3 and earlier, Ruby 2.5 series
    40Plan

Published before and after this one in the same product

  • ← EarlierCVE-2017-0902Aug 31, 2017 · RubyGems version 2.6.12 and earlier is vulnerable to a DNS hijacking vulnerability that allows a MITM attacker to force the RubyGems client
    33Monitor
  • ← EarlierCVE-2018-1000073Mar 13, 2018 · RubyGems version Ruby 2.2 series: 2.2.9 and earlier, Ruby 2.3 series: 2.3.6 and earlier, Ruby 2.4 series: 2.4.3 and earlier, Ruby 2.5 series
    31Monitor
  • Later →CVE-2018-1000075Mar 13, 2018 · RubyGems version Ruby 2.2 series: 2.2.9 and earlier, Ruby 2.3 series: 2.3.6 and earlier, Ruby 2.4 series: 2.4.3 and earlier, Ruby 2.5 series
    31Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
n/a n/a2.7.6 · descriptionVendor (CNA)
debian:jruby9.1.17.0-1 · Debian:12Package registry (OSV)
debian:ruby2.12.1.5-2+deb8u5 · Debian:8Package registry (OSV)
debian:ruby2.32.3.3-1+deb9u3 · Debian:9Package registry (OSV)
debian:rubygems3.2.0~rc.1-1 · Debian:12Package registry (OSV)
Maven:org.jruby:jruby-stdlib9.1.16.0Package registry (OSV)
opensuse:ruby-bundled-gems-rpmhelper0.0.2-lp151.2.1 · openSUSE:Leap 15.0Package registry (OSV)
opensuse:ruby2.52.5.5-lp151.4.3.1 · openSUSE:Leap 15.0Package registry (OSV)
red hat:rh-ruby23-ruby0:2.3.8-69.el6 · Red Hat:rhel_software_collections:3::el6Package registry (OSV)
red hat:rh-ruby23-ruby-debuginfo0:2.3.8-69.el6 · Red Hat:rhel_software_collections:3::el6Package registry (OSV)
red hat:rh-ruby23-ruby-devel0:2.3.8-69.el6 · Red Hat:rhel_software_collections:3::el6Package registry (OSV)
red hat:rh-ruby23-ruby-doc0:2.3.8-69.el6 · Red Hat:rhel_software_collections:3::el6Package registry (OSV)
red hat:rh-ruby23-ruby-irb0:2.3.8-69.el6 · Red Hat:rhel_software_collections:3::el6Package registry (OSV)
red hat:rh-ruby23-ruby-libs0:2.3.8-69.el6 · Red Hat:rhel_software_collections:3::el6Package registry (OSV)
red hat:rh-ruby23-ruby-tcltk0:2.3.8-69.el6 · Red Hat:rhel_software_collections:3::el6Package registry (OSV)
red hat:rh-ruby23-rubygem-bigdecimal0:1.2.8-69.el6 · Red Hat:rhel_software_collections:3::el6Package registry (OSV)
red hat:rh-ruby23-rubygem-did_you_mean0:1.0.0-69.el6 · Red Hat:rhel_software_collections:3::el6Package registry (OSV)
red hat:rh-ruby23-rubygem-io-console0:0.4.5-69.el6 · Red Hat:rhel_software_collections:3::el6Package registry (OSV)
red hat:rh-ruby23-rubygem-json0:1.8.3.1-69.el6 · Red Hat:rhel_software_collections:3::el6Package registry (OSV)
red hat:rh-ruby23-rubygem-minitest0:5.8.5-69.el6 · Red Hat:rhel_software_collections:3::el6Package registry (OSV)
RubyGems:rubygems-update2.7.6Package registry (OSV)
suse:ruby2.12.1.9-19.3.2 · SUSE:HPE Helion OpenStack 8Package registry (OSV)
suse:ruby2.52.5.5-4.3.1 · SUSE:Linux Enterprise Module for Basesystem 15Package registry (OSV)
suse:yast2-ruby-bindings3.1.53-9.8.1 · SUSE:OpenStack Cloud 7Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • No account or password is required.
  • A user must open a link or visit a page.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
None
User interaction
Required
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

CVSS vector

CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

nvd-primary

Root cause

Data received over the network is deserialized into the language’s native object format without verifying its source. Code paths inside the object can be triggered during deserialization.

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

python
payload = sock.recv(65536)job = pickle.loads(payload)

Fixed

python
payload = sock.recv(65536)if not hmac.compare_digest(sign(payload), header_sig):    raise PermissionError("invalid signature")job = JobSchema.validate(json.loads(payload))

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

ATT&CK techniques

—

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records