Bugtraq mailing list archives
Re: BUG in /bin/bash
From: mevans () inficad com (The Ghost who Admins)
Date: Thu, 22 Aug 1996 18:09:25 -0700
I got the same output on a BSDI box running BASH version 1.14.5(1) This probably means that the version of BASH that we are running is ok. The bug was with the ASCII character value of 255 being a command separator. It is a bug only if the BASH version you are running on separates the ls and who commands and runs them both separatly. since ours did not separate the commands, we are ok. Mike Evans <mevans () inficad com> On Thu, 22 Aug 1996, Red Barchetta wrote:
Their test string "bash -c 'ls\377who'" gave this output on my Solaris 2.5 system: bash: ls377who: command not found Can anyone verify that this is really a problem? Ernie Pistor
Current thread:
- BUG in /bin/bash Seven Up (Aug 22)
- <Possible follow-ups>
- Re: BUG in /bin/bash Red Barchetta (Aug 22)
- Re: BUG in /bin/bash The Ghost who Admins (Aug 22)
- Re: BUG in /bin/bash Digital Dreamer (Aug 22)
- Re: BUG in /bin/bash Earle Ake (Aug 22)
- IE 3.0? InterAccess Support Manager (Aug 22)
- Re: IE 3.0? Dave Andersen (Aug 23)
- More on the UnixWare problem Todd Vierling (Aug 23)
- resolv+ and finger... C. Hodges (Aug 23)
- Vulnerability in the Xt library Aleph One (Aug 24)
- Re: Vulnerability in the Xt library Stefan `Sec` Zehl (Aug 25)
- Re: Vulnerability in the Xt library Mike Neuman (Aug 27)
- Re: Vulnerability in the Xt library Casper Dik (Aug 28)