Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Phil Reid <preid@electromag.com.au>,
	Andrey Zhizhikin <andrey.z@gmail.com>,
	 "Armin Kuster (akuster808@gmail.com)" <akuster808@gmail.com>
Cc: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: bash: Fix CVE-2019-18276
Date: Tue, 18 Feb 2020 08:14:11 +0000	[thread overview]
Message-ID: <54127a38f14d1a3fc8ea554cce595052ec40f35c.camel@linuxfoundation.org> (raw)
In-Reply-To: <c753582b-0ba2-dbbe-df25-a9ea9cb184b6@electromag.com.au>

On Tue, 2020-02-18 at 14:41 +0800, Phil Reid wrote:
> On 17/02/2020 17:55, Richard Purdie wrote:
> > On Mon, 2020-02-17 at 07:44 +0100, Andrey Zhizhikin wrote:
> > > On Mon, Feb 17, 2020 at 4:26 AM Phil Reid <
> > > preid@electromag.com.au>
> > > wrote:
> > > > Hi All,
> > > > 
> > > > I recently started get the following failure with bash after
> > > > "b348e31c93f0 bash: Fix CVE-2019-18276"
> > > > was applied to zeus.
> > > > 
> > > > Any thoughts?
> > > > 
> > > > 
> > > > NOTE: Applying patch 'bash50-001' (downloads/bash50-001)
> > > > NOTE: Applying patch 'bash50-002' (downloads/bash50-002)
> > > > NOTE: Applying patch 'bash50-003' (downloads/bash50-003)
> > > > NOTE: Applying patch 'bash50-004' (downloads/bash50-004)
> > > > NOTE: Applying patch 'bash50-005' (downloads/bash50-005)
> > > > NOTE: Applying patch 'bash50-006' (downloads/bash50-006)
> > > > NOTE: Applying patch 'bash50-007' (downloads/bash50-007)
> > > > NOTE: Applying patch 'execute_cmd.patch' (layers/openembedded-
> > > > core/meta/recipes-extended/bash/bash/execute_cmd.patch)
> > > > NOTE: Applying patch 'mkbuiltins_have_stringize.patch'
> > > > (layers/openembedded-core/meta/recipes-
> > > > extended/bash/bash/mkbuiltins_have_stringize.patch)
> > > > NOTE: Applying patch 'build-tests.patch' (layers/openembedded-
> > > > core/meta/recipes-extended/bash/bash/build-tests.patch)
> > > > NOTE: Applying patch 'test-output.patch' (layers/openembedded-
> > > > core/meta/recipes-extended/bash/bash/test-output.patch)
> > > > NOTE: Applying patch 'fix-run-builtins.patch'
> > > > (layers/openembedded-
> > > > core/meta/recipes-extended/bash/bash/fix-run-builtins.patch)
> > > > NOTE: Applying patch 'bash-CVE-2019-18276.patch'
> > > > (layers/openembedded-core/meta/recipes-extended/bash/bash/bash-
> > > > CVE-
> > > > 2019-18276.patch)
> > > > ERROR: Command Error: 'quilt --quiltrc
> > > > /home/preid/dev/linux/v2019.11/tmp-glibc/work/cortexa9t2hf-
> > > > neon-
> > > > emit-linux-gnueabi/bash/5.0-r0/recipe-sysroot-
> > > > native/etc/quiltrc
> > > > push' exited with 0  Output:
> > > > Applying patch bash-CVE-2019-18276.patch
> > > > patching file MANIFEST
> > > > patching file bashline.c
> > > > patching file builtins/help.def
> > > > patching file config.h.in
> > > > patching file configure
> > > > Hunk #1 FAILED at 10281.
> > > > 1 out of 1 hunk FAILED -- rejects in file configure
> > > > patching file configure.ac
> > > > patching file doc/bash.1
> > > > patching file doc/bashref.texi
> > > > patching file lib/glob/glob.c
> > > > patching file pathexp.c
> > > > patching file shell.c
> > > > patching file tests/glob.tests
> > > > patching file tests/glob6.sub
> > > > patching file tests/glob7.sub
> > > > Patch bash-CVE-2019-18276.patch does not apply (enforce with
> > > > -f)
> > > > DEBUG: Python function patch_do_patch finished
> > > > DEBUG: Python function do_patch finished
> > > 
> > > Had the same issue the day before, re-building bash clean solved
> > > it.
> > > At first I wanted to report it as well, but then after I tried "-
> > > c
> > > cleanall" - the issue was gone.
> > > 
> > > Try to do a clean build of bash and see if it is still
> > > reproducible.
> > 
> > I think I understand what happens here. When you do a rebuild,
> > bitbake
> > tries to pop off all the old patches, then apply the new ones.
> > 
> > In this case its patching configure which we rebuild. It therefore
> > can't apply the new patch to configure since its changed by the
> > do_configure task.
> > 
> > The fix is to remove the configure change from the patch since we
> > just
> > need the configure.ac piece.
> > 
> I've run "bitbake -c cleanall bash" and the build has then succeeded.
> I guess we wait and see if it pops up again when bash needs to be
> rebuilt.
> 
> I did try quickly hacking the patch and removing the configure patch
> section, but the resulting configure looked different. So I went with
> the easy option above.

Reproducing should be as simple as:

bitbake bash -c configure
bitbake bash -c patch -f

Cheers,

Richard




  reply	other threads:[~2020-02-18  8:14 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-17  3:26 bash: Fix CVE-2019-18276 Phil Reid
2020-02-17  6:44 ` Andrey Zhizhikin
2020-02-17  9:55   ` Richard Purdie
2020-02-18  6:41     ` Phil Reid
2020-02-18  8:14       ` Richard Purdie [this message]
     [not found] <aa0bf5f6-aaf2-bfbf-6488-8d65cbe849f7@electromag.com.au>
     [not found] ` <4f09ab13-9571-3464-2fc3-334bc91b9c09@case.edu>
2020-02-18  2:46   ` Huo, De
     [not found]     ` <99d34efd-3a68-0b05-0e15-fbfd360a2f2a@case.edu>
2020-02-18 15:35       ` Richard Purdie
2020-02-18 15:43         ` Mittal, Anuj
2020-02-18 15:49           ` Richard Purdie
2020-02-19 15:46             ` akuster808
2020-02-19 18:55               ` Richard Purdie
2020-02-19  3:56           ` dhuo
2020-03-03  3:11           ` Yu, Mingli
2020-03-03 23:49             ` Mittal, Anuj
2020-03-04  1:16               ` Yu, Mingli
     [not found]             ` <ee8f4da6-d917-4dab-d166-62bd7dcf6142@case.edu>
2020-03-04  1:14               ` Yu, Mingli
2020-02-19  4:01       ` dhuo

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=54127a38f14d1a3fc8ea554cce595052ec40f35c.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=akuster808@gmail.com \
    --cc=andrey.z@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=preid@electromag.com.au \
    /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