First published: Wed Jun 24 2015(Updated: )
RubyGems 2.0.x before 2.0.16, 2.2.x before 2.2.4, and 2.4.x before 2.4.7 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, aka a "DNS hijack attack."
Credit: cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
rubygems/rubygems-update | >=2.4.0<2.4.7 | 2.4.7 |
rubygems/rubygems-update | >=2.2.0<2.2.4 | 2.2.4 |
rubygems/rubygems-update | >=2.0.0<2.0.16 | 2.0.16 |
Ruby | =1.9 | |
Ruby | =1.9.1 | |
Ruby | =1.9.2 | |
Ruby | =1.9.3 | |
Ruby | =2.0.0 | |
Ruby | =2.1 | |
Ruby | =2.1.1 | |
Ruby | =2.1.2 | |
Ruby | =2.1.3 | |
Ruby | =2.1.4 | |
Ruby | =2.1.5 | |
Ruby | =2.2.0 | |
RubyGems | =2.0.0 | |
RubyGems | =2.0.1 | |
RubyGems | =2.0.2 | |
RubyGems | =2.0.3 | |
RubyGems | =2.0.4 | |
RubyGems | =2.0.5 | |
RubyGems | =2.0.6 | |
RubyGems | =2.0.7 | |
RubyGems | =2.0.8 | |
RubyGems | =2.0.9 | |
RubyGems | =2.0.10 | |
RubyGems | =2.0.11 | |
RubyGems | =2.0.12 | |
RubyGems | =2.0.13 | |
RubyGems | =2.0.14 | |
RubyGems | =2.0.15 | |
RubyGems | =2.2.0 | |
RubyGems | =2.2.1 | |
RubyGems | =2.2.2 | |
RubyGems | =2.2.3 | |
RubyGems | =2.4.0 | |
RubyGems | =2.4.1 | |
RubyGems | =2.4.2 | |
RubyGems | =2.4.3 | |
RubyGems | =2.4.4 | |
RubyGems | =2.4.5 | |
RubyGems | =2.4.6 | |
Oracle Solaris and Zettabyte File System (ZFS) | =11.3 | |
Red Hat Enterprise Linux | =6.0 | |
Red Hat Enterprise Linux | =7.0 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2015-3900 has a moderate severity rating due to the potential for DNS hijack attacks.
To fix CVE-2015-3900, upgrade RubyGems to version 2.0.16, 2.2.4, or 2.4.7 or later.
CVE-2015-3900 affects RubyGems versions 2.0.x before 2.0.16, 2.2.x before 2.2.4, and 2.4.x before 2.4.7.
CVE-2015-3900 exploits vulnerabilities in RubyGems' hostname validation when fetching gems or making API requests.
Users of RubyGems versions prior to the patched versions are at risk of being impacted by CVE-2015-3900.