When using cat on some files, the files put stuff on the commnand line
that gets executed the next time you hit return.
Here is an example with my prompt set to XXX for clarity
I first cat -A the file to show what special characters the file contains.
Note that the high bit is set. vi shows this as ~Z
XXXcat -A junk
M-^Z$
XXXcat junk
^[[?1;2cXXX1;2c
1: Command not found.
2c: Command not found.
XXX
This could potentially be a security problem if there was a command called
2c or just 1 (Yeah, minor but cat shouldn't execute stuff none the less,
and I did not look into other high bit characters).
We find this on both Alpha linux and x86 linux (both redhat).
Kurt Glaesemann
p.s. This bug does not exist in vendor supplied versions of cat on AIX and
IRIX.
