Re: [Full-Disclosure] new ssh exploit?

From: Ron DuFresne (dufresne_at_winternet.com)
Date: 09/16/03

  • Next message: Jeff_Lopes_at_groove.net: "Re: [Full-Disclosure] New worm on port 445 ?"
    To: christopher neitzert <chris@neitzert.com>
    Date: Tue, 16 Sep 2003 10:25:47 -0500 (CDT)
    
    

    On Mon, 15 Sep 2003, christopher neitzert wrote:

    > More on this;
    >
    > The systems in question are FreeBSD, RedHat, Gentoo, and Debian all
    > running the latest versions of OpenSSH.
    >
    > The attack makes an enormous amount of ssh connections and attempts
    > various offsets until it finds one that works permitting root login.
    >
    > I have received numerous messages from folks requesting anonymity or
    > direct-off-list-reply confirming this exploit;
    >
    > The suggestions I have heard are:
    >
    > Turn off SSH and
    >
    > 1. upgrade to lsh.
    >
    > or
    >
    > 2. add explicit rules to your edge devices allowing ssh from only-known
    > hosts.

    This is perhaps the most workable and doable advise offered, the rest
    sucks <smile>.

    But, one has to remember ssh does not stand alone, at least openssh, it
    needs openssl to be properly maintained as well.

    Current openssh and old openssl can leave one hanging perhaps...

    Thanks,

    Ron DuFresne

    >
    > or
    >
    > 3. put ssh behind a VPN on RFC-1918 space.
    >
    > thanks.
    >
    >
    >
    >
    > On Mon, 2003-09-15 at 12:02, christopher neitzert wrote:
    > > Does anyone know of or have source related to a new, and unpublished ssh
    > > exploit? An ISP I work with has filtered all SSH connections due to
    > > several root level incidents involving ssh. Any information is
    > > appreciated.
    > >
    > >
    > --
    > Christopher Neitzert - GPG Key ID: 7DCC491B
    >

    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    "Cutting the space budget really restores my faith in humanity. It
    eliminates dreams, goals, and ideals and lets us get straight to the
    business of hate, debauchery, and self-annihilation." -- Johnny Hart
            ***testing, only testing, and damn good at it too!***

    OK, so you're a Ph.D. Just don't touch anything.

    _______________________________________________
    Full-Disclosure - We believe in it.
    Charter: http://lists.netsys.com/full-disclosure-charter.html


  • Next message: Jeff_Lopes_at_groove.net: "Re: [Full-Disclosure] New worm on port 445 ?"

    Relevant Pages

    • Re: two SSH compatibility scenarios: can it work?
      ... We are required to use SSH to log into the Engineering lab machines. ... > server software displays this header upon telnet connection to port 22. ... I still use Windows on my notebook for application compatibility. ... > running OpenSSH 3.4p1. ...
      (comp.security.ssh)
    • Re: OpenSSH, Telnet, Windows Authentication and double-hops
      ... deployment on a Windows network. ... Does this mean that you are setting SSH port forwarding ... does not provide the other side with either a Kerberos ticket, ... We're focusing on the OpenSSH for Windows distribution. ...
      (comp.security.ssh)
    • Re: ssh compatability issues
      ... >> without keeping two versions of ssh around on my home computer. ... running the OpenSSH server that comes with Solaris ... By 'some old security problems with that' I was not sure if you meant ...
      (comp.security.ssh)
    • Re: Solaris 9 SSH: HostbasedAuthentication?
      ... > Subject: Solaris 9 SSH: HostbasedAuthentication? ... > authentication. ... I'm gathering that the OpenSSH version it's based on didn't have ...
      (Focus-SUN)
    • Re: [openssh-unix-announce] Re: Upcoming OpenSSH vulnerability (fwd)
      ... Is OpenSSH 3.3 now part of the base system? ... older versions of ssh are vulnerable or not. ... I have to say that I side with Theo here: ... we wouldn't need OpenSSH. ...
      (FreeBSD-Security)