Mozilla developers 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. This vulnerability affects Firefox < 72.

The remote Ubuntu 16.04 LTS / 18.04 LTS host has packages installed that are affected by multiple vulnerabilities as referenced in the USN-4234-1 advisory.

    Multiple security issues were discovered in Firefox. If a user were tricked in to opening a specially     crafted website, an attacker could potentially exploit these to cause a denial of service, obtain     sensitive information, bypass Content Security Policy (CSP) restrictions, conduct cross-site scripting     (XSS) attacks, or execute arbitrary code.

Tenable has extracted the preceding description block directly from the Ubuntu security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The version of Firefox installed on the remote Windows host is prior to 72.0. It is, therefore, affected by multiple vulnerabilities as referenced in the mfsa2020-01 advisory, including the following:

  - 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. (CVE-2019-17015)

  - 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. (CVE-2019-17016)

  - 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.
    (CVE-2019-17017)

  - When in Private Browsing Mode on Windows 10, the Windows keyboard may retain word suggestions to improve     the accuracy of the keyboard. (CVE-2019-17018)

  - 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. (CVE-2019-17019)

  - 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. (CVE-2019-17020)

  - 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. (CVE-2019-17021)

  - 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. (CVE-2019-17022)     
  - 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. (CVE-2019-17023)

  - 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. (CVE-2019-17024)

  - 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. (CVE-2019-17025)

Note that Nessus has not tested for this issue but has instead relied only on the application's self-reported version number.

The version of Firefox installed on the remote macOS or Mac OS X host is prior to 72.0. It is, therefore, affected by multiple vulnerabilities as referenced in the mfsa2020-01 advisory, including the following:

- 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. (CVE-2019-17016)

- 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.
  (CVE-2019-17017)

- 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. (CVE-2019-17020)

- 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. (CVE-2019-17022)   
- 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. (CVE-2019-17023)

- 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. (CVE-2019-17024)

- 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. (CVE-2019-17025)

Note that Nessus has not tested for this issue but has instead relied only on the application's self-reported version number.

ID	Name	Product	Family	Severity
132854	Ubuntu 16.04 LTS / 18.04 LTS : Firefox vulnerabilities (USN-4234-1)	Nessus	Ubuntu Local Security Checks	high
132709	Mozilla Firefox < 72.0 Multiple Vulnerabilities	Nessus	Windows	high
132708	Mozilla Firefox < 72.0 Multiple Vulnerabilities	Nessus	MacOS X Local Security Checks	high

Detections

Analytics

CVE-2019-17025

high

Tenable Plugins

high

high

high