Home page logo

oss-sec logo oss-sec mailing list archives

Re: rubygems insecure download (and other problems)
From: Donald Stufft <donald () stufft io>
Date: Wed, 14 Aug 2013 17:02:36 -0400

On Aug 14, 2013, at 4:59 PM, Kurt Seifried <kseifried () redhat com> wrote:

Signed PGP part
I don't think this is CVE worthy, but it is worth fixing and not
putting everyone at such risk:


Problem #1:
install /etc/gemrc to install gems via https rather than http

everyone should be enabling HTTPS where possible, intercepting and
modifying HTTP is trivial.

Problem #2:
it redirects to  production.cf.rubygems.org which is on cloudfront so
has certificate mismatch, so either users have to accept insecurity,
or... well there is no second choice =(.


- -- 
Kurt Seifried Red Hat Security Response Team (SRT)
PGP: 0x5E267993 A90B F995 7350 148F 66BF 7554 160D 4553 5E26 7993

pip has a CVE for downloading via HTTP, does switching the
gem to HTTPS actually make gem verify it?


Donald Stufft
PGP: 0x6E3CBCE93372DCFA // 7C6B 7C5D 5E2B 6356 A926 F04F 6E3C BCE9 3372 DCFA

Attachment: signature.asc
Description: Message signed with OpenPGP using GPGMail

  By Date           By Thread  

Current thread:
[ Nmap | Sec Tools | Mailing Lists | Site News | About/Contact | Advertising | Privacy ]