[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <122827b90702250857k7bcaac7eo6757fb1c45f95c2e@mail.gmail.com>
Date: Sun, 25 Feb 2007 11:57:47 -0500
From: "Stan Bubrouski" <stan.bubrouski@...il.com>
To: "Daniel Veditz" <dveditz@...zio.com>
Cc: bugtraq@...urityfocus.com, full-disclosure@...ts.grok.org.uk,
security@...illa.org
Subject: Re: [Full-disclosure] Firefox onUnload + document.write() memory corruption vulnerability (MSIE7 null ptr)
On 2/25/07, Daniel Veditz <dveditz@...zio.com> wrote:
> Michal Zalewski wrote:
> > A quick test case that crashes while trying to follow partly
> > user-dependent corrupted pointers near valid memory regions (can be forced
> > to write, too):
> >
> > http://lcamtuf.coredump.cx/ietrap/testme.html
> >
> > Firefox problem is being tracked here:
> > https://bugzilla.mozilla.org/show_bug.cgi?id=371321
>
> This bug was fixed in 2.0.0.2, released Friday Feb 23.
No it most certainly wasn't, do your homework next time.
-sb
Powered by blists - more mailing lists