Mozilla Firefox before 18.0 on Android and SeaMonkey before 2.15 do not restrict a touch event to a single IFRAME element, which allows remote attackers to obtain sensitive information or possibly conduct cross-site scripting (XSS) attacks via a crafted HTML document.

Mozilla Firefox is updated to the 10.0.12ESR version.

This is a roll-up update for LTSS.

It fixes a lot of security issues and bugs. 10.0.12ESR fixes specifically :

MFSA 2013-01: Mozilla developers identified and fixed several memory safety bugs in the browser engine used in Firefox and other Mozilla-based products. Some of these bugs showed evidence of memory corruption under certain circumstances, and we presume that with enough effort at least some of these could be exploited to run arbitrary code.

Christoph Diehl, Christian Holler, Mats Palmgren, and Chiaki Ishikawa reported memory safety problems and crashes that affect Firefox ESR 10, Firefox ESR 17, and Firefox 17.
(CVE-2013-0769)

Bill Gianopoulos, Benoit Jacob, Christoph Diehl, Christian Holler, Gary Kwong, Robert O'Callahan, and Scoobidiver reported memory safety problems and crashes that affect Firefox ESR 17 and Firefox 17. (CVE-2013-0749)

Jesse Ruderman, Christian Holler, Julian Seward, and Scoobidiver reported memory safety problems and crashes that affect Firefox 17. (CVE-2013-0770)

MFSA 2013-02: Security researcher Abhishek Arya (Inferno) of the Google Chrome Security Team discovered a series critically rated of use-after-free, out of bounds read, and buffer overflow issues using the Address Sanitizer tool in shipped software. These issues are potentially exploitable, allowing for remote code execution. We would also like to thank Abhishek for reporting three additional user-after-free and out of bounds read flaws introduced during Firefox development that were fixed before general release.

