Using the <code>S.browser_fallback_url parameter</code> parameter, an attacker could redirect a user to a URL and cause SameSite=Strict cookies to be sent.<br>*This issue only affects Firefox for Android. Other operating systems are not affected.*. This vulnerability affects Firefox < 107.

An update of the mozjs package has been released.

The remote host is affected by the vulnerability described in GLSA-202211-06 (Mozilla Firefox: Multiple Vulnerabilities)

  - libexpat before 2.4.9 has a use-after-free in the doContent function in xmlparse.c. (CVE-2022-40674)

  - Service Workers should not be able to infer information about opaque cross-origin responses; but timing     information for cross-origin media combined with Range requests might have allowed them to determine the     presence or length of a media file.  (CVE-2022-45403)

  - Through a series of popup and <code>window.print()</code> calls, an attacker can cause a window to go     fullscreen without the user seeing the notification prompt, resulting in potential user confusion or     spoofing attacks.  (CVE-2022-45404)

  - Freeing arbitrary <code>nsIInputStream</code>'s on a different thread than creation could have led to a     use-after-free and potentially exploitable crash.  (CVE-2022-45405)

  - If an out-of-memory condition occurred when creating a JavaScript global, a JavaScript realm may be     deleted while references to it lived on in a BaseShape. This could lead to a use-after-free causing a     potentially exploitable crash.  (CVE-2022-45406)

  - If an attacker loaded a font using <code>FontFace()</code> on a background worker, a use-after-free could     have occurred, leading to a potentially exploitable crash.  (CVE-2022-45407)

  - Through a series of popups that reuse windowName, an attacker can cause a window to go fullscreen without     the user seeing the notification prompt, resulting in potential user confusion or spoofing attacks.
    (CVE-2022-45408)

  - The garbage collector could have been aborted in several states and zones and     <code>GCRuntime::finishCollection</code> may not have been called, leading to a use-after-free and     potentially exploitable crash  (CVE-2022-45409)

  - When a ServiceWorker intercepted a request with <code>FetchEvent</code>, the origin of the request was     lost after the ServiceWorker took ownership of it.  This had the effect of negating SameSite cookie     protections.  This was addressed in the spec and then in browsers.  (CVE-2022-45410)

  - Cross-Site Tracing occurs when a server will echo a request back via the Trace method, allowing an XSS     attack to access to authorization headers and cookies inaccessible to JavaScript (such as cookies     protected by HTTPOnly).  To mitigate this attack, browsers placed limits on <code>fetch()</code> and     XMLHttpRequest; however some webservers have implemented non-standard headers such as <code>X-Http-Method-     Override</code> that override the HTTP method, and made this attack possible again.  Firefox has applied     the same mitigations to the use of this and similar headers.  (CVE-2022-45411)

  - When resolving a symlink such as <code>file:///proc/self/fd/1</code>, an error message may be produced     where the symlink was resolved to a string containing unitialized memory in the buffer.  This bug only     affects Thunderbird on Unix-based operated systems (Android, Linux, MacOS). Windows is unaffected.
    (CVE-2022-45412)

  - Using the <code>S.browserfallbackurl parameter</code> parameter, an attacker could redirect a user to a     URL and cause SameSite=Strict cookies to be sent. This issue only affects Firefox for Android. Other     operating systems are not affected.  (CVE-2022-45413)

  - When downloading an HTML file, if the title of the page was formatted as a filename with a malicious     extension, Firefox may have saved the file with that extension, leading to possible system compromise if     the downloaded file was later ran.  (CVE-2022-45415)

  - Keyboard events reference strings like KeyA that were at fixed, known, and widely-spread addresses.
    Cache-based timing attacks such as Prime+Probe could have possibly figured out which keys were being     pressed.  (CVE-2022-45416)

  - Service Workers did not detect Private Browsing Mode correctly in all cases, which could have led to     Service Workers being written to disk for websites visited in Private Browsing Mode.  This would not have     persisted them in a state where they would run again, but it would have leaked Private Browsing Mode     details to disk.  (CVE-2022-45417)

  - If a custom mouse cursor is specified in CSS, under certain circumstances the cursor could have been drawn     over the browser UI, resulting in potential user confusion or spoofing attacks.  (CVE-2022-45418)

  - If the user added a security exception for an invalid TLS certificate, opened an ongoing TLS connection     with a server that used that certificate, and then deleted the exception, Firefox would have kept the     connection alive, making it seem like the certificate was still trusted.  (CVE-2022-45419)

  - Use tables inside of an iframe, an attacker could have caused iframe contents to be rendered outside the     boundaries of the iframe, resulting in potential user confusion or spoofing attacks.  (CVE-2022-45420)

  - Mozilla developers Andrew McCreight and Gabriele Svelto reported memory safety bugs present in Firefox 106     and Firefox ESR 102.4. 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-2022-45421)

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

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

    Multiple security issues were discovered in Firefox. If a user were tricked

    into opening a specially crafted website, an attacker could potentially

    exploit these to cause a denial of service, spoof the contents of the addressbar, bypass security     restrictions, cross-site tracing or execute arbitrary code. (CVE-2022-45403, CVE-2022-45404,     CVE-2022-45405, CVE-2022-45406, CVE-2022-45407, CVE-2022-45408, CVE-2022-45409, CVE-2022-45410,     CVE-2022-45411, CVE-2022-45413, CVE-2022-40674, CVE-2022-45418, CVE-2022-45419, CVE-2022-45420,     CVE-2022-45421)

    Armin Ebert discovered that Firefox did not properly manage while resolving file symlink. If a user were     tricked into opening a specially crafted weblink, an attacker could potentially exploit these to cause a     denial of service.

    (CVE-2022-45412)

    Jefferson Scher and Jayateertha Guruprasad discovered that Firefox did not properly sanitize the HTML     download file extension under certain circumstances. If a user were tricked into downloading and executing     malicious content, a remote attacker could execute arbitrary code with the privileges of the user invoking     the programs. (CVE-2022-45415)

    Erik Kraft, Martin Schwarzl, and Andrew McCreight discovered that Firefox incorrectly handled keyboard     events. An attacker could possibly use this issue to perform a timing side-channel attack and possibly     figure out which keys are being pressed. (CVE-2022-45416)

    Kagami discovered that Firefox did not detect Private Browsing Mode correctly. An attacker could possibly     use this issue to obtain sensitive information about Private Browsing Mode. (CVE-2022-45417)

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 107.0. It is, therefore, affected by multiple vulnerabilities as referenced in the mfsa2022-47 advisory.

  - Service Workers should not be able to infer information about opaque cross-origin responses; but timing     information for cross-origin media combined with Range requests might have allowed them to determine the     presence or length of a media file. (CVE-2022-45403)

  - Through a series of popup and <code>window.print()</code> calls, an attacker can cause a window to go     fullscreen without the user seeing the notification prompt, resulting in potential user confusion or     spoofing attacks. (CVE-2022-45404)

  - Freeing arbitrary <code>nsIInputStream</code>'s on a different thread than creation could have led to a     use-after-free and potentially exploitable crash. (CVE-2022-45405)

  - If an out-of-memory condition occurred when creating a JavaScript global, a JavaScript realm may be     deleted while references to it lived on in a BaseShape. This could lead to a use-after-free causing a     potentially exploitable crash. (CVE-2022-45406)

  - If an attacker loaded a font using <code>FontFace()</code> on a background worker, a use-after-free could     have occurred, leading to a potentially exploitable crash. (CVE-2022-45407)

  - Through a series of popups that reuse windowName, an attacker can cause a window to go fullscreen without     the user seeing the notification prompt, resulting in potential user confusion or spoofing attacks.
    (CVE-2022-45408)

  - The garbage collector could have been aborted in several states and zones and     <code>GCRuntime::finishCollection</code> may not have been called, leading to a use-after-free and     potentially exploitable crash (CVE-2022-45409)

  - When a ServiceWorker intercepted a request with <code>FetchEvent</code>, the origin of the request was     lost after the ServiceWorker took ownership of it.  This had the effect of negating SameSite cookie     protections.  This was addressed in the spec and then in browsers. (CVE-2022-45410)

  - Cross-Site Tracing occurs when a server will echo a request back via the Trace method, allowing an XSS     attack to access to authorization headers and cookies inaccessible to JavaScript (such as cookies     protected by HTTPOnly).  To mitigate this attack, browsers placed limits on <code>fetch()</code> and     XMLHttpRequest; however some webservers have implemented non-standard headers such as <code>X-Http-Method-     Override</code> that override the HTTP method, and made this attack possible again.  Firefox has applied     the same mitigations to the use of this and similar headers. (CVE-2022-45411)

  - When resolving a symlink such as <code>file:///proc/self/fd/1</code>, an error message may be produced     where the symlink was resolved to a string containing unitialized memory in the buffer.  This bug only     affects Firefox on Unix-based operated systems (Android, Linux, MacOS). Windows is unaffected.
    (CVE-2022-45412)

  - Using the <code>S.browserfallbackurl parameter</code> parameter, an attacker could redirect a user to a     URL and cause SameSite=Strict cookies to be sent. This issue only affects Firefox for Android. Other     operating systems are not affected. (CVE-2022-45413)

  - A flaw in XML parsing could have led to a use-after-free causing a potentially exploitable crash. In     official releases of Firefox this vulnerability is mitigated by wasm sandboxing; versions managed by Linux     distributions may have other settings. (CVE-2022-40674)

  - When downloading an HTML file, if the title of the page was formatted as a filename with a malicious     extension, Firefox may have saved the file with that extension, leading to possible system compromise if     the downloaded file was later ran. (CVE-2022-45415)

  - Keyboard events reference strings like KeyA that were at fixed, known, and widely-spread addresses.
    Cache-based timing attacks such as Prime+Probe could have possibly figured out which keys were being     pressed. (CVE-2022-45416)

  - Service Workers did not detect Private Browsing Mode correctly in all cases, which could have led to     Service Workers being written to disk for websites visited in Private Browsing Mode.  This would not have     persisted them in a state where they would run again, but it would have leaked Private Browsing Mode     details to disk. (CVE-2022-45417)

  - If a custom mouse cursor is specified in CSS, under certain circumstances the cursor could have been drawn     over the browser UI, resulting in potential user confusion or spoofing attacks. (CVE-2022-45418)

  - If the user added a security exception for an invalid TLS certificate, opened an ongoing TLS connection     with a server that used that certificate, and then deleted the exception, Firefox would have kept the     connection alive, making it seem like the certificate was still trusted. (CVE-2022-45419)

  - Using tables inside of an iframe, an attacker could have caused iframe contents to be rendered outside the     boundaries of the iframe, resulting in potential user confusion or spoofing attacks. (CVE-2022-45420)

  - Mozilla developers Andrew McCreight and Gabriele Svelto reported memory safety bugs present in Firefox 106     and Firefox ESR 102.4. 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-2022-45421)

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 macOS or Mac OS X host is prior to 107.0. It is, therefore, affected by multiple vulnerabilities as referenced in the mfsa2022-47 advisory.

  - Service Workers should not be able to infer information about opaque cross-origin responses; but timing     information for cross-origin media combined with Range requests might have allowed them to determine the     presence or length of a media file. (CVE-2022-45403)

  - Through a series of popup and <code>window.print()</code> calls, an attacker can cause a window to go     fullscreen without the user seeing the notification prompt, resulting in potential user confusion or     spoofing attacks. (CVE-2022-45404)

  - Freeing arbitrary <code>nsIInputStream</code>'s on a different thread than creation could have led to a     use-after-free and potentially exploitable crash. (CVE-2022-45405)

  - If an out-of-memory condition occurred when creating a JavaScript global, a JavaScript realm may be     deleted while references to it lived on in a BaseShape. This could lead to a use-after-free causing a     potentially exploitable crash. (CVE-2022-45406)

  - If an attacker loaded a font using <code>FontFace()</code> on a background worker, a use-after-free could     have occurred, leading to a potentially exploitable crash. (CVE-2022-45407)

  - Through a series of popups that reuse windowName, an attacker can cause a window to go fullscreen without     the user seeing the notification prompt, resulting in potential user confusion or spoofing attacks.
    (CVE-2022-45408)

  - The garbage collector could have been aborted in several states and zones and     <code>GCRuntime::finishCollection</code> may not have been called, leading to a use-after-free and     potentially exploitable crash (CVE-2022-45409)

  - When a ServiceWorker intercepted a request with <code>FetchEvent</code>, the origin of the request was     lost after the ServiceWorker took ownership of it.  This had the effect of negating SameSite cookie     protections.  This was addressed in the spec and then in browsers. (CVE-2022-45410)

  - Cross-Site Tracing occurs when a server will echo a request back via the Trace method, allowing an XSS     attack to access to authorization headers and cookies inaccessible to JavaScript (such as cookies     protected by HTTPOnly).  To mitigate this attack, browsers placed limits on <code>fetch()</code> and     XMLHttpRequest; however some webservers have implemented non-standard headers such as <code>X-Http-Method-     Override</code> that override the HTTP method, and made this attack possible again.  Firefox has applied     the same mitigations to the use of this and similar headers. (CVE-2022-45411)

  - When resolving a symlink such as <code>file:///proc/self/fd/1</code>, an error message may be produced     where the symlink was resolved to a string containing unitialized memory in the buffer.  This bug only     affects Firefox on Unix-based operated systems (Android, Linux, MacOS). Windows is unaffected.
    (CVE-2022-45412)

  - Using the <code>S.browserfallbackurl parameter</code> parameter, an attacker could redirect a user to a     URL and cause SameSite=Strict cookies to be sent. This issue only affects Firefox for Android. Other     operating systems are not affected. (CVE-2022-45413)

  - A flaw in XML parsing could have led to a use-after-free causing a potentially exploitable crash. In     official releases of Firefox this vulnerability is mitigated by wasm sandboxing; versions managed by Linux     distributions may have other settings. (CVE-2022-40674)

  - When downloading an HTML file, if the title of the page was formatted as a filename with a malicious     extension, Firefox may have saved the file with that extension, leading to possible system compromise if     the downloaded file was later ran. (CVE-2022-45415)

  - Keyboard events reference strings like KeyA that were at fixed, known, and widely-spread addresses.
    Cache-based timing attacks such as Prime+Probe could have possibly figured out which keys were being     pressed. (CVE-2022-45416)

  - Service Workers did not detect Private Browsing Mode correctly in all cases, which could have led to     Service Workers being written to disk for websites visited in Private Browsing Mode.  This would not have     persisted them in a state where they would run again, but it would have leaked Private Browsing Mode     details to disk. (CVE-2022-45417)

  - If a custom mouse cursor is specified in CSS, under certain circumstances the cursor could have been drawn     over the browser UI, resulting in potential user confusion or spoofing attacks. (CVE-2022-45418)

  - If the user added a security exception for an invalid TLS certificate, opened an ongoing TLS connection     with a server that used that certificate, and then deleted the exception, Firefox would have kept the     connection alive, making it seem like the certificate was still trusted. (CVE-2022-45419)

  - Using tables inside of an iframe, an attacker could have caused iframe contents to be rendered outside the     boundaries of the iframe, resulting in potential user confusion or spoofing attacks. (CVE-2022-45420)

  - Mozilla developers Andrew McCreight and Gabriele Svelto reported memory safety bugs present in Firefox 106     and Firefox ESR 102.4. 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-2022-45421)

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

ID	Name	Product	Family	Severity
204437	Photon OS 5.0: Mozjs PHSA-2023-5.0-0035	Nessus	PhotonOS Local Security Checks	critical
168048	GLSA-202211-06 : Mozilla Firefox: Multiple Vulnerabilities	Nessus	Gentoo Local Security Checks	critical
167744	Ubuntu 18.04 LTS / 20.04 LTS : Firefox vulnerabilities (USN-5726-1)	Nessus	Ubuntu Local Security Checks	critical
167633	Mozilla Firefox < 107.0	Nessus	Windows	critical
167632	Mozilla Firefox < 107.0	Nessus	MacOS X Local Security Checks	critical

Detections

Analytics

CVE-2022-45413

medium

Tenable Plugins

critical

critical

critical

critical

critical