Bug 786258 (CVE-2011-3659) - CVE-2011-3659 Mozilla: child nodes from nsDOMAttribute still accessible after removal of nodes (MFSA 2012-04)
Summary: CVE-2011-3659 Mozilla: child nodes from nsDOMAttribute still accessible after...
Keywords:
Status: CLOSED ERRATA
Alias: CVE-2011-3659
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
urgent
urgent
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-01-31 20:46 UTC by Vincent Danen
Modified: 2021-02-24 13:16 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-02-01 09:04:40 UTC
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2012:0079 0 normal SHIPPED_LIVE Critical: firefox security update 2012-02-01 05:04:08 UTC
Red Hat Product Errata RHSA-2012:0080 0 normal SHIPPED_LIVE Critical: thunderbird security update 2012-02-01 04:43:33 UTC

Description Vincent Danen 2012-01-31 20:46:32 UTC 
It was found that removed child nodes of nsDOMAttribute could be accessed under certain circumstances, due to premature notification of AttributeChildRemoved.  This use-after-free of the child nodes could possibly allow for the the remote execution of arbitrary code.

Reference:
https://bugzilla.mozilla.org/show_bug.cgi?id=708198

External References:

http://www.mozilla.org/security/announce/2012/mfsa2012-04.html
Comment 1 errata-xmlrpc 2012-01-31 23:45:02 UTC 
This issue has been addressed in following products:

  Red Hat Enterprise Linux 6

Via RHSA-2012:0080 https://rhn.redhat.com/errata/RHSA-2012-0080.html
Comment 2 errata-xmlrpc 2012-02-01 00:07:28 UTC 
This issue has been addressed in following products:

  Red Hat Enterprise Linux 4
  Red Hat Enterprise Linux 5
  Red Hat Enterprise Linux 6

Via RHSA-2012:0079 https://rhn.redhat.com/errata/RHSA-2012-0079.html
Note You need to log in before you can comment on or make changes to this bug.