The problem code is only encountered after channels are established, and
channels are never established prior to authentication, so the bug can
only be exploited by authenticated users. Even then, it's an overflow
on the heap, not the stack, so it would be difficult to exploit at all,
and extremely difficult to exploit with an outcome other than "user's
ssh session terminates".
Your best strategy on this bug for now is to ensure that the users that
have access to your server are trustworthy, or disable SSH.
Cheers,
--Rich