lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date: Wed, 01 Oct 2014 07:32:57 -0700
From: Paul Vixie <>
To: Michal Zalewski <>
Cc: "" <>
Subject: Re: [FD] the other bash RCEs (CVE-2014-6277 and CVE-2014-6278)

michal, thank you for your incredibly informative report here. i have a
minor correction.

> Michal Zalewski <>
> Wednesday, October 01, 2014 7:21 AM
> ...
> Note: over the past few days, Florian's patch has been picked up by
> major Linux distros (Red Hat, Debian, SUSE, etc), so there is a
> reasonable probability that you are in good shape. To test, execute
> this command from within a bash shell:
> foo='() { echo not patched; }' bash -c foo

this command need not be executed from within bash. the problem occurs
when bash is run by the command, and the shell that runs the command can
be anything. for example, on a system where i have deliberately not
patched bash, where sh is "ash" (almquist shell):

> $ foo='() { echo not patched; }' bash -c foo
> not patched 

here's me testing it from within tcsh:

> % env foo='() { echo not patched; }' bash -c foo
> not patched
> % (setenv foo '() { echo not patched; }'; bash -c foo)
> not patched

this is a minor issue, but i've found in matters of security bug
reports, tests, and discussions, that any minor matter can lead to deep

thanks again for your excellent report, and your continuing work on this


Sent through the Full Disclosure mailing list
Web Archives & RSS:

Powered by blists - more mailing lists