Skip to content
Noroxi
CVE-2017-0903· NVD / CVE Program· CNA hackerone

RubyGems versions between 2.0.0 and 2.6.13 are vulnerable to a possible remote code execution vulnerability.

RubyGems versions between 2.0.0 and 2.6.13 are vulnerable to a possible remote code execution vulnerability. YAML deserialization of gem specifications can bypass class white lists. Specially crafted serialized objects can possibly be used to escalate to remote code execution.

CriticalCVSS 9.8 · v3.0—No exploit Fix available
Published
Oct 11, 2017
Updated
Jun 16, 2026
EPSS
15.9% · 97th percentile
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

Report tools

JSON

Action score

44

Plan

Add it to your regular patch cycle.

CVSS
39 / 40 · 9.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
5 / 30 · 15.9%

Affected systems

VendorProduct
rubygemsrubygems
debiandebian linux
canonicalubuntu linux
redhatenterprise linux desktop
redhatenterprise linux server
redhatenterprise linux server aus
redhatenterprise linux server eus
redhatenterprise linux server tus
redhatenterprise linux workstation

Affected versions

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

  • canonical ubuntu linux14.04
  • canonical ubuntu linux16.04
  • canonical ubuntu linux17.10
  • debian debian linux8.0
  • debian debian linux9.0
  • redhat enterprise linux desktop7.0
  • redhat enterprise linux server7.0
  • redhat enterprise linux server aus7.4
  • redhat enterprise linux server aus7.6
  • redhat enterprise linux server eus7.4
  • redhat enterprise linux server eus7.5
  • redhat enterprise linux server eus7.6
  • redhat enterprise linux server tus7.4
  • redhat enterprise linux server tus7.6
  • redhat enterprise linux workstation7.0
  • rubygems rubygems2.0.0
  • rubygems rubygems2.0.1
  • rubygems rubygems2.0.10
  • rubygems rubygems2.0.11
  • rubygems rubygems2.0.12

Versions reported by the vendor

Affected version ranges reported by the assigning authority (hackerone). Independent of NVD's CPE analysis and usually ahead of it.

  • HackerOne RubyGems

    • Versions >= 2.0.0affected

Package-level exposure

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

EcosystemPackageAffected rangeFix
Debian:12rubygemsbefore 3.2.0~rc.1-13.2.0~rc.1-1
Debian:8ruby2.1before 2.1.5-2+deb8u42.1.5-2+deb8u4
Debian:9ruby2.3before 2.3.3-1+deb9u22.3.3-1+deb9u2
Red Hat:enterprise_linux:7::clientrubybefore 0:2.0.0.648-33.el7_40:2.0.0.648-33.el7_4
Red Hat:enterprise_linux:7::clientruby-debuginfobefore 0:2.0.0.648-33.el7_40:2.0.0.648-33.el7_4
Red Hat:enterprise_linux:7::clientruby-develbefore 0:2.0.0.648-33.el7_40:2.0.0.648-33.el7_4
Red Hat:enterprise_linux:7::clientruby-docbefore 0:2.0.0.648-33.el7_40:2.0.0.648-33.el7_4
Red Hat:enterprise_linux:7::clientruby-irbbefore 0:2.0.0.648-33.el7_40:2.0.0.648-33.el7_4
Red Hat:enterprise_linux:7::clientruby-libsbefore 0:2.0.0.648-33.el7_40:2.0.0.648-33.el7_4
Red Hat:enterprise_linux:7::clientruby-tcltkbefore 0:2.0.0.648-33.el7_40:2.0.0.648-33.el7_4
Red Hat:enterprise_linux:7::clientrubygem-bigdecimalbefore 0:1.2.0-33.el7_40:1.2.0-33.el7_4
Red Hat:enterprise_linux:7::clientrubygem-io-consolebefore 0:0.4.2-33.el7_40:0.4.2-33.el7_4
Red Hat:enterprise_linux:7::clientrubygem-jsonbefore 0:1.7.7-33.el7_40:1.7.7-33.el7_4
Red Hat:enterprise_linux:7::clientrubygem-minitestbefore 0:4.3.2-33.el7_40:4.3.2-33.el7_4
Red Hat:enterprise_linux:7::clientrubygem-psychbefore 0:2.0.0-33.el7_40:2.0.0-33.el7_4
Red Hat:enterprise_linux:7::clientrubygem-rakebefore 0:0.9.6-33.el7_40:0.9.6-33.el7_4
Red Hat:enterprise_linux:7::clientrubygem-rdocbefore 0:4.0.0-33.el7_40:4.0.0-33.el7_4
Red Hat:enterprise_linux:7::clientrubygemsbefore 0:2.0.14.1-33.el7_40:2.0.14.1-33.el7_4
Red Hat:enterprise_linux:7::clientrubygems-develbefore 0:2.0.14.1-33.el7_40:2.0.14.1-33.el7_4
Red Hat:rhel_software_collections:3::el6rh-ruby22-rubybefore 0:2.2.9-19.el60:2.2.9-19.el6
Red Hat:rhel_software_collections:3::el6rh-ruby22-ruby-debuginfobefore 0:2.2.9-19.el60:2.2.9-19.el6
Red Hat:rhel_software_collections:3::el6rh-ruby22-ruby-develbefore 0:2.2.9-19.el60:2.2.9-19.el6
Red Hat:rhel_software_collections:3::el6rh-ruby22-ruby-docbefore 0:2.2.9-19.el60:2.2.9-19.el6
Red Hat:rhel_software_collections:3::el6rh-ruby22-ruby-irbbefore 0:2.2.9-19.el60:2.2.9-19.el6

