Skip to content
Noroxi
CVE-2015-4020· NVD / CVE Program· CNA mitre

RubyGems 2.0.x before 2.0.17, 2.2.x before 2.2.5, and 2.4.x before 2.4.8 does not validate the hostname when fetching gems or making API req

RubyGems 2.0.x before 2.0.17, 2.2.x before 2.2.5, and 2.4.x before 2.4.8 does not validate the hostname when fetching gems or making API requests, which allows remote attackers to redirect requests to arbitrary domains via a crafted DNS SRV record with a domain that is suffixed with the original domain name, aka a "DNS hijack attack." NOTE: this vulnerability exists because to an incomplete fix for CVE-2015-3900.

MediumCVSS 4.3 · v2.0—No exploit Fix available
Published
Aug 25, 2015
Updated
Jun 16, 2026
EPSS
3.5% · 89th 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

18

Monitor

Low priority for now.

CVSS
17 / 40 · 4.3 / 10
CISA KEV
0 / 30 · Not listed
EPSS
1 / 30 · 3.5%

Noroxi analysis

No Noroxi analysis for this record yet

We don't hand-write analysis for the hundreds of thousands of vulnerabilities in the database; 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

Affected systems

VendorProduct
rubygemsrubygems
oraclesolaris

Affected versions

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

  • oracle solaris11.3
  • rubygems rubygems2.0.0
  • rubygems rubygems2.0.1
  • rubygems rubygems2.0.10
  • rubygems rubygems2.0.11
  • rubygems rubygems2.0.12
  • rubygems rubygems2.0.13
  • rubygems rubygems2.0.14
  • rubygems rubygems2.0.15
  • rubygems rubygems2.0.16
  • rubygems rubygems2.0.2
  • rubygems rubygems2.0.3
  • rubygems rubygems2.0.4
  • rubygems rubygems2.0.5
  • rubygems rubygems2.0.6
  • rubygems rubygems2.0.7
  • rubygems rubygems2.0.8
  • rubygems rubygems2.0.9
  • rubygems rubygems2.2.0
  • rubygems rubygems2.2.1

Package-level exposure

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

EcosystemPackageAffected rangeFix
RubyGemsrubygems-updatefrom 2.1.0.rc.1 · before 2.2.52.2.5
RubyGemsrubygems-updatefrom 2.3.0 · before 2.4.82.4.8
RubyGemsrubygems-updatebefore 2.0.172.0.17

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
  • 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

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
RubyGems:rubygems-update2.0.17Package registry (OSV)
RubyGems:rubygems-update2.2.5Package registry (OSV)
RubyGems:rubygems-update2.4.8Package 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

Change log

  1. Fix✗ → ✓

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

References

All records