Mozilla Products Multiple Vulnerabilities

Multiple vulnerabilitieshave been identified in Mozilla Firefox, Thunderbird and SeaMonkey, which could be exploited by attackers to manipulate or disclose certain data, bypass security restrictions or compromise a vulnerable system.

1. Due to memory corruption errors in the browser engine when parsing malformed data, which could be exploited by attackers to crash a vulnerable browser or execute arbitrary code.

2. Due to an integer overflow error in the implementation of the HTML frameset, which could be exploited to execute arbitrary code.

3. Due to a dangling pointer in the implementation of "navigator.plugins", which could be exploited to execute arbitrary code.

4. Due to an error when loading librairies.

5. Due to a heap overflow error when transforming text runs, which could be exploited to execute arbitrary code.

6. Due to a dangling pointer error in "nsTreeSelection", which could be exploited to execute arbitrary code.

7. Due to a use-after-free error related to XUL "tree" objects, which could be exploited to execute arbitrary code.

8. Due to a dandling pointer related to the implementation of XUL tree's content view (nsTreeContentView), which could be exploited to execute arbitrary code.

9. Due to a use-after-free error when normalizing documents, which could be exploited to execute arbitrary code.

10. Due to a memory corruption when processing a specially crafted font in "data:" URL, which could be exploited to execute arbitrary code.

11. Due to an error in the wrapper class XPCSafeJSObjectWrapper (SJOW), which could be exploited to execute arbitrary code.

12. Due to a same-origin policy violation related to the wrapper class XPCSafeJSObjectWrapper (SJOW), which could allow cross-domain scripting attacks.

13. Due to an error related to the "type" attribute of an "object" tag, which could allow cross site scripting attacks.

14. Due to an error related to copy-and-paste and drag-and-drop into "designMode" documents, which could allow cross site scripting attacks.

15. Due to the "statusText" property of an "XMLHttpRequest" object being readable by the requestor even when the request is made across origins, which could be exploited to gain knowledge of certain information.