The following issue has been fixed in Firefox 18 :

   - Global-buffer-overflow in     CharDistributionAnalysis::HandleOneChar (CVE-2013-0760)

    The following issues has been fixed in Firefox 18, ESR     17.0.1, and ESR 10.0.12 :

   - Heap-use-after-free in imgRequest::OnStopFrame     (CVE-2013-0762)
  - Heap-use-after-free in ~nsHTMLEditRules (CVE-2013-0766)
  - Out of bounds read in     nsSVGPathElement::GetPathLengthScale (CVE-2013-0763)
  - Heap-buffer-overflow in     gfxTextRun::ShrinkToLigatureBoundaries (CVE-2013-0771)

    The following issue has been fixed in Firefox 18 and in     the earlier ESR 10.0.11 release :

   - Heap-buffer-overflow in nsWindow::OnExposeEvent     (CVE-2012-5829) MFSA 2013-03: Security researcher     miaubiz used the Address Sanitizer tool to discover a     buffer overflow in Canvas when specific bad height and     width values were given through HTML. This could lead to     a potentially exploitable crash. (CVE-2013-0768)

    Miaubiz also found a potentially exploitable crash when     2D and 3D content was mixed which was introduced during     Firefox development and fixed before general release.

    MFSA 2013-04: Security researcher Masato Kinugawa found     a flaw in which the displayed URL values within the     addressbar can be spoofed by a page during loading. This     allows for phishing attacks where a malicious page can     spoof the identify of another site. (CVE-2013-0759)

    MFSA 2013-05: Using the Address Sanitizer tool, security     researcher Atte Kettunen from OUSPG discovered that the     combination of large numbers of columns and column     groups in a table could cause the array containing the     columns during rendering to overwrite itself. This can     lead to a user-after-free causing a potentially     exploitable crash. (CVE-2013-0744)

    MFSA 2013-06: Mozilla developer Wesley Johnston reported     that when there are two or more iframes on the same HTML     page, an iframe is able to see the touch events and     their targets that occur within the other iframes on the     page. If the iframes are from the same origin, they can     also access the properties and methods of the targets of     other iframes but same-origin policy (SOP) restricts     access across domains. This allows for information     leakage and possibilities for cross-site scripting (XSS)     if another vulnerability can be used to get around SOP     restrictions. (CVE-2013-0751)

    MFSA 2013-07: Mozilla community member Jerry Baker     reported a crashing issue found through Thunderbird when     downloading messages over a Secure Sockets Layer (SSL)     connection. This was caused by a bug in the networking     code assuming that secure connections were entirely     handled on the socket transport thread when they can     occur on a variety of threads. The resulting crash was     potentially exploitable. (CVE-2013-0764)

    MFSA 2013-08: Mozilla developer Olli Pettay discovered     that the AutoWrapperChanger class fails to keep some     JavaScript objects alive during garbage collection. This     can lead to an exploitable crash allowing for arbitrary     code execution. (CVE-2013-0745)

    MFSA 2013-09: Mozilla developer Boris Zbarsky reported     reported a problem where jsval-returning quickstubs fail     to wrap their return values, causing a compartment     mismatch. This mismatch can cause garbage collection to     occur incorrectly and lead to a potentially exploitable     crash. (CVE-2013-0746)

    MFSA 2013-10: Mozilla security researcher Jesse Ruderman     reported that events in the plugin handler can be     manipulated by web content to bypass same-origin policy     (SOP) restrictions. This can allow for clickjacking on     malicious web pages. (CVE-2013-0747)

    MFSA 2013-11: Mozilla security researcher Jesse Ruderman     discovered that using the toString function of XBL     objects can lead to inappropriate information leakage by     revealing the address space layout instead of just the     ID of the object. This layout information could     potentially be used to bypass ASLR and other security     protections. (CVE-2013-0748)

    MFSA 2013-12: Security researcher pa_kt reported a flaw     via TippingPoint's Zero Day Initiative that an integer     overflow is possible when calculating the length for a     JavaScript string concatenation, which is then used for     memory allocation. This results in a buffer overflow,     leading to a potentially exploitable memory corruption.
    (CVE-2013-0750)

    MFSA 2013-13: Security researcher Sviatoslav Chagaev     reported that when using an XBL file containing multiple     XML bindings with SVG content, a memory corruption can     occur. In concern with remote XUL, this can lead to an     exploitable crash. (CVE-2013-0752)

    MFSA 2013-14: Security researcher Mariusz Mlynski     reported that it is possible to change the prototype of     an object and bypass Chrome Object Wrappers (COW) to     gain access to chrome privileged functions. This could     allow for arbitrary code execution. (CVE-2013-0757)

    MFSA 2013-15: Security researcher Mariusz Mlynski     reported that it is possible to open a chrome privileged     web page through plugin objects through interaction with     SVG elements. This could allow for arbitrary code     execution. (CVE-2013-0758)

    MFSA 2013-16: Security researcher regenrecht reported,     via TippingPoint's Zero Day Initiative, a use-after-free     in XMLSerializer by the exposing of serializeToStream to     web content. This can lead to arbitrary code execution     when exploited. (CVE-2013-0753)

    MFSA 2013-17: Security researcher regenrecht reported,     via TippingPoint's Zero Day Initiative, a use-after-free     within the ListenerManager when garbage collection is     forced after data in listener objects have been     allocated in some circumstances. This results in a     use-after-free which can lead to arbitrary code     execution. (CVE-2013-0754)

    MFSA 2013-18: Security researcher regenrecht reported,     via TippingPoint's Zero Day Initiative, a use-after-free     using the domDoc pointer within Vibrate library. This     can lead to arbitrary code execution when exploited.
    (CVE-2013-0755)

    MFSA 2013-19: Security researcher regenrecht reported,     via TippingPoint's Zero Day Initiative, a garbage     collection flaw in JavaScript Proxy objects. This can     lead to a use-after-free leading to arbitrary code     execution. (CVE-2013-0756)

    MFSA 2013-20: Google reported to Mozilla that TURKTRUST,     a certificate authority in Mozilla's root program, had     mis-issued two intermediate certificates to customers.
    The issue was not specific to Firefox but there was     evidence that one of the certificates was used for     man-in-the-middle (MITM) traffic management of domain     names that the customer did not legitimately own or     control. This issue was resolved by revoking the trust     for these specific mis-issued certificates.
    (CVE-2013-0743)

Note that Tenable Network Security has extracted the preceding description block directly from the SUSE security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.

The Mozilla January 8th 2013 security release contains updates :

