OSEC

Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com
 
From: Stanley G. Bubrouski (stanCCS.NEU.EDU)
Date: Tue Feb 20 2001 - 15:19:36 CST

  • Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

    Author: Stan Bubrouski (stanccs.neu.edu)
    Date: February 20, 2001
    Package: Licq
    Versions affected: v.85 and v1.0.2 and possibly previous or newer versions.
    Severity: Remote user's can cause Licq to crash or lock up completely.

    Problems: While testing Licq back in December it became apparent to me that
    Licq could be made to crash consistently if a certain amount of data is
    sent to a port it is listening on. Further testing showed that sending a
    certain amount of data to the port the Remote Management Service (RMS)
    plugin listens on it too would cause Licq to crash or lock up. The
    amount of data needed to be sent to crash Licq may vary from system to
    system. On the Red Hat linux 7.0 system I used 16707 or more bytes sent
    to the port Licq was listening on was enough to crash it. Sending around
    12000 or more characters to the RMS plugin port was enough to crash Licq
    on my system as well. I've attached a simple exploit to demonstrate the
    DoS. I haven't tested any versions newer than 1.0.2 but they should be
    assumed vulnerable as well.

    Copyright 2001 Stan Bubrouski

    --
    Stan Bubrouski                                       stanccs.neu.edu
    316 Huntington Ave. Apt #676, Boston, MA 02115       (617) 377-7222