On 9/12/16 10:30 AM, Franco Costantini wrote:
> By the way, we actually found more than 10 (potentially) different errors
> (judging by their backtrace), but I didn't want to spam the list. What
> would be the best way to report them?
Send them to me.
Chet
--
``The lyf so short, the craft so lo
By the way, we actually found more than 10 (potentially) different errors
(judging by their backtrace), but I didn't want to spam the list. What
would be the best way to report them?
Regards
On Sat, Sep 10, 2016 at 7:52 PM, Chet Ramey wrote:
> On 9/9/16 9:35 AM, Franco Costantini wrote:
> > Hi,
On 9/9/16 9:35 AM, Franco Costantini wrote:
> Hi,
>
> we recently found an invalid memory access parsing and executing fuzzed
> bash code in GNU Bash 4.4.0 (bash-20160826 snapshot, found in
> http://git.savannah.gnu.org/cgit/bash.git/commit/?h=devel&id=79eedac429c5112ae65a430674de5e4be1cd5444).
T
On Sep 09 2016, Franco Costantini wrote:
> We tested this issue on Ubuntu 14.04.5 (x86_64) but other configurations
> could be affected. To reproduce it, compilation with Address Sanitizer is
> required:
valgrind also finds the same error.
Andreas.
--
Andreas Schwab, sch...@linux-m68k.org
GPG
Hi,
we recently found an invalid memory access parsing and executing fuzzed
bash code in GNU Bash 4.4.0 (bash-20160826 snapshot, found in
http://git.savannah.gnu.org/cgit/bash.git/commit/?h=devel&id=79eedac429c5112ae65a430674de5e4be1cd5444
).
We tested this issue on Ubuntu 14.04.5 (x86_64) but oth