bugtraq
[Top] [All Lists]

Firefox onUnload + document.write() memory corruption vulnerability (MSI

To: bugtraq@securityfocus.com
Subject: Firefox onUnload + document.write() memory corruption vulnerability (MSIE7 null ptr)
From: Michal Zalewski <lcamtuf@dione.ids.pl>
Date: Fri, 23 Feb 2007 02:36:44 +0100 (CET)
Cc: full-disclosure@lists.grok.org.uk, security@mozilla.org
Delivered-to: sp-com-lists@consult.net
Delivered-to: bugtraq-list@securepoint.com
Delivered-to: mailing list bugtraq@securityfocus.com
Delivered-to: moderator for bugtraq@securityfocus.com
List-help: <mailto:bugtraq-help@securityfocus.com>
List-id: <bugtraq.list-id.securityfocus.com>
List-post: <mailto:bugtraq@securityfocus.com>
List-subscribe: <mailto:bugtraq-subscribe@securityfocus.com>
List-unsubscribe: <mailto:bugtraq-unsubscribe@securityfocus.com>
Mailing-list: contact bugtraq-help@securityfocus.com; run by ezmlm
While researching my previous report on MSIE7 browser entrapment, I
noticed that Firefox is susceptible to a pretty nasty, and apparently
easily exploitable memory corruption vulnerability. When a location
transition occurs and the structure of a document is modified from within
onUnload event handler, freed memory structures are left in inconsistent
state, possibly leading to a remote compromise.

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

This also crashes MSIE7 with a seemingly harmless NULL pointer bug (didn't
research it - do your homework).

Firefox problem is being tracked here:
  https://bugzilla.mozilla.org/show_bug.cgi?id=371321

/mz

<Prev in Thread] Current Thread [Next in Thread>