RubyGems is vulnerable to improper access control. A remote attacker with the ability to manipulate DNS responses could direct the gem command towards a different domain due to unsanitize DNS responses when requesting the hostname of the rubygems server for a domain resulting in DNS hijacking vulnerability.
blog.rubygems.org/2017/08/27/2.6.13-released.html
www.securityfocus.com/bid/100586
www.securitytracker.com/id/1039249
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
access.redhat.com/security/updates/classification/#moderate
bugzilla.redhat.com/show_bug.cgi?id=1506785
github.com/rubygems/rubygems/commit/8d91516fb7037ecfb27622f605dc40245e0f8d32
hackerone.com/reports/218088
lists.debian.org/debian-lts-announce/2018/07/msg00012.html
security.gentoo.org/glsa/201710-01
usn.ubuntu.com/3553-1/
usn.ubuntu.com/3685-1/
www.debian.org/security/2017/dsa-3966