From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/ruby: security bump to version 2.4.6
Date: Wed, 24 Apr 2019 22:30:27 +0200 [thread overview]
Message-ID: <87mukf6t98.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20190416213340.14880-1-peter@korsgaard.com> (Peter Korsgaard's message of "Tue, 16 Apr 2019 23:33:40 +0200")
>>>>> "Peter" == Peter Korsgaard <peter@korsgaard.com> writes:
> Fixes the following security issues:
> - CVE-2019-8320: Delete directory using symlink when decompressing tar
> - CVE-2019-8321: Escape sequence injection vulnerability in verbose
> - CVE-2019-8322: Escape sequence injection vulnerability in gem owner
> - CVE-2019-8323: Escape sequence injection vulnerability in API response handling
> - CVE-2019-8324: Installing a malicious gem may lead to arbitrary code execution
> - CVE-2019-8325: Escape sequence injection vulnerability in errors
> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
Committed to 2019.02.x, thanks.
--
Bye, Peter Korsgaard
prev parent reply other threads:[~2019-04-24 20:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-16 21:33 [Buildroot] [PATCH] package/ruby: security bump to version 2.4.6 Peter Korsgaard
2019-04-17 6:42 ` Thomas Petazzoni
2019-04-24 20:30 ` Peter Korsgaard [this message]
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=87mukf6t98.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