3 ms·

Even if you have a setuid script it appears that bash won't import functions in that case. However the fact that the script isn't setuid isn't really the conce

Even if you have a setuid script it appears that bash won't import functions in that case. However the fact that the script isn't setuid isn't really the concern for these shellshock, since a setuid program could indirectly run /bin/sh. Again, though, this doesn't seem to another shellshock problem. In shellshock you only needed to control the value of an environment variable, not its name. If you can control the name and the value then there are plenty of other ways you can attack programs.

kentonv 12y ago
> However the fact that the script isn't setuid isn't really > the concern for these shellshock, since a setuid program > could indirectly run /bin/sh. A setuid program which runs any child process without having first cleared the environment or authenticated the caller for root access is already broken by means of LD_PRELOAD.