bugtraq - (Fw) : mIRC 6.12 (latest) DCC Exploit

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Date: 23 Oct 2003 17:05:10 -0000
From: K-OTiK Security <Special-Alerts@...tik.com>
To: bugtraq@...urityfocus.com
Subject: (Fw) : mIRC 6.12 (latest) DCC Exploit

this news was found on irchelp, DCC Exploit Affecting mIRC 6.12 :

another exploit was identified which can crash even the recently released version 6.12. It only seems to affect people who minimize DCC get dialog windows (manually or by default), and then open those windows to get a file with an excessively long filename. You can't be crashed unless that sequence of events occurs. That manual step is required. If you auto-get the file, or don't get the file at all, nothing happens. 

If and only if you think the above affects you, then here is a temporary fix which should be pasted in your "remotes" section (alt-r to access). It basically rejects any excessively long filename. 

ctcp *:dcc send:*: if ($len($nopath($filename)) >= 225) { echo 4 -s $nick tried to crash you with an illegal dcc send of $nopath($filename) | halt } 

or this shorter version without the warning message: 

ctcp *:dcc send:*: if ($len($nopath($filename)) >= 225) halt 

If you are not comfortable with modifying your remotes, you can just ignore all incoming DCC sends with the following, which is the same temporary fix as for the other bug described in the next section: 

/ignore -wd * 

You can undo the above command by /ignore -rwd * (note the r for remove).

Regards.

K-OTik Staff /// http://www.k-otik.com