+96

Other highest-scoring records for the same primary product.

  • 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
  • CVE-2017-0901RubyGems version 2.6.12 and earlier fails to validate specification names, allowing a maliciously crafted gem to potentially overwrite any f
    39Monitor
  • CVE-2019-8324An issue was discovered in RubyGems 2.6 and later through 3.0.2.
    36Monitor
  • CVE-2022-36073RubyGems allows creation of users with arbitrary unverified emails
    35Monitor
  • CVE-2017-0902RubyGems version 2.6.12 and earlier is vulnerable to a DNS hijacking vulnerability that allows a MITM attacker to force the RubyGems client
    33Monitor

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
debian:ruby2.12.1.5-2+deb8u4 · Debian:8Package registry (OSV)
debian:ruby2.32.3.3-1+deb9u2 · Debian:9Package registry (OSV)
debian:rubygems3.2.0~rc.1-1 · Debian:12Package registry (OSV)
red hat:rh-ruby24-ruby0:2.4.2-86.el6 · Red Hat:rhel_software_collections:3::el6Package registry (OSV)
red hat:rh-ruby24-ruby-debuginfo0:2.4.2-86.el6 · Red Hat:rhel_software_collections:3::el6Package registry (OSV)
red hat:rh-ruby24-ruby-devel0:2.4.2-86.el6 · Red Hat:rhel_software_collections:3::el6Package registry (OSV)
red hat:rh-ruby24-ruby-doc0:2.4.2-86.el6 · Red Hat:rhel_software_collections:3::el6Package registry (OSV)
red hat:rh-ruby24-ruby-irb0:2.4.2-86.el6 · Red Hat:rhel_software_collections:3::el6Package registry (OSV)
red hat:rh-ruby24-ruby-libs0:2.4.2-86.el6 · Red Hat:rhel_software_collections:3::el6Package registry (OSV)
red hat:rh-ruby24-rubygem-bigdecimal0:1.3.0-86.el6 · Red Hat:rhel_software_collections:3::el6Package registry (OSV)
red hat:rh-ruby24-rubygem-did_you_mean0:1.1.0-86.el6 · Red Hat:rhel_software_collections:3::el6Package registry (OSV)
red hat:rh-ruby24-rubygem-io-console0:0.4.6-86.el6 · Red Hat:rhel_software_collections:3::el6Package registry (OSV)
red hat:rh-ruby24-rubygem-json0:2.0.4-86.el6 · Red Hat:rhel_software_collections:3::el6Package registry (OSV)
red hat:rh-ruby24-rubygem-minitest0:5.10.1-86.el6 · Red Hat:rhel_software_collections:3::el6Package registry (OSV)
red hat:rh-ruby24-rubygem-net-telnet0:0.1.1-86.el6 · Red Hat:rhel_software_collections:3::el6Package registry (OSV)
RubyGems:rubygems-update2.6.14Package registry (OSV)
suse:ruby2.12.1.9-19.3.2 · SUSE:HPE Helion OpenStack 8Package 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

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • No user action is required.
  • 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
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

CVSS vector

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/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

—

Noroxi analysis

No Noroxi analysis for this record yet

We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

We use this product, ask for help

Change log

  1. Fix✗ → ✓

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

References

All records