Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 188798 - CVE-2006-1724 Crashes with evidence of memory corruption (
CVE-2006-1724 Crashes with evidence of memory corruption (
Product: Fedora
Classification: Fedora
Component: mozilla (Show other bugs)
All Linux
medium Severity urgent
: ---
: ---
Assigned To: Christopher Aillon
Ben Levenson
: Security
Depends On:
  Show dependency treegraph
Reported: 2006-04-12 22:26 EDT by Josh Bressers
Modified: 2007-11-30 17:11 EST (History)
2 users (show)

See Also:
Fixed In Version: FEDORA-2006-487
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-10-02 08:40:14 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Josh Bressers 2006-04-12 22:26:08 EDT
Crashes with evidence of memory corruption (

As  part of the Firefox release we fixed several crash bugs to
improve the stability of the product, with a particular focus on finding
crashes caused by DHTML. Some of these crashes showed evidence of memory
corruption that we presume could be exploited to run arbitrary code with
enough effort.

Note:  Thunderbird shares the browser engine with Firefox and could be
vulnerable if JavaScript were to be enabled in mail. This is not the default
setting and we strongly discourage users from running JavaScript in mail.


Upgrade to the fixed versions. Do not enable JavaScript in Thunderbird or
the mail portion of SeaMonkey.


Also fixed in Firefox/Thunderbird 1.0.8, Mozilla Suite 1.7.13
Muck with the boxobject's internal frame pointer.

This issue also affects FC4
Comment 1 Josh Bressers 2006-04-24 08:49:59 EDT
Lifting embargo
Comment 2 David Eisenstein 2006-10-02 08:24:36 EDT
So was this ever fixed in FC5?  FC4?  With Seamonkey, maybe?
Comment 3 David Eisenstein 2006-10-02 08:40:14 EDT
Ah.  I see that this was indeed fixed on 2006-05-03, for both FC4 and FC5
(but not mentioned in the advisories.)  The update to Mozilla-1.7.13 fixed
this issue along with the others mentioned.

This bug was fixed for FC4 in Fedora Update FEDORA-2006-488

This bug was fixed for FC5 in Fedora Update FEDORA-2006-487

Going ahead and closing this ERRATA.

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