The remote CentOS Linux 7 host has a package installed that is affected by multiple vulnerabilities as referenced in the RHSA-2022:8555 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. This vulnerability affects Firefox ESR < 102.5, Thunderbird < 102.5,     and Firefox < 107. (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. This vulnerability affects Firefox ESR < 102.5, Thunderbird < 102.5, and Firefox < 107.
    (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. This vulnerability affects Firefox ESR < 102.5,     Thunderbird < 102.5, and Firefox < 107. (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. This vulnerability affects Firefox ESR < 102.5, Thunderbird < 102.5, and     Firefox < 107. (CVE-2022-45406)

  - 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. This     vulnerability affects Firefox ESR < 102.5, Thunderbird < 102.5, and Firefox < 107. (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. This vulnerability affects Firefox ESR < 102.5, Thunderbird < 102.5, and     Firefox < 107. (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. This vulnerability affects Firefox ESR <     102.5, Thunderbird < 102.5, and Firefox < 107. (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. Thunderbird has     applied the same mitigations to the use of this and similar headers. This vulnerability affects Firefox     ESR < 102.5, Thunderbird < 102.5, and Firefox < 107. (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. <br>*This bug only     affects Thunderbird on Unix-based operated systems (Android, Linux, MacOS). Windows is unaffected.*. This     vulnerability affects Firefox ESR < 102.5, Thunderbird < 102.5, and Firefox < 107. (CVE-2022-45412)

  - 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. This vulnerability affects Firefox ESR < 102.5, Thunderbird < 102.5, and Firefox < 107.
    (CVE-2022-45416)

  - 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. This vulnerability affects     Firefox ESR < 102.5, Thunderbird < 102.5, and Firefox < 107. (CVE-2022-45418)

  - 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. This vulnerability     affects Firefox ESR < 102.5, Thunderbird < 102.5, and Firefox < 107. (CVE-2022-45420)

  - Mozilla developers Andrew McCreight and Gabriele Svelto reported memory safety bugs present in Thunderbird     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. This vulnerability affects Firefox ESR < 102.5,     Thunderbird < 102.5, and Firefox < 107. (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 mozilla-firefox installed on the remote host is prior to 102.5.0esr / 107.0. It is, therefore, affected by multiple vulnerabilities as referenced in the SSA:2022-320-02 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)

  - 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)

  - 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)

  - 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)

  - 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 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.

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

    Multiple security issues were discovered in Thunderbird. If a user were tricked into opening a specially     crafted website in a browsing context, an attacker could potentially exploit these to cause a denial of     service, obtain sensitive information, bypass security restrictions, cross-site tracing, or execute     arbitrary code. (CVE-2022-45403, CVE-2022-45404, CVE-2022-45405, CVE-2022-45406, CVE-2022-45408,     CVE-2022-45409, CVE-2022-45410, CVE-2022-45411, CVE-2022-45418, CVE-2022-45420, CVE-2022-45421,     CVE-2022-46878, CVE-2022-46880, CVE-2022-46881, CVE-2022-46882, CVE-2023-23605)

    Armin Ebert discovered that Thunderbird did not properly manage memory 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)

    Sarah Jamie Lewis discovered that Thunderbird did not properly manage network request while handling HTML     emails with certain tags. If a user were tricked into opening a specially HTML email, an attacker could     potentially exploit these issue and load remote content regardless of a configuration to block remote     content. (CVE-2022-45414)

    Erik Kraft, Martin Schwarzl, and Andrew McCreight discovered that Thunderbird 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)

    It was discovered that Thunderbird was using an out-of-date libusrsctp library. An attacker could possibly     use this library to perform a reentrancy issue on Thunderbird. (CVE-2022-46871)

    Nika Layzell discovered that Thunderbird was not performing a check on paste received from cross-     processes. An attacker could potentially exploit this to obtain sensitive information. (CVE-2022-46872)

    Matthias Zoellner discovered that Thunderbird was not keeping the filename ending intact when using the     drag-and-drop event. An attacker could possibly use this issue to add a file with a malicious extension,     leading to execute arbitrary code. (CVE-2022-46874)

    Hafiizh discovered that Thunderbird was not properly handling fullscreen notifications when the window     goes into fullscreen mode. An attacker could possibly use this issue to spoof the user and obtain     sensitive information. (CVE-2022-46877)

    Tom Schuster discovered that Thunderbird was not performing a validation check on GTK drag data. An     attacker could potentially exploits this to obtain sensitive information. (CVE-2023-23598)

    Vadim discovered that Thunderbird was not properly sanitizing a curl command output when copying a network     request from the developer tools panel. An attacker could potentially exploits this to hide and execute     arbitrary commands. (CVE-2023-23599)

    Luan Herrera discovered that Thunderbird was not stopping navigation when dragging a URL from a cross-     origin iframe into the same tab. An attacker potentially exploits this to spoof the user. (CVE-2023-23601)

    Dave Vandyke discovered that Thunderbird did not properly implement CSP policy when creating a WebSocket     in a WebWorker. An attacker who was able to inject markup into a page otherwise protected by a Content     Security Policy may have been able to inject an executable script. (CVE-2023-23602)

    Dan Veditz discovered that Thunderbird did not properly implement CSP policy on regular expression when     using console.log. An attacker potentially exploits this to exfiltrate data. (CVE-2023-23603)

    It was discovered that Thunderbird did not properly check the Certificate OCSP revocation status when     verifying S/Mime signatures. An attacker could possibly use this issue to bypass signature validation     check by sending email signed with a revoked certificate. (CVE-2023-0430)

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.

ID	Name	Product	Family	Published	Updated	Severity
168313	CentOS 7 : thunderbird (RHSA-2022:8555)	Nessus	CentOS Local Security Checks	12/1/2022	10/9/2024	critical
167774	Slackware Linux 15.0 / current mozilla-firefox Multiple Vulnerabilities (SSA:2022-320-02)	Nessus	Slackware Local Security Checks	11/17/2022	1/5/2023	critical
167632	Mozilla Firefox < 107.0	Nessus	MacOS X Local Security Checks	11/16/2022	10/25/2023	critical
171009	Ubuntu 18.04 LTS / 20.04 LTS / 22.04 LTS : Thunderbird vulnerabilities (USN-5824-1)	Nessus	Ubuntu Local Security Checks	2/6/2023	8/28/2024	critical

Detections

Analytics

Plugins Search

critical

critical

critical

critical