Crashes with evidence of memory corruption (220.127.116.11)
As part of the Firefox 18.104.22.168 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
Note: Thunderbird shares the browser engine with Firefox and could be
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 RHEL3
This issue also affects RHEL2.1
*Ping* Was this bug fixed anywhere? I do not see CVE-2006-1724 listed among
the items fixed in Mozilla. Is this, perhaps, a Firefox-only bug?
*ping* Noticing that this bugzilla remains open. Hasn't Seamonkey already
been issued to replace Mozilla for the RHEL's? If so, could this bug be
closed somehow, referring folks to look at (an) RHSA for Seamonkey for the fix
to this issue?
As a matter of fact, wasn't this issue fixed with Mozilla-1.7.13 instead of
needing Seamonkey to fix it? Or was Mozilla-1.7.13 ever issued for RHEL?
Mitre's CVE-2006-1724 indicates a couple of RHSA's were issued for this issue,
but they were for:
* <http://rhn.redhat.com/errata/RHSA-2006-0328.html> Firefox, and
* <http://rhn.redhat.com/errata/RHSA-2006-0330.html> Thunderbird,
not for Mozilla/Seamonkey...
Ah. Looks like this Mozilla issue is fixed by:
Hmm, RHSA-2006:0329 doesn't list CVE-2006-1724, we'll have to look if this was
deliberate or if it's a mistake.
RHSA-2006:0329 not listing this CVE id is a mistake, I'm fixing it now. Thanks
for catching this.