Re: Buffer Overflow

2022-04-12 Thread Greg Wooledge
On Tue, Apr 12, 2022 at 02:45:15PM -0400, Sergio Fuentes wrote: > Please, run the following 3 commands to reproduce the bug: > > echo '. ./poc.sh' > poc.sh > chmod +x poc.sh > bash -c './poc.sh' You're performing an infinite recursion. Eventually, you'll overflow the stack, and bash will crash.

Re: Buffer Overflow

2022-04-12 Thread Dennis Williamson
On Tue, Apr 12, 2022, 3:18 PM Sergio Fuentes < fuentes.sergio.nov2...@gmail.com> wrote: > Hello, > > Please, run the following 3 commands to reproduce the bug: > > echo '. ./poc.sh' > poc.sh > chmod +x poc.sh > bash -c './poc.sh' > > The backtrace from gdb: > gdb /bin/bash core > ... > Program ter

Re: Buffer Overflow

2022-04-12 Thread Chet Ramey
On 4/12/22 2:45 PM, Sergio Fuentes wrote: > Hello, > > Please, run the following 3 commands to reproduce the bug: > > echo '. ./poc.sh' > poc.sh > chmod +x poc.sh > bash -c './poc.sh' You've created infinite recursion using `.' and run yourself out of stack space. This isn't a bug. You can set

Buffer Overflow

2022-04-12 Thread Sergio Fuentes
Hello, Please, run the following 3 commands to reproduce the bug: echo '. ./poc.sh' > poc.sh chmod +x poc.sh bash -c './poc.sh' The backtrace from gdb: gdb /bin/bash core ... Program terminated with signal SIGSEGV, Segmentation fault. #0 0x5612fcdece65 in yyparse () (gdb) bt #0 0x5612f