Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] ruby: add upstream security patches bumping rubygems to 2.6.13
Date: Thu, 21 Sep 2017 13:17:57 +0200	[thread overview]
Message-ID: <878th8wba2.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20170907091755.9491-1-peter@korsgaard.com> (Peter Korsgaard's message of "Thu, 7 Sep 2017 11:17:55 +0200")

>>>>> "Peter" == Peter Korsgaard <peter@korsgaard.com> writes:

 > We unfortunately cannot use the upstream patches directly as they are not in
 > 'patch -p1' format, so convert them and include instead.

 > Fixes:

 > CVE-2017-0899 - RubyGems version 2.6.12 and earlier is vulnerable to
 > maliciously crafted gem specifications that include terminal escape
 > characters.  Printing the gem specification would execute terminal escape
 > sequences.

 > CVE-2017-0900 - RubyGems version 2.6.12 and earlier is vulnerable to
 > maliciously crafted gem specifications to cause a denial of service attack
 > against RubyGems clients who have issued a `query` command.

 > CVE-2017-0901 - RubyGems version 2.6.12 and earlier fails to validate
 > specification names, allowing a maliciously crafted gem to potentially
 > overwrite any file on the filesystem.

 > CVE-2017-0902 - RubyGems version 2.6.12 and earlier is vulnerable to a DNS
 > hijacking vulnerability that allows a MITM attacker to force the RubyGems
 > client to download and install gems from a server that the attacker
 > controls.

 > For more details, see
 > https://www.ruby-lang.org/en/news/2017/08/29/multiple-vulnerabilities-in-rubygems/

 > Signed-off-by: Peter Korsgaard <peter@korsgaard.com>

Committed to 2017.02.x, thanks.

-- 
Bye, Peter Korsgaard

  parent reply	other threads:[~2017-09-21 11:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-07  9:17 [Buildroot] [PATCH] ruby: add upstream security patches bumping rubygems to 2.6.13 Peter Korsgaard
2017-09-09 20:48 ` Thomas Petazzoni
2017-09-21 11:17 ` Peter Korsgaard [this message]
2017-10-16 21:53 ` Peter Korsgaard

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=878th8wba2.fsf@dell.be.48ers.dk \
    --to=peter@korsgaard.com \
    --cc=buildroot@busybox.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox