==================================================================== CERT-Renater Note d'Information No. 2020/VULN692 _____________________________________________________________________ DATE : 16/12/2020 HARDWARE PLATFORM(S): / OPERATING SYSTEM(S): Systems running Firefox versions prior to 78.6, 84. ===================================================================== https://www.mozilla.org/en-US/security/advisories/mfsa2020-55/ https://www.mozilla.org/en-US/security/advisories/mfsa2020-54/ _____________________________________________________________________ Mozilla Foundation Security Advisory 2020-55 Security Vulnerabilities fixed in Firefox ESR 78.6 Announced December 15, 2020 Impact critical Products Firefox ESR Fixed in Firefox ESR 78.6 #CVE-2020-16042: Operations on a BigInt could have caused uninitialized memory to be exposed Reporter André Bargull Impact critical Description When a BigInt was right-shifted the backing store was not properly cleared, allowing uninitialized memory to be read. References Bug 1679003 #CVE-2020-26971: Heap buffer overflow in WebGL Reporter Omair, Abraruddin Khan Impact high Description Certain blit values provided by the user were not properly constrained leading to a heap buffer overflow on some video drivers. References Bug 1663466 #CVE-2020-26973: CSS Sanitizer performed incorrect sanitization Reporter Kai Engert Impact high Description Certain input to the CSS Sanitizer confused it, resulting in incorrect components being removed. This could have been used as a sanitizer bypass. References Bug 1680084 #CVE-2020-26974: Incorrect cast of StyleGenericFlexBasis resulted in a heap use-after-free Reporter Pham Bao of VinCSS (Member of Vingroup) Impact high Description When flex-basis was used on a table wrapper, a StyleGenericFlexBasis object could have been incorrectly cast to the wrong type. This resulted in a heap user-after-free, memory corruption, and a potentially exploitable crash. References Bug 1681022 #CVE-2020-26978: Internal network hosts could have been probed by a malicious webpage Reporter Samy Kamkar, Ben Seri, and Gregory Vishnepolsky Impact moderate Description Using techniques that built on the slipstream research, a malicious webpage could have exposed both an internal network's hosts as well as services running on the user's local machine. References Bug 1677047 #CVE-2020-35111: The proxy.onRequest API did not catch view-source URLs Reporter Yassine Tioual Impact low Description When an extension with the proxy permission registered to receive , the proxy.onRequest callback was not triggered for view-source URLs. While web content cannot navigate to such URLs, a user opening View Source could have inadvertently leaked their IP address. References Bug 1657916 #CVE-2020-35112: Opening an extension-less download may have inadvertently launched an executable instead Reporter Samuel Attard via the Chrome Security Team Impact low Description If a user downloaded a file lacking an extension on Windows, and then "Open"-ed it from the downloads panel, if there was an executable file in the downloads directory with the same name but with an executable extension (such as .bat or .exe) that executable would have been launched instead. Note: This issue only affected Windows operating systems. Other operating systems are unaffected. References Bug 1661365 #CVE-2020-35113: Memory safety bugs fixed in Firefox 84 and Firefox ESR 78.6 Reporter Christian Holler Impact high Description Mozilla developer Christian Holler reported memory safety bugs present in Firefox 83 and Firefox ESR 78.5. Some of these bugs showed evidence of memory corruption and we presume that with enough effort some of these could have been exploited to run arbitrary code. References Memory safety bugs fixed in Firefox 84 and Firefox ESR 78.6 _____________________________________________________________________ Mozilla Foundation Security Advisory 2020-54 Security Vulnerabilities fixed in Firefox 84 Announced December 15, 2020 Impact critical Products Firefox Fixed in Firefox 84 #CVE-2020-16042: Operations on a BigInt could have caused uninitialized memory to be exposed Reporter André Bargull Impact critical Description When a BigInt was right-shifted the backing store was not properly cleared, allowing uninitialized memory to be read. References Bug 1679003 #CVE-2020-26971: Heap buffer overflow in WebGL Reporter Omair, Abraruddin Khan Impact high Description Certain blit values provided by the user were not properly constrained leading to a heap buffer overflow on some video drivers. References Bug 1663466 #CVE-2020-26972: Use-After-Free in WebGL Reporter Brian Carpenter via the ASAN Nightly project Impact high Description The lifecycle of IPC Actors allows managed actors to outlive their manager actors; and the former must ensure that they are not attempting to use a dead actor they have a reference to. Such a check was omitted in WebGL, resulting in a use-after-free and a potentially exploitable crash. References Bug 1671382 #CVE-2020-26973: CSS Sanitizer performed incorrect sanitization Reporter Kai Engert Impact high Description Certain input to the CSS Sanitizer confused it, resulting in incorrect components being removed. This could have been used as a sanitizer bypass. References Bug 1680084 #CVE-2020-26974: Incorrect cast of StyleGenericFlexBasis resulted in a heap use-after-free Reporter Pham Bao of VinCSS (Member of Vingroup) Impact high Description When flex-basis was used on a table wrapper, a StyleGenericFlexBasis object could have been incorrectly cast to the wrong type. This resulted in a heap user-after-free, memory corruption, and a potentially exploitable crash. References Bug 1681022 #CVE-2020-26975: Malicious applications on Android could have induced Firefox for Android into sending arbitrary attacker-specified headers Reporter Pedro Oliveira Impact moderate Description When a malicious application installed on the user's device broadcast an Intent to Firefox for Android, arbitrary headers could have been specified, leading to attacks such as abusing ambient authority or session fixation. This was resolved by only allowing certain safe-listed headers. Note: This issue only affected Firefox for Android. Other operating systems are unaffected. References Bug 1661071 #CVE-2020-26976: HTTPS pages could have been intercepted by a registered service worker when they should not have been Reporter Andrew Sutherland Impact moderate Description When a HTTPS pages was embedded in a HTTP page, and there was a service worker registered for the former, the service worker could have intercepted the request for the secure page despite the iframe not being a secure context due to the (insecure) framing. References Bug 1674343 #CVE-2020-26977: URL spoofing via unresponsive port in Firefox for Android Reporter andrew g Impact moderate Description By attempting to connect a website using an unresponsive port, an attacker could have controlled the content of a tab while the URL bar displayed the original domain. Note: This issue only affects Firefox for Android. Other operating systems are unaffected. References Bug 1676311 #CVE-2020-26978: Internal network hosts could have been probed by a malicious webpage Reporter Samy Kamkar, Ben Seri, and Gregory Vishnepolsky Impact moderate Description Using techniques that built on the slipstream research, a malicious webpage could have exposed both an internal network's hosts as well as services running on the user's local machine. References Bug 1677047 #CVE-2020-26979: When entering an address in the address or search bars, a website could have redirected the user before they were navigated to the intended url Reporter David Schütz Impact low Description When a user typed a URL in the address bar or the search bar and quickly hit the enter key, a website could sometimes capture that event and then redirect the user before navigation occurred to the desired, entered address. To construct a convincing spoof the attacker would have had to guess what the user was typing, perhaps by suggesting it. References Bug 1641287, 1673299 #CVE-2020-35111: The proxy.onRequest API did not catch view-source URLs Reporter Yassine Tioual Impact low Description When an extension with the proxy permission registered to receive , the proxy.onRequest callback was not triggered for view- source URLs. While web content cannot navigate to such URLs, a user opening View Source could have inadvertently leaked their IP address. References Bug 1657916 #CVE-2020-35112: Opening an extension-less download may have inadvertently launched an executable instead Reporter Samuel Attard via the Chrome Security Team Impact low Description If a user downloaded a file lacking an extension on Windows, and then "Open"-ed it from the downloads panel, if there was an executable file in the downloads directory with the same name but with an executable extension (such as .bat or .exe) that executable would have been launched instead. Note: This issue only affected Windows operating systems. Other operating systems are unaffected. References Bug 1661365 #CVE-2020-35113: Memory safety bugs fixed in Firefox 84 and Firefox ESR 78.6 Reporter Christian Holler Impact high Description Mozilla developer Christian Holler reported memory safety bugs present in Firefox 83 and Firefox ESR 78.5. Some of these bugs showed evidence of memory corruption and we presume that with enough effort some of these could have been exploited to run arbitrary code. References Memory safety bugs fixed in Firefox 84 and Firefox ESR 78.6 #CVE-2020-35114: Memory safety bugs fixed in Firefox 84 Reporter Mozilla developers Impact high Description Mozilla developers Christian Holler, Jan-Ivar Bruaroey, and Gabriele Svelto reported memory safety bugs present in Firefox 83. Some of these bugs showed evidence of memory corruption and we presume that with enough effort some of these could have been exploited to run arbitrary code. References Memory safety bugs fixed in Firefox 84 ========================================================= + CERT-RENATER       |    tel : 01-53-94-20-44          + + 23/25 Rue Daviel   |    fax : 01-53-94-20-41         + + 75013 Paris        |    email:cert@support.renater.fr + =========================================================