Marc, I've just upgraded to 4.3.7-ubuntu1.2 in trusty
(https://launchpad.net/ubuntu/+source/bash/4.3-7ubuntu1.2) which I
assume was supposed to protect against the test case provided for
CVE-2014-7169. It doesn't appear to have done so. Confirmed that the
upgrade was successfully applied.
harry@ma
Re the above: the patch was *not* correctly applied in trusty package
bash_4.3-7ubuntu1.2.
lucid package bash_4.3-7ubuntu1.2 appears to have been upgraded fine,
and handles the test case correctly.
harry@mars:~$ md5sum Downloads/bash_4.3-7ubuntu1.1_amd64/bin/bash
Downloads/bash_4.3-7ubuntu1.2_am
As per comment #5 on bug #1373781, the executables appear not to have
been updated to their patched versions (forgot to recompile, I guess?)
before the packages were generated.
Appears to be the case all bash and bash-static packages of the
4.3-7ubuntu1.2 ilk.
--
You received this bug notificati
It's the infinite loop of trapped SIGTERMs that raises this exception,
and can be performed in any way that deliberately infinitely loops a
signal trap.
$ bash -c 'trap "kill 0" EXIT SIGTERM'
Segmentation fault (core dumped)
$ bash -c 'trap "kill $$" EXIT SIGTERM'
Segmentation fault (core dumped)
So, after some browsing, it apears that trap recursion was introduced
intentionally in 4.3-rc2. There is commented code in bash.c that makes
it look like trap recursion was originally intended to be a configurable
build option, but was made default behaviour instead.
One fairly easy fix would be t
5 matches
Mail list logo
