CVE-2017-0903: RubyGems versions between 2.0.0 and 2.6.13 are vulnerable to a possible remote code execution vulnerability.
Noroxi assessment
Priority: Plan (action score 44/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: 15.8% (FIRST EPSS); higher than 96.9% of all records.
- 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.
- Fixed version: rubygems (Debian:12) 3.2.0~rc.1-1; ruby2.1 (Debian:8) 2.1.5-2+deb8u4; ruby2.3 (Debian:9) 2.3.3-1+deb9u2.
Add it to your regular patch cycle. Upgrade to rubygems (Debian:12) 3.2.0~rc.1-1; ruby2.1 (Debian:8) 2.1.5-2+deb8u4; ruby2.3 (Debian:9) 2.3.3-1+deb9u2 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 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.
- Published
- Oct 11, 2017
- Updated
- Jun 16, 2026
- EPSS
- 15.8% · 96th percentile
- CWE
- CWE-502
Report tools
Action score
44
Add it to your regular patch cycle.
- CVSS
- 39 / 40 · 9.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 5 / 30 · 15.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.
Is your version affected? Check itNoroxi 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 helpAffected 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.
| Vendor | Product | CPE |
|---|---|---|
| rubygems | rubygems | cpe:2.3:a:rubygems:rubygems |
| debian | debian linux | cpe:2.3:o:debian:debian_linux |
| canonical | ubuntu linux | cpe:2.3:o:canonical:ubuntu_linux |
| redhat | enterprise linux desktop | cpe:2.3:o:redhat:enterprise_linux_desktop |
| redhat | enterprise linux server | cpe:2.3:o:redhat:enterprise_linux_server |
| redhat | enterprise linux server aus | cpe:2.3:o:redhat:enterprise_linux_server_aus |
| redhat | enterprise linux server eus | cpe:2.3:o:redhat:enterprise_linux_server_eus |
| redhat | enterprise linux server tus | cpe:2.3:o:redhat:enterprise_linux_server_tus |
| redhat | enterprise linux workstation | cpe:2.3:o:redhat:enterprise_linux_workstation |
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
Affected versions · NVD (20)
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
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | rubygems | before 3.2.0~rc.1-1 | 3.2.0~rc.1-1 |
| Debian:8 | ruby2.1 | before 2.1.5-2+deb8u4 | 2.1.5-2+deb8u4 |
| Debian:9 | ruby2.3 | before 2.3.3-1+deb9u2 | 2.3.3-1+deb9u2 |
| Red Hat:enterprise_linux:7::client | ruby | before 0:2.0.0.648-33.el7_4 | 0:2.0.0.648-33.el7_4 |
| Red Hat:enterprise_linux:7::client | ruby-debuginfo | before 0:2.0.0.648-33.el7_4 | 0:2.0.0.648-33.el7_4 |
| Red Hat:enterprise_linux:7::client | ruby-devel | before 0:2.0.0.648-33.el7_4 | 0:2.0.0.648-33.el7_4 |
| Red Hat:enterprise_linux:7::client | ruby-doc | before 0:2.0.0.648-33.el7_4 | 0:2.0.0.648-33.el7_4 |
| Red Hat:enterprise_linux:7::client | ruby-irb | before 0:2.0.0.648-33.el7_4 | 0:2.0.0.648-33.el7_4 |
| Red Hat:enterprise_linux:7::client | ruby-libs | before 0:2.0.0.648-33.el7_4 | 0:2.0.0.648-33.el7_4 |
| Red Hat:enterprise_linux:7::client | ruby-tcltk | before 0:2.0.0.648-33.el7_4 | 0:2.0.0.648-33.el7_4 |
| Red Hat:enterprise_linux:7::client | rubygem-bigdecimal | before 0:1.2.0-33.el7_4 | 0:1.2.0-33.el7_4 |
| Red Hat:enterprise_linux:7::client | rubygem-io-console | before 0:0.4.2-33.el7_4 | 0:0.4.2-33.el7_4 |
| Red Hat:enterprise_linux:7::client | rubygem-json | before 0:1.7.7-33.el7_4 | 0:1.7.7-33.el7_4 |
| Red Hat:enterprise_linux:7::client | rubygem-minitest | before 0:4.3.2-33.el7_4 | 0:4.3.2-33.el7_4 |
| Red Hat:enterprise_linux:7::client | rubygem-psych | before 0:2.0.0-33.el7_4 | 0:2.0.0-33.el7_4 |
| Red Hat:enterprise_linux:7::client | rubygem-rake | before 0:0.9.6-33.el7_4 | 0:0.9.6-33.el7_4 |
| Red Hat:enterprise_linux:7::client | rubygem-rdoc | before 0:4.0.0-33.el7_4 | 0:4.0.0-33.el7_4 |
| Red Hat:enterprise_linux:7::client | rubygems | before 0:2.0.14.1-33.el7_4 | 0:2.0.14.1-33.el7_4 |
| Red Hat:enterprise_linux:7::client | rubygems-devel | before 0:2.0.14.1-33.el7_4 | 0:2.0.14.1-33.el7_4 |
| Red Hat:rhel_software_collections:3::el6 | rh-ruby22-ruby | before 0:2.2.9-19.el6 | 0:2.2.9-19.el6 |
| Red Hat:rhel_software_collections:3::el6 | rh-ruby22-ruby-debuginfo | before 0:2.2.9-19.el6 | 0:2.2.9-19.el6 |
| Red Hat:rhel_software_collections:3::el6 | rh-ruby22-ruby-devel | before 0:2.2.9-19.el6 | 0:2.2.9-19.el6 |
| Red Hat:rhel_software_collections:3::el6 | rh-ruby22-ruby-doc | before 0:2.2.9-19.el6 | 0:2.2.9-19.el6 |
| Red Hat:rhel_software_collections:3::el6 | rh-ruby22-ruby-irb | before 0:2.2.9-19.el6 | 0:2.2.9-19.el6 |
+96
Same product
rubygems: all recordsOther 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…40Plan
- CVE-2017-0901RubyGems version 2.6.12 and earlier fails to validate specification names, allowing a maliciously crafted gem to potentially overwrite any…39Monitor
Published before and after this one in the same product
- ← EarlierCVE-2017-0900Aug 31, 2017 · RubyGems version 2.6.12 and earlier is vulnerable to maliciously crafted gem specifications to cause a denial of service attack against…33Monitor
- ← 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
- Later →CVE-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…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 / package | Fixed version | Source |
|---|---|---|
| debian:ruby2.1 | 2.1.5-2+deb8u4 · Debian:8 | Package registry (OSV) |
| debian:ruby2.3 | 2.3.3-1+deb9u2 · Debian:9 | Package registry (OSV) |
| debian:rubygems | 3.2.0~rc.1-1 · Debian:12 | Package registry (OSV) |
| red hat:rh-ruby24-ruby | 0:2.4.2-86.el6 · Red Hat:rhel_software_collections:3::el6 | Package registry (OSV) |
| red hat:rh-ruby24-ruby-debuginfo | 0:2.4.2-86.el6 · Red Hat:rhel_software_collections:3::el6 | Package registry (OSV) |
| red hat:rh-ruby24-ruby-devel | 0:2.4.2-86.el6 · Red Hat:rhel_software_collections:3::el6 | Package registry (OSV) |
| red hat:rh-ruby24-ruby-doc | 0:2.4.2-86.el6 · Red Hat:rhel_software_collections:3::el6 | Package registry (OSV) |
| red hat:rh-ruby24-ruby-irb | 0:2.4.2-86.el6 · Red Hat:rhel_software_collections:3::el6 | Package registry (OSV) |
| red hat:rh-ruby24-ruby-libs | 0:2.4.2-86.el6 · Red Hat:rhel_software_collections:3::el6 | Package registry (OSV) |
| red hat:rh-ruby24-rubygem-bigdecimal | 0:1.3.0-86.el6 · Red Hat:rhel_software_collections:3::el6 | Package registry (OSV) |
| red hat:rh-ruby24-rubygem-did_you_mean | 0:1.1.0-86.el6 · Red Hat:rhel_software_collections:3::el6 | Package registry (OSV) |
| red hat:rh-ruby24-rubygem-io-console | 0:0.4.6-86.el6 · Red Hat:rhel_software_collections:3::el6 | Package registry (OSV) |
| red hat:rh-ruby24-rubygem-json | 0:2.0.4-86.el6 · Red Hat:rhel_software_collections:3::el6 | Package registry (OSV) |
| red hat:rh-ruby24-rubygem-minitest | 0:5.10.1-86.el6 · Red Hat:rhel_software_collections:3::el6 | Package registry (OSV) |
| red hat:rh-ruby24-rubygem-net-telnet | 0:0.1.1-86.el6 · Red Hat:rhel_software_collections:3::el6 | Package registry (OSV) |
| RubyGems:rubygems-update | 2.6.14 | Package registry (OSV) |
| suse:ruby2.1 | 2.1.9-19.3.2 · SUSE:HPE Helion OpenStack 8 | Package registry (OSV) |
| suse:yast2-ruby-bindings | 3.1.53-9.8.1 · SUSE:OpenStack Cloud 7 | Package 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.
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Not on record for this CVE: EPSS history · researcher credit · variant or chain candidate · public bounty 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
Weakness class (CWE)
CWE-502 · Deserialization of Untrusted DataCVSS 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.
The bug in code
The whole CWE-502 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
payload = sock.recv(65536)
job = pickle.loads(payload)Fixed
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.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (12 more)Show less
- blog.rubygems.org/2017/10/09/unsafe-object-deserialization-vulnerability.html
- www.securityfocus.com/bid/101275
- access.redhat.com/errata/RHSA-2017:3485
- access.redhat.com/errata/RHSA-2018:0378
- access.redhat.com/errata/RHSA-2018:0583
- access.redhat.com/errata/RHSA-2018:0585
- github.com/rubygems/rubygems/commit/510b1638ac9bba3ceb7a5d73135dafff9e5bab49
- hackerone.com/reports/274990
- lists.debian.org/debian-lts-announce/2018/07/msg00012.html
- usn.ubuntu.com/3553-1/
- usn.ubuntu.com/3685-1/
- www.debian.org/security/2017/dsa-4031
Vendor advisories and official records. Exploit/PoC links are deliberately left out.