Mozilla Firefox was updated to version 18.0. Mozilla SeaMonkey was updated to version 2.15. Mozilla Thunderbird was updated to version 17.0.2. Mozilla XULRunner was updated to version 17.0.2.

  - MFSA 2013-01/CVE-2013-0749/CVE-2013-0769/CVE-2013-0770     Miscellaneous memory safety hazards

  - MFSA     2013-02/CVE-2013-0760/CVE-2013-0762/CVE-2013-0766/CVE-20     13-0767     CVE-2013-0761/CVE-2013-0763/CVE-2013-0771/CVE-2012-5829     Use-after-free and buffer overflow issues found using     Address Sanitizer

  - MFSA 2013-03/CVE-2013-0768 (bmo#815795) Buffer Overflow     in Canvas

  - MFSA 2013-04/CVE-2012-0759 (bmo#802026) URL spoofing in     addressbar during page loads

  - MFSA 2013-05/CVE-2013-0744 (bmo#814713) Use-after-free     when displaying table with many columns and column     groups

  - MFSA 2013-06/CVE-2013-0751 (bmo#790454) Touch events are     shared across iframes

  - MFSA 2013-07/CVE-2013-0764 (bmo#804237) Crash due to     handling of SSL on threads

  - MFSA 2013-08/CVE-2013-0745 (bmo#794158)     AutoWrapperChanger fails to keep objects alive during     garbage collection

  - MFSA 2013-09/CVE-2013-0746 (bmo#816842) Compartment     mismatch with quickstubs returned values

  - MFSA 2013-10/CVE-2013-0747 (bmo#733305) Event     manipulation in plugin handler to bypass same-origin     policy

  - MFSA 2013-11/CVE-2013-0748 (bmo#806031) Address space     layout leaked in XBL objects

  - MFSA 2013-12/CVE-2013-0750 (bmo#805121) Buffer overflow     in JavaScript string concatenation

  - MFSA 2013-13/CVE-2013-0752 (bmo#805024) Memory     corruption in XBL with XML bindings containing SVG

  - MFSA 2013-14/CVE-2013-0757 (bmo#813901) Chrome Object     Wrapper (COW) bypass through changing prototype

  - MFSA 2013-15/CVE-2013-0758 (bmo#813906) Privilege     escalation through plugin objects

  - MFSA 2013-16/CVE-2013-0753 (bmo#814001) Use-after-free     in serializeToStream

  - MFSA 2013-17/CVE-2013-0754 (bmo#814026) Use-after-free     in ListenerManager

  - MFSA 2013-18/CVE-2013-0755 (bmo#814027) Use-after-free     in Vibrate

  - MFSA 2013-19/CVE-2013-0756 (bmo#814029) Use-after-free     in JavaScript Proxy objects

Mozilla NSPR was updated to 4.9.4, containing some small bugfixes and new features.

Mozilla NSS was updated to 3.14.1 containing various new features, security fix and bugfixes :

  - MFSA 2013-20/CVE-2013-0743 (bmo#825022, bnc#796628)     revoke mis-issued intermediate certificates from     TURKTRUST

Cryptographic changes done :

  - Support for TLS 1.1 (RFC 4346)

  - Experimental support for DTLS 1.0 (RFC 4347) and     DTLS-SRTP (RFC 5764)

  - Support for AES-CTR, AES-CTS, and AES-GCM

  - Support for Keying Material Exporters for TLS (RFC 5705)

  - Support for certificate signatures using the MD5 hash     algorithm is now disabled by default

  - The NSS license has changed to MPL 2.0. Previous     releases were released under a MPL 1.1/GPL 2.0/LGPL 2.1     tri-license. For more information about MPL 2.0, please     see http://www.mozilla.org/MPL/2.0/FAQ.html. For an     additional explanation on GPL/LGPL compatibility, see     security/nss/COPYING in the source code.

  - Export and DES cipher suites are disabled by default.
    Non-ECC AES and Triple DES cipher suites are enabled by     default

Please see http://www.mozilla.org/security/announce/ for more information.

The remote host is affected by the vulnerability described in GLSA-201309-23 (Mozilla Products: Multiple vulnerabilities)

    Multiple vulnerabilities have been discovered in Mozilla Firefox,       Thunderbird, and SeaMonkey. Please review the CVE identifiers referenced       below for details.
  Impact :

    A remote attacker could entice a user to view a specially crafted web       page or email, possibly resulting in execution of arbitrary code or a       Denial of Service condition. Further, a remote attacker could conduct XSS       attacks, spoof URLs, bypass address space layout randomization, conduct       clickjacking attacks, obtain potentially sensitive information, bypass       access restrictions, modify the local filesystem, or conduct other       unspecified attacks.
  Workaround :

    There is no known workaround at this time.

Mozilla Firefox was updated to the 10.0.12ESR release.

  - Mozilla developers identified and fixed several memory     safety bugs in the browser engine used in Firefox and     other Mozilla-based products. Some of these bugs showed     evidence of memory corruption under certain     circumstances, and we presume that with enough effort at     least some of these could be exploited to run arbitrary     code. (MFSA 2013-01)

  - Christoph Diehl, Christian Holler, Mats Palmgren, and     Chiaki Ishikawa reported memory safety problems and     crashes that affect Firefox ESR 10, Firefox ESR 17, and     Firefox 17. (CVE-2013-0769)

  - Bill Gianopoulos, Benoit Jacob, Christoph Diehl,     Christian Holler, Gary Kwong, Robert O'Callahan, and     Scoobidiver reported memory safety problems and crashes     that affect Firefox ESR 17 and Firefox 17.
    (CVE-2013-0749)

  - Jesse Ruderman, Christian Holler, Julian Seward, and     Scoobidiver reported memory safety problems and crashes     that affect Firefox 17. (CVE-2013-0770)

  - Security researcher Abhishek Arya (Inferno) of the     Google Chrome Security Team discovered a series     critically rated of use-after-free, out of bounds read,     and buffer overflow issues using the Address Sanitizer     tool in shipped software. These issues are potentially     exploitable, allowing for remote code execution. We     would also like to thank Abhishek for reporting three     additional user-after-free and out of bounds read flaws     introduced during Firefox development that were fixed     before general release. (MFSA 2013-02)

The following issue was fixed in Firefox 18 :

  - Global-buffer-overflow in     CharDistributionAnalysis::HandleOneChar. (CVE-2013-0760)

The following issues were fixed in Firefox 18, ESR 17.0.1, and ESR 10.0.12 :

  - Heap-use-after-free in imgRequest::OnStopFrame.
    (CVE-2013-0762)

  - Heap-use-after-free in ~nsHTMLEditRules. (CVE-2013-0766)

  - Out of bounds read in     nsSVGPathElement::GetPathLengthScale. (CVE-2013-0767)

The following issues were fixed in Firefox 18 and ESR 17.0.1 :

  - Heap-use-after-free in     mozilla::TrackUnionStream::EndTrack. (CVE-2013-0761)

  - Heap-use-after-free in Mesa, triggerable by resizing a     WebGL canvas. (CVE-2013-0763)

  - Heap-buffer-overflow in     gfxTextRun::ShrinkToLigatureBoundaries. (CVE-2013-0771)

The following issue was fixed in Firefox 18 and in the earlier ESR 10.0.11 release :

  - Heap-buffer-overflow in nsWindow::OnExposeEvent.
    (CVE-2012-5829)

  - Security researcher miaubiz used the Address Sanitizer     tool to discover a buffer overflow in Canvas when     specific bad height and width values were given through     HTML. This could lead to a potentially exploitable     crash. (CVE-2013-0768). (MFSA 2013-03)

    Miaubiz also found a potentially exploitable crash when     2D and 3D content was mixed which was introduced during     Firefox development and fixed before general release.

  - Security researcher Masato Kinugawa found a flaw in     which the displayed URL values within the addressbar can     be spoofed by a page during loading. This allows for     phishing attacks where a malicious page can spoof the     identify of another site. (CVE-2013-0759). (MFSA     2013-04)

  - Using the Address Sanitizer tool, security researcher     Atte Kettunen from OUSPG discovered that the combination     of large numbers of columns and column groups in a table     could cause the array containing the columns during     rendering to overwrite itself. This can lead to a     user-after-free causing a potentially exploitable crash.
    (CVE-2013-0744). (MFSA 2013-05)

  - Mozilla developer Wesley Johnston reported that when     there are two or more iframes on the same HTML page, an     iframe is able to see the touch events and their targets     that occur within the other iframes on the page. If the     iframes are from the same origin, they can also access     the properties and methods of the targets of other     iframes but same-origin policy (SOP) restricts access     across domains. This allows for information leakage and     possibilities for cross-site scripting (XSS) if another     vulnerability can be used to get around SOP     restrictions. (CVE-2013-0751). (MFSA 2013-06)

  - Mozilla community member Jerry Baker reported a crashing     issue found through Thunderbird when downloading     messages over a Secure Sockets Layer (SSL) connection.
    This was caused by a bug in the networking code assuming     that secure connections were entirely handled on the     socket transport thread when they can occur on a variety     of threads. The resulting crash was potentially     exploitable. (CVE-2013-0764). (MFSA 2013-07)

  - Mozilla developer Olli Pettay discovered that the     AutoWrapperChanger class fails to keep some JavaScript     objects alive during garbage collection. This can lead     to an exploitable crash allowing for arbitrary code     execution. (CVE-2013-0745). (MFSA 2013-08)

  - Mozilla developer Boris Zbarsky reported reported a     problem where jsval-returning quickstubs fail to wrap     their return values, causing a compartment mismatch.
    This mismatch can cause garbage collection to occur     incorrectly and lead to a potentially exploitable crash.
    (CVE-2013-0746). (MFSA 2013-09)

  - Mozilla security researcher Jesse Ruderman reported that     events in the plugin handler can be manipulated by web     content to bypass same-origin policy (SOP) restrictions.
    This can allow for clickjacking on malicious web pages.
    (CVE-2013-0747). (MFSA 2013-10)

  - Mozilla security researcher Jesse Ruderman discovered     that using the toString function of XBL objects can lead     to inappropriate information leakage by revealing the     address space layout instead of just the ID of the     object. This layout information could potentially be     used to bypass ASLR and other security protections.
    (CVE-2013-0748). (MFSA 2013-11)

  - Security researcher pa_kt reported a flaw via     TippingPoint's Zero Day Initiative that an integer     overflow is possible when calculating the length for a     JavaScript string concatenation, which is then used for     memory allocation. This results in a buffer overflow,     leading to a potentially exploitable memory corruption.
    (CVE-2013-0750). (MFSA 2013-12)

  - Security researcher Sviatoslav Chagaev reported that     when using an XBL file containing multiple XML bindings     with SVG content, a memory corruption can occur. In     concern with remote XUL, this can lead to an exploitable     crash. (CVE-2013-0752). (MFSA 2013-13)

  - Security researcher Mariusz Mlynski reported that it is     possible to change the prototype of an object and bypass     Chrome Object Wrappers (COW) to gain access to chrome     privileged functions. This could allow for arbitrary     code execution. (CVE-2013-0757). (MFSA 2013-14)

  - Security researcher Mariusz Mlynski reported that it is     possible to open a chrome privileged web page through     plugin objects through interaction with SVG elements.
    This could allow for arbitrary code execution.
    (CVE-2013-0758). (MFSA 2013-15)

  - Security researcher regenrecht reported, via     TippingPoint's Zero Day Initiative, a use-after-free in     XMLSerializer by the exposing of serializeToStream to     web content. This can lead to arbitrary code execution     when exploited. (CVE-2013-0753). (MFSA 2013-16)

  - Security researcher regenrecht reported, via     TippingPoint's Zero Day Initiative, a use-after-free     within the ListenerManager when garbage collection is     forced after data in listener objects have been     allocated in some circumstances. This results in a     use-after-free which can lead to arbitrary code     execution. (CVE-2013-0754). (MFSA 2013-17)

  - Security researcher regenrecht reported, via     TippingPoint's Zero Day Initiative, a use-after-free     using the domDoc pointer within Vibrate library. This     can lead to arbitrary code execution when exploited.
    (CVE-2013-0755). (MFSA 2013-18)

  - Security researcher regenrecht reported, via     TippingPoint's Zero Day Initiative, a garbage collection     flaw in JavaScript Proxy objects. This can lead to a     use-after-free leading to arbitrary code execution.
    (CVE-2013-0756). (MFSA 2013-19)

  - Google reported to Mozilla that TURKTRUST, a certificate     authority in Mozilla's root program, had mis-issued two     intermediate certificates to customers. The issue was     not specific to Firefox but there was evidence that one     of the certificates was used for man-in-the-middle     (MITM) traffic management of domain names that the     customer did not legitimately own or control. This issue     was resolved by revoking the trust for these specific     mis-issued certificates. (CVE-2013-0743). (MFSA 2013-20)

Mozilla Firefox was updated to the 10.0.12ESR release.

  - Mozilla developers identified and fixed several memory     safety bugs in the browser engine used in Firefox and     other Mozilla-based products. Some of these bugs showed     evidence of memory corruption under certain     circumstances, and we presume that with enough effort at     least some of these could be exploited to run arbitrary     code. (MFSA 2013-01)

    o Christoph Diehl, Christian Holler, Mats Palmgren, and     Chiaki Ishikawa reported memory safety problems and     crashes that affect Firefox ESR 10, Firefox ESR 17, and     Firefox 17. (CVE-2013-0769) o Bill Gianopoulos, Benoit     Jacob, Christoph Diehl, Christian Holler, Gary Kwong,     Robert O'Callahan, and Scoobidiver reported memory     safety problems and crashes that affect Firefox ESR 17     and Firefox 17. (CVE-2013-0749) o Jesse Ruderman,     Christian Holler, Julian Seward, and Scoobidiver     reported memory safety problems and crashes that affect     Firefox 17. (CVE-2013-0770)

  - Security researcher Abhishek Arya (Inferno) of the     Google Chrome Security Team discovered a series     critically rated of use-after-free, out of bounds read,     and buffer overflow issues using the Address Sanitizer     tool in shipped software. These issues are potentially     exploitable, allowing for remote code execution. We     would also like to thank Abhishek for reporting three     additional user-after-free and out of bounds read flaws     introduced during Firefox development that were fixed     before general release. (MFSA 2013-02)

    The following issue was fixed in Firefox 18 :

o Global-buffer-overflow in CharDistributionAnalysis::HandleOneChar.
(CVE-2013-0760)

The following issues were fixed in Firefox 18, ESR 17.0.1, and ESR 10.0.12 :

o Heap-use-after-free in imgRequest::OnStopFrame (CVE-2013-0762) o Heap-use-after-free in ~nsHTMLEditRules (CVE-2013-0766) o Out of bounds read in nsSVGPathElement::GetPathLengthScale. (CVE-2013-0767)

The following issues were fixed in Firefox 18 and ESR 17.0.1 :

o Heap-use-after-free in mozilla::TrackUnionStream::EndTrack (CVE-2013-0761) o Heap-use-after-free in Mesa, triggerable by resizing a WebGL canvas (CVE-2013-0763) o Heap-buffer-overflow in gfxTextRun::ShrinkToLigatureBoundaries. (CVE-2013-0771)

The following issue was fixed in Firefox 18 and in the earlier ESR 10.0.11 release :

o Heap-buffer-overflow in nsWindow::OnExposeEvent. (CVE-2012-5829)

  - Security researcher miaubiz used the Address Sanitizer     tool to discover a buffer overflow in Canvas when     specific bad height and width values were given through     HTML. This could lead to a potentially exploitable     crash. (CVE-2013-0768). (MFSA 2013-03)

    Miaubiz also found a potentially exploitable crash when     2D and 3D content was mixed which was introduced during     Firefox development and fixed before general release.

  - Security researcher Masato Kinugawa found a flaw in     which the displayed URL values within the addressbar can     be spoofed by a page during loading. This allows for     phishing attacks where a malicious page can spoof the     identify of another site. (CVE-2013-0759). (MFSA     2013-04)

  - Using the Address Sanitizer tool, security researcher     Atte Kettunen from OUSPG discovered that the combination     of large numbers of columns and column groups in a table     could cause the array containing the columns during     rendering to overwrite itself. This can lead to a     user-after-free causing a potentially exploitable crash.
    (CVE-2013-0744). (MFSA 2013-05)

  - Mozilla developer Wesley Johnston reported that when     there are two or more iframes on the same HTML page, an     iframe is able to see the touch events and their targets     that occur within the other iframes on the page. If the     iframes are from the same origin, they can also access     the properties and methods of the targets of other     iframes but same-origin policy (SOP) restricts access     across domains. This allows for information leakage and     possibilities for cross-site scripting (XSS) if another     vulnerability can be used to get around SOP     restrictions. (CVE-2013-0751). (MFSA 2013-06)

  - Mozilla community member Jerry Baker reported a crashing     issue found through Thunderbird when downloading     messages over a Secure Sockets Layer (SSL) connection.
    This was caused by a bug in the networking code assuming     that secure connections were entirely handled on the     socket transport thread when they can occur on a variety     of threads. The resulting crash was potentially     exploitable. (CVE-2013-0764). (MFSA 2013-07)

  - Mozilla developer Olli Pettay discovered that the     AutoWrapperChanger class fails to keep some JavaScript     objects alive during garbage collection. This can lead     to an exploitable crash allowing for arbitrary code     execution. (CVE-2013-0745). (MFSA 2013-08)

  - Mozilla developer Boris Zbarsky reported reported a     problem where jsval-returning quickstubs fail to wrap     their return values, causing a compartment mismatch.
    This mismatch can cause garbage collection to occur     incorrectly and lead to a potentially exploitable crash.
    (CVE-2013-0746). (MFSA 2013-09)

  - Mozilla security researcher Jesse Ruderman reported that     events in the plugin handler can be manipulated by web     content to bypass same-origin policy (SOP) restrictions.
    This can allow for clickjacking on malicious web pages.
    (CVE-2013-0747). (MFSA 2013-10)

  - Mozilla security researcher Jesse Ruderman discovered     that using the toString function of XBL objects can lead     to inappropriate information leakage by revealing the     address space layout instead of just the ID of the     object. This layout information could potentially be     used to bypass ASLR and other security protections.
    (CVE-2013-0748). (MFSA 2013-11)

  - Security researcher pa_kt reported a flaw via     TippingPoint's Zero Day Initiative that an integer     overflow is possible when calculating the length for a     JavaScript string concatenation, which is then used for     memory allocation. This results in a buffer overflow,     leading to a potentially exploitable memory corruption.
    (CVE-2013-0750). (MFSA 2013-12)

  - Security researcher Sviatoslav Chagaev reported that     when using an XBL file containing multiple XML bindings     with SVG content, a memory corruption can occur. In     concern with remote XUL, this can lead to an exploitable     crash. (CVE-2013-0752). (MFSA 2013-13)

  - Security researcher Mariusz Mlynski reported that it is     possible to change the prototype of an object and bypass     Chrome Object Wrappers (COW) to gain access to chrome     privileged functions. This could allow for arbitrary     code execution. (CVE-2013-0757). (MFSA 2013-14)

  - Security researcher Mariusz Mlynski reported that it is     possible to open a chrome privileged web page through     plugin objects through interaction with SVG elements.
    This could allow for arbitrary code execution.
    (CVE-2013-0758). (MFSA 2013-15)

  - Security researcher regenrecht reported, via     TippingPoint's Zero Day Initiative, a use-after-free in     XMLSerializer by the exposing of serializeToStream to     web content. This can lead to arbitrary code execution     when exploited. (CVE-2013-0753). (MFSA 2013-16)

  - Security researcher regenrecht reported, via     TippingPoint's Zero Day Initiative, a use-after-free     within the ListenerManager when garbage collection is     forced after data in listener objects have been     allocated in some circumstances. This results in a     use-after-free which can lead to arbitrary code     execution. (CVE-2013-0754). (MFSA 2013-17)

  - Security researcher regenrecht reported, via     TippingPoint's Zero Day Initiative, a use-after-free     using the domDoc pointer within Vibrate library. This     can lead to arbitrary code execution when exploited.
    (CVE-2013-0755). (MFSA 2013-18)

  - Security researcher regenrecht reported, via     TippingPoint's Zero Day Initiative, a garbage collection     flaw in JavaScript Proxy objects. This can lead to a     use-after-free leading to arbitrary code execution.
    (CVE-2013-0756). (MFSA 2013-19)

  - Google reported to Mozilla that TURKTRUST, a certificate     authority in Mozilla's root program, had mis-issued two     intermediate certificates to customers. The issue was     not specific to Firefox but there was evidence that one     of the certificates was used for man-in-the-middle     (MITM) traffic management of domain names that the     customer did not legitimately own or control. This issue     was resolved by revoking the trust for these specific     mis-issued certificates. (CVE-2013-0743). (MFSA 2013-20)

Versions of Firefox 17.x are potentially affected by the following security issues :

  - Multiple, unspecified use-after-free, out-of-bounds read and buffer overflow errors exist. (CVE-2012-5829, CVE-2013-0760, CVE-2013-0761, CVE-2013-0762, CVE-2013-0763, CVE-2013-0766, CVE-2013-0767, CVE-2013-0771)

  - Two intermediate certificates were improperly issued by TURKTRUST certificate authority. (CVE-2013-0743)

  - A use-after-free error exists related to displaying HTML tables with many columns and column groups. (CVE-2013-0744)

  - An error exists related to the 'AutoWrapperChanger' class that does not properly manage objects during garbage collection. (CVE-2012-0745)

  - An error exists related to 'jsval', 'quickstubs', and compartmental mismatches that can lead potentially exploitable crashes. (CVE-2013-0746)

  - Errors exist related to events in the plugin handler that can allow same-origin policy bypass. (CVE-2013-0747)

  - An error related to the 'toString' method of XBL objects can lead to address information leakage. (CVE-2013-0748)

  - An unspecified memory corruption issue exists. (CVE-2013-0749, CVE-2013-0769, CVE-2013-0770)

  - A buffer overflow exists related to JavaScript string concatenation. (CVE-2013-0750)

  - An error exists related to multiple XML bindings with SVG content, contained in XBL files. (CVE-2013-0752)

  - A use-after-free error exists related to 'XMLSerializer' and 'serializeToStream'. (CVE-2013-0753)

  - A use-after-free error exists related to garbage collection and 'ListenManager'. (CVE-2013-0754)

  - A use-after-free error exists related to the 'Vibrate' library and 'domDoc'. (CVE-2013-0755)

  - A use-after-free error exists related to JavaScript 'Proxy' objects. (CVE-2013-0756)

  - 'Chrome Object Wrappers' (COW) can be bypassed by changing object prototypes and can allow arbitrary code execution. (CVE-2013-0757)

  - An error related to SVG elements and plugins can allow privilege escalation. (CVE-2013-0758)

  - An error exists related to the address bar that can allow URL spoofing attacks. (CVE-2013-0759)

  - An error exists related to SSL and threading that can result in potentially exploitable crashes. (CVE-2013-0764)

  - An error exists related to 'Canvas' and bad height or width values passed to it from HTML. (CVE-2013-0768)

Versions of Firefox prior to 18.0 are potentially affected by the following security issues :

 - Multiple, unspecified use-after-free, out-of-bounds read and buffer overflow errors exist. (CVE-2012-5829, CVE-2013-0760, CVE-2013-0761, CVE-2013-0762, CVE-2013-0763, CVE-2013-0766, CVE-2013-0767, CVE-2013-0771)
 - Two intermediate certificates were improperly issued by TURKTRUST certificate authority. (CVE-2013-0743)
 - A use-after-free error exists related to displaying HTML tables with many columns and column groups. (CVE-2013-0744)
 - An error exists related to the 'AutoWrapperChanger' class that does not properly manage objects during garbage collection. (CVE-2012-0745)
 - An error exists related to 'jsval', 'quickstubs', and compartmental mismatches that can lead potentially exploitable crashes. (CVE-2013-0746)
 - Errors exist related to events in the plugin handler that can allow same-origin policy bypass. (CVE-2013-0747)
 - An error related to the 'toString' method of XBL objects can lead to address information leakage. (CVE-2013-0748)
 - An unspecified memory corruption issue exists. (CVE-2013-0749, CVE-2013-0769, CVE-2013-0770)
 - A buffer overflow exists related to JavaScript string concatenation. (CVE-2013-0750)
 - An error exists related to multiple XML bindings with SVG content, contained in XBL files. (CVE-2013-0752)
 - A use-after-free error exists related to 'XMLSerializer' and 'serializeToStream'. (CVE-2013-0753)
 - A use-after-free error exists related to garbage collection and 'ListenManager'. (CVE-2013-0754)
 - A use-after-free error exists related to the 'Vibrate' library and 'domDoc'. (CVE-2013-0755)
 - A use-after-free error exists related to JavaScript 'Proxy' objects. (CVE-2013-0756)
 - 'Chrome Object Wrappers' (COW) can be bypassed by changing object prototypes and can allow arbitrary code execution. (CVE-2013-0757)
 - An error related to SVG elements and plugins can allow privilege escalation. (CVE-2013-0758)
 - An error exists related to the address bar that can allow URL spoofing attacks. (CVE-2013-0759)
 - An error exists related to SSL and threading that can result in potentially exploitable crashes. (CVE-2013-0764)
 - An error exists related to 'Canvas' and bad height or width values passed to it from HTML. (CVE-2013-0768)

The Mozilla Project reports :

MFSA 2013-01 Miscellaneous memory safety hazards (rv:18.0/ rv:10.0.12 / rv:17.0.2)

MFSA 2013-02 Use-after-free and buffer overflow issues found using Address Sanitizer

MFSA 2013-03 Buffer Overflow in Canvas

MFSA 2013-04 URL spoofing in addressbar during page loads

MFSA 2013-05 Use-after-free when displaying table with many columns and column groups

MFSA 2013-06 Touch events are shared across iframes

MFSA 2013-07 Crash due to handling of SSL on threads

MFSA 2013-08 AutoWrapperChanger fails to keep objects alive during garbage collection

MFSA 2013-09 Compartment mismatch with quickstubs returned values

MFSA 2013-10 Event manipulation in plugin handler to bypass same-origin policy

MFSA 2013-11 Address space layout leaked in XBL objects

MFSA 2013-12 Buffer overflow in JavaScript string concatenation

MFSA 2013-13 Memory corruption in XBL with XML bindings containing SVG

MFSA 2013-14 Chrome Object Wrapper (COW) bypass through changing prototype

MFSA 2013-15 Privilege escalation through plugin objects

MFSA 2013-16 Use-after-free in serializeToStream

MFSA 2013-17 Use-after-free in ListenerManager

MFSA 2013-18 Use-after-free in Vibrate

MFSA 2013-19 Use-after-free in JavaScript Proxy objects

MFSA 2013-20 Mis-issued TURKTRUST certificates

ID	Name	Product	Family	Severity
83574	SUSE SLES10 Security Update : Mozilla Firefox (SUSE-SU-2013:0306-1)	Nessus	SuSE Local Security Checks	critical
74918	openSUSE Security Update : firefox / seamonkey / thunderbird (openSUSE-SU-2013:0149-1)	Nessus	SuSE Local Security Checks	critical
70183	GLSA-201309-23 : Mozilla Products: Multiple vulnerabilities	Nessus	Gentoo Local Security Checks	critical
64136	SuSE 11.2 Security Update : MozillaFirefox (SAT Patch Number 7224)	Nessus	SuSE Local Security Checks	critical
63626	SuSE 10 Security Update : MozillaFirefox (ZYPP Patch Number 8426)	Nessus	SuSE Local Security Checks	critical
801345	Mozilla Firefox 17.x <= 17 Multiple Vulnerabilities	Log Correlation Engine	Web Clients	high
6668	Mozilla Firefox < 18.0 Multiple Vulnerabilities	Nessus Network Monitor	Web Clients	high
63463	FreeBSD : mozilla -- multiple vulnerabilities (a4ed6632-5aa9-11e2-8fcb-c8600054b392)	Nessus	FreeBSD Local Security Checks	critical

Detections

Analytics

CVE-2013-0751

medium

Tenable Plugins

critical

critical

critical

critical

critical

high

high

critical