From: Mark Hatle <mark.hatle@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: [PATCH] Bash bug fixes and CVE updates
Date: Fri, 3 Oct 2014 09:51:24 -0500 [thread overview]
Message-ID: <1412347885-57716-1-git-send-email-mark.hatle@windriver.com> (raw)
Use the official community fixes by patching to the latest patch level.
The key patches for the active CVEs are listed below:
bash32-052 CVE-2014-6271 9/24/2014
bash32-053 CVE-2014-7169 9/26/2014
bash32-054 exported function namespace change 9/27/2014
bash32-055 CVE-2014-7186/CVE-2014-7187 10/1/2014
bash32-056 CVE-2014-6277 10/2/2014
bash43-025 CVE-2014-6271 9/24/2014
bash43-026 CVE-2014-7169 9/26/2014
bash43-027 exported function namespace change 9/27/2014
bash43-028 CVE-2014-7186/CVE-2014-7187 10/1/2014
bash43-029 CVE-2014-6277 10/2/2014
I am still in the process of validating the before and after behavior of
bash using the ptests, I'll let the list know once the tests have been
completed.
Mark Hatle (1):
bash: Upgrade bash to latest patch level to fix CVEs
.../bash/bash-3.2.48/cve-2014-6271.patch | 77 --------------
.../bash/bash-3.2.48/cve-2014-7169.patch | 16 ---
.../recipes-extended/bash/bash/cve-2014-6271.patch | 114 ---------------------
.../recipes-extended/bash/bash/cve-2014-7169.patch | 16 ---
meta/recipes-extended/bash/bash_3.2.48.bb | 38 ++++---
meta/recipes-extended/bash/bash_4.3.bb | 90 +++++++++++++++-
6 files changed, 112 insertions(+), 239 deletions(-)
delete mode 100644 meta/recipes-extended/bash/bash-3.2.48/cve-2014-6271.patch
delete mode 100644 meta/recipes-extended/bash/bash-3.2.48/cve-2014-7169.patch
delete mode 100644 meta/recipes-extended/bash/bash/cve-2014-6271.patch
delete mode 100644 meta/recipes-extended/bash/bash/cve-2014-7169.patch
--
1.9.3
next reply other threads:[~2014-10-03 14:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-03 14:51 Mark Hatle [this message]
2014-10-03 14:51 ` [PATCH] bash: Upgrade bash to latest patch level to fix CVEs Mark Hatle
2014-10-03 21:02 ` [PATCH] Bash bug fixes and CVE updates Mark Hatle
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=1412347885-57716-1-git-send-email-mark.hatle@windriver.com \
--to=mark.hatle@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
/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