Mozilla Foundation Security Advisory 2020-01
Security Vulnerabilities fixed in Firefox 72
- Announced
- January 7, 2020
- Impact
- high
- Products
- Firefox
- Fixed in
-
- Firefox 72
#CVE-2019-17015: Memory corruption in parent process during new content process initialization on Windows
- Reporter
- Thomas Imbert
- Impact
- high
Description
During the initialization of a new content process, a pointer offset can be manipulated leading to memory corruption and a potentially exploitable crash in the parent process.
Note: this issue only occurs on Windows. Other operating systems are unaffected.
References
#CVE-2019-17016: Bypass of @namespace CSS sanitization during pasting
- Reporter
- Michał Bentkowski
- Impact
- high
Description
When pasting a <style> tag from the clipboard into a rich text editor, the CSS sanitizer incorrectly rewrites a @namespace rule. This could allow for injection into certain types of websites resulting in data exfiltration.
References
#CVE-2019-17017: Type Confusion in XPCVariant.cpp
- Reporter
- bo13oy
- Impact
- high
Description
Due to a missing case handling object types, a type confusion vulnerability could occur, resulting in a crash. We presume that with enough effort that it could be exploited to run arbitrary code.
References
#CVE-2019-17018: Windows Keyboard in Private Browsing Mode may retain word suggestions
- Reporter
- Siye Lui
- Impact
- moderate
Description
When in Private Browsing Mode on Windows 10, the Windows keyboard may retain word suggestions to improve the accuracy of the keyboard.
References
#CVE-2019-17019: Python files could be inadvertently executed upon opening a download
- Reporter
- Prithwish Kumar Pal
- Impact
- moderate
Description
When Python was installed on Windows, a python file being served with the MIME type of text/plain could be executed by Python instead of being opened as a text file when the Open option was selected upon download.
Note: this issue only occurs on Windows. Other operating systems are unaffected.
References
#CVE-2019-17020: Content Security Policy not applied to XSL stylesheets applied to XML documents
- Reporter
- Matthew Somerville
- Impact
- moderate
Description
If an XML file is served with a Content Security Policy and the XML file includes an XSL stylesheet, the Content Security Policy will not be applied to the contents of the XSL stylesheet. If the XSL sheet e.g. includes JavaScript, it would bypass any of the restrictions of the Content Security Policy applied to the XML document.
References
#CVE-2019-17021: Heap address disclosure in parent process during content process initialization on Windows
- Reporter
- Thomas Imbert
- Impact
- moderate
Description
During the initialization of a new content process, a race condition occurs that can allow a content process to disclose heap addresses from the parent process.
Note: this issue only occurs on Windows. Other operating systems are unaffected.
References
#CVE-2019-17022: CSS sanitization does not escape HTML tags
- Reporter
- Michał Bentkowski
- Impact
- moderate
Description
When pasting a <style> tag from the clipboard into a rich text editor, the CSS sanitizer does not escape < and > characters. Because the resulting string is pasted directly into the text node of the element this does not result in a direct injection into the webpage; however, if a webpage subsequently copies the node's innerHTML, assigning it to another innerHTML, this would result in an XSS vulnerability. Two WYSIWYG editors were identified with this behavior, more may exist.
References
#CVE-2019-17023: NSS may negotiate TLS 1.2 or below after a TLS 1.3 HelloRetryRequest had been sent
- Reporter
- Google oss-fuzz
- Impact
- low
Description
After a HelloRetryRequest has been sent, the client may negotiate a lower protocol that TLS 1.3, resulting in an invalid state transition in the TLS State Machine. If the client gets into this state, incoming Application Data records will be ignored.
References
#CVE-2019-17024: Memory safety bugs fixed in Firefox 72 and Firefox ESR 68.4
- Reporter
- Mozilla developers
- Impact
- high
Description
Mozilla developers Jason Kratzer, Christian Holler, and Bob Clary reported memory safety bugs present in Firefox 71 and Firefox ESR 68.3. 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
#CVE-2019-17025: Memory safety bugs fixed in Firefox 72
- Reporter
- Mozilla developers
- Impact
- high
Description
Mozilla developers Karl Tomlinson, Jason Kratzer, Tyson Smith, Jon Coppeard, and Christian Holler reported memory safety bugs present in Firefox 71. 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.