Bug 448364 (CVE-2008-2419) - CVE-2008-2419 firefox: heap corruption during Iframe operations between a JSframe write and a JSframe close
Summary: CVE-2008-2419 firefox: heap corruption during Iframe operations between a JSf...
Keywords:
Status: CLOSED NOTABUG
Alias: CVE-2008-2419
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
high
high
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL: http://nvd.nist.gov/nvd.cfm?cvename=C...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-05-26 09:25 UTC by Tomas Hoger
Modified: 2019-09-29 12:24 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-04-08 21:45:54 UTC
Embargoed:


Attachments (Terms of Use)

Description Tomas Hoger 2008-05-26 09:25:34 UTC
Common Vulnerabilities and Exposures assigned an identifier CVE-2008-2419 to the following vulnerability:

Mozilla Firefox 2.0.0.14 allows remote attackers to cause a denial of
service (heap corruption and application crash) or possibly execute
arbitrary code by triggering an error condition during certain Iframe
operations between a JSframe write and a JSframe close, as
demonstrated by an error in loading an empty Java applet defined by a
'src="javascript:"' sequence.

References:
http://www.0x000000.com/?i=576
http://www.securityfocus.com/bid/29318
http://xforce.iss.net/xforce/xfdb/42589

Comment 1 Vincent Danen 2010-04-08 21:45:54 UTC
It is possible that this could affect Seamonkey 1.1.x, however there is no further information available on this issue, and it looks like it may only affect Windows.  It also looks as though this issue may be more related to the java interpreter than to firefox itself.  Regardless, upstream is unable to reproduce or determine this to be security significant in firefox itself.

https://bugzilla.mozilla.org/show_bug.cgi?id=323026
https://bugzilla.mozilla.org/show_bug.cgi?id=275783
https://bugzilla.mozilla.org/show_bug.cgi?id=256763


Note You need to log in before you can comment on or make changes to this bug.