Re: Re: [Full-disclosure] Microsoft Windows XP/2003/Vista memory corruption 0day

2006-12-22 Thread Mike
Well, Just a warning b4 running the proof of concept... Make sure to close and save useful stuff. It indeed works on xp sp2 and it will reboot your machiene. I have to say, This would be trick to exploit another programs messagebox, and wha joy could you possibly get out of restarting someone

RE: [Full-disclosure] Microsoft Windows XP/2003/Vista memory corruption 0day

2006-12-22 Thread Michele Cicciotti
Holy mackerel! Instances of this bug date back to 1999! Different bug. That appears to be a trivial exhaustion of CSRSS worker threads through indiscriminate calls to MessageBox+MB_SERVICE_NOTIFICATION, which causes a DoS as no threads are available to serve kernel-mode requests from win32k,

Microsoft Windows XP/2003/Vista memory corruption 0day

2006-12-21 Thread 3APA3A
Dear full-disclosure@lists.grok.org.uk, Since it's already wide spread on the public forums and exploit is published on multiple sites and there is no way to stop it, I think it's time to alert lists about this. On the one of Russian forums:

Re: [Full-disclosure] Microsoft Windows XP/2003/Vista memory corruption 0day

2006-12-21 Thread 3APA3A
Dear lists, in another Russian forum, Killer{R} made analysis on this issue using Windows 2000 sources: http://bugtraq.ru/cgi-bin/forum.mcgi?type=sbb=21m=140672 The problem is in win32k.sys' function GetHardErrorText, which tries to prepare EXCEPTION data for event log, and seems to be

Re: [Full-disclosure] Microsoft Windows XP/2003/Vista memory corruption 0day

2006-12-21 Thread Alexander Sotirov
3APA3A wrote: Killer{R} assumes the problem is in strcpy(), because it should not be used for overlapping buffers, but at least ANSI implementation of strcpy from Visual C should be safe in this very situation (copying to lower addresses). May be code is different for Windows XP or

Re: [Full-disclosure] Microsoft Windows XP/2003/Vista memory corruption 0day

2006-12-21 Thread Pukhraj Singh
Holy mackerel! Instances of this bug date back to 1999! http://groups.google.ca/group/microsoft.public.win32.programmer.kernel/browse_thread/thread/c5946bf40f227058/7bd7b5d66a4e5aff --Pukhraj On 12/21/06, Alexander Sotirov [EMAIL PROTECTED] wrote: 3APA3A wrote: Killer{R} assumes the