Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] patch: add upstream security fix
Date: Mon, 9 Apr 2018 20:59:17 +0200	[thread overview]
Message-ID: <20180409205917.4bf6a8d3@windsurf> (raw)
In-Reply-To: <653d97fd8ac542e3eac3c0a78dc701a7033ba39a.1523290836.git.baruch@tkos.co.il>

Hello,

On Mon,  9 Apr 2018 19:20:36 +0300, Baruch Siach wrote:
> Fixes CVE-2018-1000156: arbitrary command execution in ed-style patches.
> 
> Depend on MMU for now, because the patch adds a fork() call. Upstream
> later switched to gnulib provided execute(), so this dependency can be
> dropped on the next version bump.
> 
> Signed-off-by: Baruch Siach <baruch@tkos.co.il>
> ---
>  ...-files-to-be-missing-for-ed-style-patches.patch |  37 +++++
>  ...ry-command-execution-in-ed-style-patches-.patch | 157 +++++++++++++++++++++
>  package/patch/Config.in                            |   2 +
>  3 files changed, 196 insertions(+)
>  create mode 100644 package/patch/0002-Allow-input-files-to-be-missing-for-ed-style-patches.patch
>  create mode 100644 package/patch/0003-Fix-arbitrary-command-execution-in-ed-style-patches-.patch

Applied to master, thanks.

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com

  reply	other threads:[~2018-04-09 18:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-09 16:20 [Buildroot] [PATCH] patch: add upstream security fix Baruch Siach
2018-04-09 18:59 ` Thomas Petazzoni [this message]
2018-04-09 19:07 ` Peter Korsgaard
2018-04-10 20:48 ` 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=20180409205917.4bf6a8d3@windsurf \
    --to=thomas.petazzoni@bootlin.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