Back to list
Re: [oss-security] Bug in bash <= 4.3 [security feature bypassed]
Jun 04 2014 09:13AM
Jose Carlos Luna Duran (jose carlos luna gmail com)
In my opinion the drop of privs in bash was mostly a "help" measure
for poorly written setuid programs executing system() calls. I don't
think is the role of bash to do this as the problem that could be
exploited by that would really be in the original program that does
not drop privs before invoking the shell. This has been known for some
time in some circles at least, but as I said the problem would really
be in the non-priv-dropping privileged program, that's why most people
did not really care that much. Last year there was a vuln that is very
much related to this subject:
Correct me if I'm wrong, but even in that case there is another "help"
measure that has been implemented at least in linux kernels > 3.1:
Therefore setuid calls do not fail anymore even in the case of
existing resource limits for processes (in linux).
But in any case, for the sake of correctness I agree that the
drop_priv code should be fixed (or just completely removed...).
2014-06-03 16:16 GMT+02:00 Hector Marco <hecmargi (at) upv (dot) es [email concealed]>:
> Hi everyone,
> Recently we discovered a bug in bash. After some time after reporting
> it to bash developers, it has not been fixed.
> We think that this is a security issue because in some circumstances
> the bash security feature could be bypassed allowing the bash to be a
> valid target shell in an attack.
> We strongly recommend to patch your bash code.
> Why don't fix this bug by simple adding mandatory "if" clause ?
> Any comments about this issue are welcomed.
> Details at:
> Thanks you,
> Hector Marco
Jose Carlos Luna Duran
Network Software Engineering.
Jose.Carlos.Luna (at) gmail (dot) com [email concealed]
[ reply ]
Copyright 2010, SecurityFocus