BugTraq
0day: mIRC pwns Windows Oct 03 2007 04:06PM
jinc4fareijj hotmail com (2 replies)
Re: 0day: mIRC pwns Windows Oct 03 2007 07:59PM
Gavin Hanover (netmunky gmail com) (1 replies)
is this a mirc bug or a mail client bug?

on systems with thunderbird installed, this opens a new mail window to %xx...
on systems with outlook/outlook express, this opens calc.exe
(both using mirc 6.3)

similar behavior as clicking start -> run and pasting the URI

regardless, unless you can pass arbitrary arguements or pass data on
to a server, i don't think you're going to find many already existing
executables on the user's system to do malicious tasks with this "mirc
bug". various tests can't even get notepad to open a simple txt file.
you can't even run shutdown.exe without specifying some arguments.

research kills frivolous 0day announcements.

On 3 Oct 2007 16:06:29 -0000, jinc4fareijj (at) hotmail (dot) com [email concealed]
<jinc4fareijj (at) hotmail (dot) com [email concealed]> wrote:
> Yipiya Ypipiya yah yeah. Here is a 0day! hurra mIRC pwns your Windozes! (ref. pdp)
>
> send this to a user and make him double click on it (masquerade it with pink fore/background color and say 'free pr0n click here ->' it works all the time! damned perverts):
> mailto:%xx../../../../../../../../../../../windows/system32/calc.exe".ba
t
>
> Now the question is, should we say *0day* for a bug in a core element that is WELL KNOWN by everyone (reported months ago), and will be patched, or should we try to get credits for finding a *vector* as pdp did with the supposed *acrobat reader pdf bug* ?
>
> Fame kills bugs.
>

--
In God we trust,
Everyone else must have an x.509 certificate.

[ reply ]
Re[2]: 0day: mIRC pwns Windows Oct 04 2007 11:12AM
3APA3A (3APA3A SECURITY NNOV RU) (2 replies)
Re: 0day: mIRC pwns Windows Oct 04 2007 04:04PM
Greg Rubin (grrubin gmail com)
Re: Re[2]: 0day: mIRC pwns Windows Oct 04 2007 01:47PM
Gavin Hanover (netmunky gmail com)
Re: 0day: mIRC pwns Windows Oct 03 2007 06:47PM
Gregory Rubin (grrubin gmail com)


 

Privacy Statement
Copyright 2010, SecurityFocus