public inbox for ipfire-scm@lists.ipfire.org
 help / color / mirror / Atom feed
From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. e86c70a99f024c5d2973d25577ca2e657ce659db
Date: Thu, 25 Sep 2014 19:38:57 +0200	[thread overview]
Message-ID: <20140925173858.16512202A8@argus.ipfire.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 2380 bytes --]

This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "IPFire 2.x development tree".

The branch, next has been updated
       via  e86c70a99f024c5d2973d25577ca2e657ce659db (commit)
      from  a4c895e569730bb73496907c748a18a17b6045be (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
commit e86c70a99f024c5d2973d25577ca2e657ce659db
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date:   Thu Sep 25 19:38:23 2014 +0200

    bash: Import fix for CVE-2014-7169
    
    http://www.openwall.com/lists/oss-security/2014/09/25/10

-----------------------------------------------------------------------

Summary of changes:
 lfs/bash                                 |  1 +
 src/patches/bash-3.2-CVE-2014-7169.patch | 11 +++++++++++
 2 files changed, 12 insertions(+)
 create mode 100644 src/patches/bash-3.2-CVE-2014-7169.patch

Difference in files:
diff --git a/lfs/bash b/lfs/bash
index 47a6c45..58556fa 100644
--- a/lfs/bash
+++ b/lfs/bash
@@ -97,6 +97,7 @@ $(TARGET) : $(patsubst %,$(DIR_DL)/%,$(objects))
 	cd $(DIR_APP) && patch -Np1 < $(DIR_SRC)/src/patches/bash-4.0-profile-1.patch
 	cd $(DIR_APP) && patch -Np1 < $(DIR_SRC)/src/patches/bash-3.2-ssh_source_bash.patch
 	cd $(DIR_APP) && patch -Np0 < $(DIR_SRC)/src/patches/bash-3.2-CVE-2014-6271.patch
+	cd $(DIR_APP) && patch -Np0 < $(DIR_SRC)/src/patches/bash-3.2-CVE-2014-7169.patch
 
 	cd $(DIR_APP) && ./configure $(EXTRA_CONFIG)
 	cd $(DIR_APP) && make $(EXTRA_MAKE)
diff --git a/src/patches/bash-3.2-CVE-2014-7169.patch b/src/patches/bash-3.2-CVE-2014-7169.patch
new file mode 100644
index 0000000..964b91f
--- /dev/null
+++ b/src/patches/bash-3.2-CVE-2014-7169.patch
@@ -0,0 +1,11 @@
+*** ../bash-20140912/parse.y	2014-08-26 15:09:42.000000000 -0400
+--- parse.y	2014-09-24 22:47:28.000000000 -0400
+***************
+*** 2959,2962 ****
+--- 2959,2964 ----
+    word_desc_to_read = (WORD_DESC *)NULL;
+  
++   eol_ungetc_lookahead = 0;
++ 
+    current_token = '\n';		/* XXX */
+    last_read_token = '\n';


hooks/post-receive
--
IPFire 2.x development tree

                 reply	other threads:[~2014-09-25 17:38 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20140925173858.16512202A8@argus.ipfire.org \
    --to=git@ipfire.org \
    --cc=ipfire-scm@lists.ipfire.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