<div dir="ltr">On Thu, Sep 25, 2014 at 1:04 PM, Giuseppe De Marco <span dir="ltr"><<a href="mailto:demarcog83@gmail.com" target="_blank">demarcog83@gmail.com</a>></span> wrote:<br><div class="gmail_extra"><div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><span class="">2014-09-25 12:32 GMT+02:00 Saverio Proto <<a href="mailto:zioproto@gmail.com">zioproto@gmail.com</a>>:<br>
> <a href="https://securityblog.redhat.com/2014/09/24/bash-specially-crafted-environment-variables-code-injection-attack/" target="_blank">https://securityblog.redhat.com/2014/09/24/bash-specially-crafted-environment-variables-code-injection-attack/</a><br>
><br>
> <a href="http://www.exploit-db.com/exploits/34766/" target="_blank">http://www.exploit-db.com/exploits/34766/</a><br>
><br>
> Saverio<br>
<br>
</span>Azz, era dal fork bomb[1] che non si vedevano i disordini di bash.<br>
Provato su ash di openWRT, a parita di utilità risulta immune :)<br>
divago.<br>
<br>
[1] <a href="http://www.cyberciti.biz/faq/understanding-bash-fork-bomb/" target="_blank">http://www.cyberciti.biz/faq/understanding-bash-fork-bomb/</a><br></blockquote><div><br></div><div>un'opera d'arte<br><br><a href="http://www.digitalcraft.org/?artikel_id=292">http://www.digitalcraft.org/?artikel_id=292</a><br><br><br></div><br></div>
</div></div>