Vulnerability Note VU#815432

Mozilla XML.prototype.hasOwnProperty() method memory corruption vulnerability

Original Release date: 08 Nov 2006 | Last revised: 21 Dec 2006

Overview

Mozilla products fail to properly handle the XML.prototype.hasOwnProperty() method. This vulnerability may allow a remote attacker execute arbitrary code.

Description

The ECMAScript for XML (E4X) Specification defines the XML.prototype.hasOwnProperty() as a JavaScript method used to determine if an object contains a specific property. Mozilla products fail to properly handle the XML.prototype.hasOwnProperty() method, which can lead to memory corruption.

For more information refer to Mozilla Foundation Security Advisory 2006-65.

Impact

A remote, unauthenticated attacker may be able to execute arbitrary code on a vulnerable system. The attacker could also cause the vulnerable application to crash.

Solution

Apply an update

According to the Mozilla Foundation Security Update 2006-65, this vulnerability is addressed in Firefox 1.5.0.8, Thunderbird 1.5.0.8, and SeaMonkey 1.0.6.

Note that according to Mozilla:

    Firefox 1.5.0.x will be maintained with security and stability updates until April 24, 2007. All users are strongly encouraged to upgrade to Firefox 2.

Disable JavaScript
This vulnerability can be mitigated by disabling JavaScript.

Systems Affected (Learn More)

VendorStatusDate NotifiedDate Updated
MozillaAffected-08 Nov 2006
If you are a vendor and your product is affected, let us know.

CVSS Metrics (Learn More)

Group Score Vector
Base N/A N/A
Temporal N/A N/A
Environmental N/A N/A

References

Credit

This vulnerability was reported in Mozilla Foundation Security Advisory 2006-65. Mozilla credits shutdown for providing information concerning this issue.

This document was written by Jeff Gennari.

Other Information

  • CVE IDs: CVE-2006-5747
  • Date Public: 08 Nov 2006
  • Date First Published: 08 Nov 2006
  • Date Last Updated: 21 Dec 2006
  • Severity Metric: 14.45
  • Document Revision: 36

Feedback

If you have feedback, comments, or additional information about this vulnerability, please send us email.