I just throught i'd post it on here, it has come to my attention that the following versions of openssh are vulnerable, and to my understanding, they are also installed by default on redhat 7.2 and FreeBSD 4.5. The exploit must be done by someone with an account (to my understanding heh), so you can't get remote rooted unless they have some level of access to your system, but it's still a definite threat, and this vulnerability will grant them root privaledges. I won't explain anything more about it really, no need to give script kiddies a helping hand, but if you've got the following, i would strongly recommend an upgrade:

Versions:

ssh 1.5-openssh1.2.3 through ssh1.9-openssh2.9.2

Details of the problems can be found here (http://online.securityfocus.com/search?submit=yes&category=23&order=DESC&query=OpenSSH&offset=10)

FreeBSD advisory (from March 7) here:
ftp://ftp.freebsd.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-02:13.openssh.asc

It is/was actually a zlib bug, but translated into an OpenSSH hole. It is easy enough to upgrade to 3.x OpenSSH if you don't use RPM. If you use RPM you have to upgrade about 10 packages and it is a royal pain.

Oh, were we talking about the zlib bug? In that case, FreeBSD is unaffected -- linux is the only operating system with the required broken malloc for the zlib bug to be a danger.

The OpenSSH and zlib bugs are two separate issues.

The zlib bug doesn't have an effect on FreeBSD:Unlike some implementations of malloc(3)/free(3), the malloc(3) and
free(3) routines used in FreeBSD (aka phkmalloc, written by
Poul-Henning Kamp <phk@FreeBSD.org>), are not vulnerable to this type
of bug.taken from: ftp://ftp.freebsd.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-02:18.zlib.asc

The OpenSSH bug is different and related to session management or something similar, indeed affecting FreeBSD.