|
Greetings,
If you initiate a "icq chat" with someone on licq then proceed to send a constant stream of characters (I usually send close to 1000 chars) right after one another it will cause their licq to segmentation fault. Tested on licq 1.0.4 (Slackware 8.0, kernel 2.4.17) The end result after the flood is:
licq Segmentation Violation Detected. Backtrace: licq(licq_handle_sigsegv+0x73) [0x809171b] /lib/libpthread.so.0(pthread_kill+0x170)
[0x4002deb4]
/lib/libc.so.6(__libc_sigaction+0x1f8) [0x400ce928] licq(PopChatEvent__12CChatManager+0xab) [0x808ab2b] /usr/local/lib/licq/licq_qt-gui.so(slot_chat__7ChatDlg+0xea6) [0x401fb68a] /usr/lib/libqt.so.2(activate_signal__7QObjectPCci+0x12a) [0x40448b7e] /usr/lib/libqt.so.2(activated__15QSocketNotifieri+0x28) [0x4049a0b8] /usr/lib/libqt.so.2(event__15QSocketNotifierP6QEvent+0x44) [0x4047b07c] /usr/lib/libqt.so.2(notify__12QApplicationP7QObjectP6QEvent+0x1ea) 0x403f88a6] /usr/lib/libqt.so.2(qt_set_socket_handler__FiiP7QObjectb+0x4f2) [0x403c685a] /usr/lib/libqt.so.2(processNextEvent__12QApplicationb+0x6c7) [0x403c6f9b] /usr/lib/libqt.so.2(enter_loop__12QApplication+0x3c) [0x403fa5f4] /usr/lib/libqt.so.2(exec__12QApplication+0x2b) [0x403c68c7] /usr/local/lib/licq/licq_qt-gui.so(Run__8CLicqGuiP10CICQDaemon+0xf9) [0x402070ed] /usr/local/lib/licq/licq_qt-gui.so(LP_Main+0x4d) [0x40205475] /usr/local/lib/licq/licq_qt-gui.so(LP_Main_tep+0x21) [0x40205191] /lib/libpthread.so.0(pthread_detach+0x519) [0x4002b065] /lib/libc.so.6(__clone+0x3a) [0x4016d01a] Attempting to generate core file. syn@slackware:~# Follow Up:
Jon Keating ([EMAIL PROTECTED]) posted a patch and
some extra information to the SecurityFocus bugtraq mailing list today
and it can be viewed at:
I would also like to apologize for not sending
this directly to the devel mailing list but instead sending it to the
sourceforge bug report page, followed by the bugtraq mailing
list.
Cheers,
Pat H.
|
