Matrix Javascript SDK is the Matrix Client-Server SDK for JavaScript. Prior to version 19.7.0, an attacker cooperating with a malicious homeserver can construct messages appearing to have come from another person. Such messages will be marked with a grey shield on some platforms, but this may be missing in others. This attack is possible due to the matrix-js-sdk implementing a too permissive key forwarding strategy on the receiving end. Starting with version 19.7.0, the default policy for accepting key forwards has been made more strict in the matrix-js-sdk. matrix-js-sdk will now only accept forwarded keys in response to previously issued requests and only from own, verified devices. The SDK now sets a `trusted` flag on the decrypted message upon decryption, based on whether the key used to decrypt the message was received from a trusted source. Clients need to ensure that messages decrypted with a key with `trusted = false` are decorated appropriately, for example, by showing a warning for such messages. This attack requires coordination between a malicious homeserver and an attacker, and those who trust your homeservers do not need a workaround.

The Linux/Unix host has one or more packages installed that are impacted by a vulnerability without a vendor supplied patch available.

  - Matrix Javascript SDK is the Matrix Client-Server SDK for JavaScript. Prior to version 19.7.0, an attacker     cooperating with a malicious homeserver can construct messages appearing to have come from another person.
    Such messages will be marked with a grey shield on some platforms, but this may be missing in others. This     attack is possible due to the matrix-js-sdk implementing a too permissive key forwarding strategy on the     receiving end. Starting with version 19.7.0, the default policy for accepting key forwards has been made     more strict in the matrix-js-sdk. matrix-js-sdk will now only accept forwarded keys in response to     previously issued requests and only from own, verified devices. The SDK now sets a `trusted` flag on the     decrypted message upon decryption, based on whether the key used to decrypt the message was received from     a trusted source. Clients need to ensure that messages decrypted with a key with `trusted = false` are     decorated appropriately, for example, by showing a warning for such messages. This attack requires     coordination between a malicious homeserver and an attacker, and those who trust your homeservers do not     need a workaround. (CVE-2022-39249)

Note that Nessus relies on the presence of the package as reported by the vendor.

The remote CentOS Linux 7 host has a package installed that is affected by multiple vulnerabilities as referenced in the RHSA-2022:7184 advisory.

  - Matrix Javascript SDK is the Matrix Client-Server SDK for JavaScript. Starting with version 17.1.0-rc.1,     improperly formed beacon events can disrupt or impede the matrix-js-sdk from functioning properly,     potentially impacting the consumer's ability to process data safely. Note that the matrix-js-sdk can     appear to be operating normally but be excluding or corrupting runtime data presented to the consumer.
    This is patched in matrix-js-sdk v19.7.0. Redacting applicable events, waiting for the sync processor to     store data, and restarting the client are possible workarounds. Alternatively, redacting the applicable     events and clearing all storage will fix the further perceived issues. Downgrading to an unaffected     version, noting that such a version may be subject to other vulnerabilities, will additionally resolve the     issue. (CVE-2022-39236)

  - Matrix Javascript SDK is the Matrix Client-Server SDK for JavaScript. Prior to version 19.7.0, an attacker     cooperating with a malicious homeserver can construct messages appearing to have come from another person.
    Such messages will be marked with a grey shield on some platforms, but this may be missing in others. This     attack is possible due to the matrix-js-sdk implementing a too permissive key forwarding strategy on the     receiving end. Starting with version 19.7.0, the default policy for accepting key forwards has been made     more strict in the matrix-js-sdk. matrix-js-sdk will now only accept forwarded keys in response to     previously issued requests and only from own, verified devices. The SDK now sets a `trusted` flag on the     decrypted message upon decryption, based on whether the key used to decrypt the message was received from     a trusted source. Clients need to ensure that messages decrypted with a key with `trusted = false` are     decorated appropriately, for example, by showing a warning for such messages. This attack requires     coordination between a malicious homeserver and an attacker, and those who trust your homeservers do not     need a workaround. (CVE-2022-39249)

  - Matrix JavaScript SDK is the Matrix Client-Server software development kit (SDK) for JavaScript. Prior to     version 19.7.0, an attacker cooperating with a malicious homeserver could interfere with the verification     flow between two users, injecting its own cross-signing user identity in place of one of the users'     identities. This would lead to the other device trusting/verifying the user identity under the control of     the homeserver instead of the intended one. The vulnerability is a bug in the matrix-js-sdk, caused by     checking and signing user identities and devices in two separate steps, and inadequately fixing the keys     to be signed between those steps. Even though the attack is partly made possible due to the design     decision of treating cross-signing user identities as Matrix devices on the server side (with their device     ID set to the public part of the user identity key), no other examined implementations were vulnerable.
    Starting with version 19.7.0, the matrix-js-sdk has been modified to double check that the key signed is     the one that was verified instead of just referencing the key by ID. An additional check has been made to     report an error when one of the device ID matches a cross-signing key. As this attack requires     coordination between a malicious homeserver and an attacker, those who trust their homeservers do not need     a particular workaround. (CVE-2022-39250)

  - Matrix Javascript SDK is the Matrix Client-Server SDK for JavaScript. Prior to version 19.7.0, an attacker     cooperating with a malicious homeserver can construct messages that legitimately appear to have come from     another person, without any indication such as a grey shield. Additionally, a sophisticated attacker     cooperating with a malicious homeserver could employ this vulnerability to perform a targeted attack in     order to send fake to-device messages appearing to originate from another user. This can allow, for     example, to inject the key backup secret during a self-verification, to make a targeted device start using     a malicious key backup spoofed by the homeserver. These attacks are possible due to a protocol confusion     vulnerability that accepts to-device messages encrypted with Megolm instead of Olm. Starting with version     19.7.0, matrix-js-sdk has been modified to only accept Olm-encrypted to-device messages. Out of caution,     several other checks have been audited or added. This attack requires coordination between a malicious     home server and an attacker, so those who trust their home servers do not need a workaround.
    (CVE-2022-39251)

  - A same-origin policy violation could have allowed the theft of cross-origin URL entries, leaking the     result of a redirect, via `performance.getEntries()`. This vulnerability affects Firefox < 106, Firefox     ESR < 102.4, and Thunderbird < 102.4. (CVE-2022-42927)

  - Certain types of allocations were missing annotations that, if the Garbage Collector was in a specific     state, could have lead to memory corruption and a potentially exploitable crash. This vulnerability     affects Firefox < 106, Firefox ESR < 102.4, and Thunderbird < 102.4. (CVE-2022-42928)

  - If a website called `window.print()` in a particular way, it could cause a denial of service of the     browser, which may persist beyond browser restart depending on the user's session restore settings. This     vulnerability affects Firefox < 106, Firefox ESR < 102.4, and Thunderbird < 102.4. (CVE-2022-42929)

  - Mozilla developers Ashley Hale and the Mozilla Fuzzing Team reported memory safety bugs present in Firefox     105 and Firefox ESR 102.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. This vulnerability     affects Firefox < 106, Firefox ESR < 102.4, and Thunderbird < 102.4. (CVE-2022-42932)

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 thunderbird installed on the remote host is prior to 102.4.0-1. It is, therefore, affected by multiple vulnerabilities as referenced in the ALAS2-2022-1900 advisory.

    2024-05-09: CVE-2021-28429 was added to this advisory.

    Integer overflow vulnerability in av_timecode_make_string in libavutil/timecode.c in FFmpeg version 4.3.2,     allows local attackers to cause a denial of service (DoS) via crafted .mov file. (CVE-2021-28429)

    When receiving an HTML email that contained an <code>iframe</code> element, which used a     <code>srcdoc</code> attribute to define the inner HTML document, remote objects specified in the nested     document, for example images or videos, were not blocked. Rather, the network was accessed, the objects     were loaded and displayed. This vulnerability affects Thunderbird < 102.2.1 and Thunderbird < 91.13.1.
    (CVE-2022-3032)

    A flaw was found in Mozilla. The Mozilla Foundation Security Advisory describes the issue of a Thunderbird     user replying to a crafted HTML email containing a meta tag, with the meta tag having the http-     equiv='refresh' attribute and the content attribute specifying an URL. Thunderbird started a network     request to that URL, regardless of the configuration, to block remote content. In combination with certain     other HTML elements and attributes in the email, it was possible to execute JavaScript code included in     the message in the context of the message compose document. The JavaScript code was able to perform     actions including, but probably not limited to, reading and modifying the contents of the message compose     document, including the quoted original message, which could potentially contain the decrypted plaintext     of encrypted data in the crafted email. The contents could then be transmitted to the network, either to     the URL specified in the META refresh tag or to a different URL, as the JavaScript code could modify the     URL specified in the document. This bug doesn't affect users who have changed the default Message Body     display setting to 'simple html' or 'plain text.' (CVE-2022-3033)

    A flaw was found in Mozilla. The Mozilla Foundation Security Advisory describes the issue of sending a     request to the remote document when receiving an HTML email that specified to load an iframe element from     a remote location. However, Thunderbird didn't display the document. (CVE-2022-3034)

    matrix-js-sdk is a Matrix messaging protocol Client-Server SDK for JavaScript. In versions prior to 19.4.0     events sent with special strings in key places can temporarily disrupt or impede the matrix-js-sdk from     functioning properly, potentially impacting the consumer's ability to process data safely. Note that the     matrix-js-sdk can appear to be operating normally but be excluding or corrupting runtime data presented to     the consumer. This issue has been fixed in matrix-js-sdk 19.4.0 and users are advised to upgrade. Users     unable to upgrade may mitigate this issue by redacting applicable events, waiting for the sync processor     to store data, and restarting the client. Alternatively, redacting the applicable events and clearing all     storage will often fix most perceived issues. In some cases, no workarounds are possible. (CVE-2022-36059)

    A flaw was found in Mozilla. According to the Mozilla Foundation Security Advisory, Thunderbird users who     use the Matrix chat protocol are vulnerable to a data corruption issue. An attacker could potentially     cause data integrity issues by sending specially crafted messages. (CVE-2022-39236)

    A flaw was found in Mozilla. According to the Mozilla Foundation Security Advisory, Thunderbird users who     use the Matrix chat protocol are vulnerable to an impersonation attack. A malicious server administrator     could fake encrypted messages to look as if they were sent from another user on that server.
    (CVE-2022-39249)

    A flaw was found in Mozilla. According to the Mozilla Foundation Security Advisory, Thunderbird users who     use the Matrix chat protocol are vulnerable to an impersonation attack. A malicious server administrator     could interfere with cross-device verification to authenticate their own device. (CVE-2022-39250)

    A flaw was found in Mozilla. According to the Mozilla Foundation Security Advisory, Thunderbird users who     use the Matrix chat protocol are vulnerable to an impersonation attack. An attacker could spoof historical     messages from other users, and use a malicious key backup to the user's account under specific conditions     in order to exfiltrate message keys. (CVE-2022-39251)

    A vulnerability was found in expat. With this flaw, it is possible to create a situation in which parsing     is suspended while substituting in an internal entity so that XML_ResumeParser directly uses the     internalEntityProcessor as its processor. If the subsequent parse includes some unclosed tags, this will     return without calling storeRawNames to ensure that the raw versions of the tag names are stored in memory     other than the parse buffer itself. Issues occur if the parse buffer is changed or reallocated (for     example, if processing a file line by line), problems occur. Using this vulnerability in the doContent     function allows an attacker to triage a denial of service or potentially arbitrary code execution.
    (CVE-2022-40674)

    A flaw was found in Mozilla. The Mozilla Foundation Security Advisory describes the issue that when     injecting an HTML base element; some requests would ignore the CSP's base-uri settings and accept the     injected element's base instead. (CVE-2022-40956)

    Inconsistent data in instruction and data cache when creating wasm code could lead to a potentially     exploitable crash.<br>*This bug only affects Firefox on ARM64 platforms.*. This vulnerability affects     Firefox ESR < 102.3, Thunderbird < 102.3, and Firefox < 105. (CVE-2022-40957)

    A flaw was found in Mozilla. The Mozilla Foundation Security Advisory describes the issue that by     injecting a cookie with certain special characters, an attacker on a shared subdomain, which is not a     secure context,could set and overwrite cookies from a secure context, leading to session fixation and     other attacks. (CVE-2022-40958)

    A flaw was found in Mozilla. The Mozilla Foundation Security Advisory describes the issue that certain     pages did not have their FeaturePolicy fully initialized during iframe navigation, leading to a bypass     that leaked device permissions into untrusted subdocuments. (CVE-2022-40959)

    A flaw was found in Mozilla. The Mozilla Foundation Security Advisory describes the issue that concurrent     use of the URL parser with non-UTF-8 data was not thread-safe, leading to a use-after-free problem and     causing a potentially exploitable crash. (CVE-2022-40960)

    A flaw was found in Mozilla. The Mozilla Foundation Security Advisory describes the issue of Mozilla     developers Nika Layzell, Timothy Nikkel, Jeff Muizelaar, Sebastian Hengst, Andreas Pehrson, and the     Mozilla Fuzzing Team reporting memory safety bugs present in Firefox 104 and Firefox ESR 102.2. Some of     these bugs showed evidence of memory corruption and the presumption that with enough effort, some have     been exploited to run arbitrary code. (CVE-2022-40962)

    Mozilla: A same-origin policy violation could have allowed the theft of cross-origin URL entries, leaking     the result of a redirect, via performance.getEntries(). (CVE-2022-42927)

    Mozilla: Certain types of allocations were missing annotations that, if the Garbage Collector was in a     specific state, could have lead to memory corruption and a potentially exploitable crash. (CVE-2022-42928)

    A flaw was found in Mozilla. The Mozilla Foundation Security Advisory describes the issue of a website     called window.print() causing a denial of service of the browser, which may persist beyond browser restart     depending on the user's session restore settings. (CVE-2022-42929)

    Mozilla developers Ashley Hale and the Mozilla Fuzzing Team reported memory safety bugs present in Firefox     105 and Firefox ESR 102.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. This vulnerability     affects Firefox < 106, Firefox ESR < 102.4, and Thunderbird < 102.4. (CVE-2022-42932)

Tenable has extracted the preceding description block directly from the tested product 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 remote Rocky Linux 8 host has packages installed that are affected by multiple vulnerabilities as referenced in the RLSA-2022:7190 advisory.

  - Matrix Javascript SDK is the Matrix Client-Server SDK for JavaScript. Prior to version 19.7.0, an attacker     cooperating with a malicious homeserver can construct messages that legitimately appear to have come from     another person, without any indication such as a grey shield. Additionally, a sophisticated attacker     cooperating with a malicious homeserver could employ this vulnerability to perform a targeted attack in     order to send fake to-device messages appearing to originate from another user. This can allow, for     example, to inject the key backup secret during a self-verification, to make a targeted device start using     a malicious key backup spoofed by the homeserver. These attacks are possible due to a protocol confusion     vulnerability that accepts to-device messages encrypted with Megolm instead of Olm. Starting with version     19.7.0, matrix-js-sdk has been modified to only accept Olm-encrypted to-device messages. Out of caution,     several other checks have been audited or added. This attack requires coordination between a malicious     home server and an attacker, so those who trust their home servers do not need a workaround.
    (CVE-2022-39251)

  - Matrix Javascript SDK is the Matrix Client-Server SDK for JavaScript. Starting with version 17.1.0-rc.1,     improperly formed beacon events can disrupt or impede the matrix-js-sdk from functioning properly,     potentially impacting the consumer's ability to process data safely. Note that the matrix-js-sdk can     appear to be operating normally but be excluding or corrupting runtime data presented to the consumer.
    This is patched in matrix-js-sdk v19.7.0. Redacting applicable events, waiting for the sync processor to     store data, and restarting the client are possible workarounds. Alternatively, redacting the applicable     events and clearing all storage will fix the further perceived issues. Downgrading to an unaffected     version, noting that such a version may be subject to other vulnerabilities, will additionally resolve the     issue. (CVE-2022-39236)

  - Matrix Javascript SDK is the Matrix Client-Server SDK for JavaScript. Prior to version 19.7.0, an attacker     cooperating with a malicious homeserver can construct messages appearing to have come from another person.
    Such messages will be marked with a grey shield on some platforms, but this may be missing in others. This     attack is possible due to the matrix-js-sdk implementing a too permissive key forwarding strategy on the     receiving end. Starting with version 19.7.0, the default policy for accepting key forwards has been made     more strict in the matrix-js-sdk. matrix-js-sdk will now only accept forwarded keys in response to     previously issued requests and only from own, verified devices. The SDK now sets a `trusted` flag on the     decrypted message upon decryption, based on whether the key used to decrypt the message was received from     a trusted source. Clients need to ensure that messages decrypted with a key with `trusted = false` are     decorated appropriately, for example, by showing a warning for such messages. This attack requires     coordination between a malicious homeserver and an attacker, and those who trust your homeservers do not     need a workaround. (CVE-2022-39249)

  - Matrix JavaScript SDK is the Matrix Client-Server software development kit (SDK) for JavaScript. Prior to     version 19.7.0, an attacker cooperating with a malicious homeserver could interfere with the verification     flow between two users, injecting its own cross-signing user identity in place of one of the users'     identities. This would lead to the other device trusting/verifying the user identity under the control of     the homeserver instead of the intended one. The vulnerability is a bug in the matrix-js-sdk, caused by     checking and signing user identities and devices in two separate steps, and inadequately fixing the keys     to be signed between those steps. Even though the attack is partly made possible due to the design     decision of treating cross-signing user identities as Matrix devices on the server side (with their device     ID set to the public part of the user identity key), no other examined implementations were vulnerable.
    Starting with version 19.7.0, the matrix-js-sdk has been modified to double check that the key signed is     the one that was verified instead of just referencing the key by ID. An additional check has been made to     report an error when one of the device ID matches a cross-signing key. As this attack requires     coordination between a malicious homeserver and an attacker, those who trust their homeservers do not need     a particular workaround. (CVE-2022-39250)

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-5724-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, bypass Content Security Policy (CSP) or other security restrictions, or execute arbitrary code.
    These issues only affect Ubuntu 18.04 LTS, Ubuntu 20.04 LTS and Ubuntu 22.04 LTS. (CVE-2022-3266,     CVE-2022-40956, CVE-2022-40957, CVE-2022-40958, CVE-2022-40959, CVE-2022-40960, CVE-2022-40962)

    Multiple security issues were discovered in the Matrix SDK bundled with Thunderbird. An attacker could     potentially exploit these in order to impersonate another user. These issues only affect Ubuntu 18.04 LTS,     Ubuntu 20.04 LTS and Ubuntu 22.04 LTS. (CVE-2022-39236, CVE-2022-39249, CVE-2022-39250, CVE-2022-39251)

    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, or execute arbitrary code. (CVE-2022-42927, CVE-2022-42928,     CVE-2022-42929, CVE-2022-42932)

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 remote Scientific Linux 7 host has packages installed that are affected by multiple vulnerabilities as referenced in the SLSA-2022:7184-1 advisory.

  - Mozilla: Matrix SDK bundled with Thunderbird vulnerable to an impersonation attack by malicious server     administrators (CVE-2022-39249)

  - Mozilla: Matrix SDK bundled with Thunderbird vulnerable to a device verification attack (CVE-2022-39250)

  - Mozilla: Matrix SDK bundled with Thunderbird vulnerable to an impersonation attack (CVE-2022-39251)

  - Mozilla: Same-origin policy violation could have leaked cross-origin URLs (CVE-2022-42927)

  - Mozilla: Memory Corruption in JS Engine (CVE-2022-42928)

  - Mozilla: Matrix SDK bundled with Thunderbird vulnerable to a data corruption issue (CVE-2022-39236)

  - Mozilla: Denial of Service via window.print (CVE-2022-42929)

  - Mozilla: Memory safety bugs fixed in Firefox ESR 102.4 and Thunderbird 102.4 (CVE-2022-42932)

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

The remote host is affected by the vulnerability described in GLSA-202210-35 (Mozilla Thunderbird: Multiple Vulnerabilities)

  - Matrix Javascript SDK is the Matrix Client-Server SDK for JavaScript. Starting with version 17.1.0-rc.1,     improperly formed beacon events can disrupt or impede the matrix-js-sdk from functioning properly,     potentially impacting the consumer's ability to process data safely. Note that the matrix-js-sdk can     appear to be operating normally but be excluding or corrupting runtime data presented to the consumer.
    This is patched in matrix-js-sdk v19.7.0. Redacting applicable events, waiting for the sync processor to     store data, and restarting the client are possible workarounds. Alternatively, redacting the applicable     events and clearing all storage will fix the further perceived issues. Downgrading to an unaffected     version, noting that such a version may be subject to other vulnerabilities, will additionally resolve the     issue. (CVE-2022-39236)

  - Matrix Javascript SDK is the Matrix Client-Server SDK for JavaScript. Prior to version 19.7.0, an attacker     cooperating with a malicious homeserver can construct messages appearing to have come from another person.
    Such messages will be marked with a grey shield on some platforms, but this may be missing in others. This     attack is possible due to the matrix-js-sdk implementing a too permissive key forwarding strategy on the     receiving end. Starting with version 19.7.0, the default policy for accepting key forwards has been made     more strict in the matrix-js-sdk. matrix-js-sdk will now only accept forwarded keys in response to     previously issued requests and only from own, verified devices. The SDK now sets a `trusted` flag on the     decrypted message upon decryption, based on whether the key used to decrypt the message was received from     a trusted source. Clients need to ensure that messages decrypted with a key with `trusted = false` are     decorated appropriately, for example, by showing a warning for such messages. This attack requires     coordination between a malicious homeserver and an attacker, and those who trust your homeservers do not     need a workaround. (CVE-2022-39249)

  - Matrix JavaScript SDK is the Matrix Client-Server software development kit (SDK) for JavaScript. Prior to     version 19.7.0, an attacker cooperating with a malicious homeserver could interfere with the verification     flow between two users, injecting its own cross-signing user identity in place of one of the users'     identities. This would lead to the other device trusting/verifying the user identity under the control of     the homeserver instead of the intended one. The vulnerability is a bug in the matrix-js-sdk, caused by     checking and signing user identities and devices in two separate steps, and inadequately fixing the keys     to be signed between those steps. Even though the attack is partly made possible due to the design     decision of treating cross-signing user identities as Matrix devices on the server side (with their device     ID set to the public part of the user identity key), no other examined implementations were vulnerable.
    Starting with version 19.7.0, the matrix-js-sdk has been modified to double check that the key signed is     the one that was verified instead of just referencing the key by ID. An additional check has been made to     report an error when one of the device ID matches a cross-signing key. As this attack requires     coordination between a malicious homeserver and an attacker, those who trust their homeservers do not need     a particular workaround. (CVE-2022-39250)

  - Matrix Javascript SDK is the Matrix Client-Server SDK for JavaScript. Prior to version 19.7.0, an attacker     cooperating with a malicious homeserver can construct messages that legitimately appear to have come from     another person, without any indication such as a grey shield. Additionally, a sophisticated attacker     cooperating with a malicious homeserver could employ this vulnerability to perform a targeted attack in     order to send fake to-device messages appearing to originate from another user. This can allow, for     example, to inject the key backup secret during a self-verification, to make a targeted device start using     a malicious key backup spoofed by the homeserver. These attacks are possible due to a protocol confusion     vulnerability that accepts to-device messages encrypted with Megolm instead of Olm. Starting with version     19.7.0, matrix-js-sdk has been modified to only accept Olm-encrypted to-device messages. Out of caution,     several other checks have been audited or added. This attack requires coordination between a malicious     home server and an attacker, so those who trust their home servers do not need a workaround.
    (CVE-2022-39251)

  - A same-origin policy violation could have allowed the theft of cross-origin URL entries, leaking the     result of a redirect, via <code>performance.getEntries()</code>.  (CVE-2022-42927)

  - Certain types of allocations were missing annotations that, if the Garbage Collector was in a specific     state, could have lead to memory corruption and a potentially exploitable crash.  (CVE-2022-42928)

  - If a website called <code>window.print()</code> in a particular way, it could cause a denial of service of     the browser, which may persist beyond browser restart depending on the user's session restore settings.
    (CVE-2022-42929)

  - Mozilla developers Ashley Hale and the Mozilla Fuzzing Team reported memory safety bugs present in     Thunderbird 102.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-2022-42932)

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

The remote SUSE Linux SLED15 / SLED_SAP15 / SLES15 / SLES_SAP15 host has packages installed that are affected by multiple vulnerabilities as referenced in the SUSE-SU-2022:3800-1 advisory.

  - When saving or opening an email attachment on macOS, Thunderbird did not set attribute     com.apple.quarantine on the received file. If the received file was an application and the user attempted     to open it, then the application was started immediately without asking the user to confirm. This     vulnerability affects Thunderbird < 102.3. (CVE-2022-3155)

  - An out-of-bounds read can occur when decoding H264 video. This results in a potentially exploitable crash.
    This vulnerability affects Firefox ESR < 102.3, Thunderbird < 102.3, and Firefox < 105. (CVE-2022-3266)

  - Matrix Javascript SDK is the Matrix Client-Server SDK for JavaScript. Starting with version 17.1.0-rc.1,     improperly formed beacon events can disrupt or impede the matrix-js-sdk from functioning properly,     potentially impacting the consumer's ability to process data safely. Note that the matrix-js-sdk can     appear to be operating normally but be excluding or corrupting runtime data presented to the consumer.
    This is patched in matrix-js-sdk v19.7.0. Redacting applicable events, waiting for the sync processor to     store data, and restarting the client are possible workarounds. Alternatively, redacting the applicable     events and clearing all storage will fix the further perceived issues. Downgrading to an unaffected     version, noting that such a version may be subject to other vulnerabilities, will additionally resolve the     issue. (CVE-2022-39236)

  - Matrix Javascript SDK is the Matrix Client-Server SDK for JavaScript. Prior to version 19.7.0, an attacker     cooperating with a malicious homeserver can construct messages appearing to have come from another person.
    Such messages will be marked with a grey shield on some platforms, but this may be missing in others. This     attack is possible due to the matrix-js-sdk implementing a too permissive key forwarding strategy on the     receiving end. Starting with version 19.7.0, the default policy for accepting key forwards has been made     more strict in the matrix-js-sdk. matrix-js-sdk will now only accept forwarded keys in response to     previously issued requests and only from own, verified devices. The SDK now sets a `trusted` flag on the     decrypted message upon decryption, based on whether the key used to decrypt the message was received from     a trusted source. Clients need to ensure that messages decrypted with a key with `trusted = false` are     decorated appropriately, for example, by showing a warning for such messages. This attack requires     coordination between a malicious homeserver and an attacker, and those who trust your homeservers do not     need a workaround. (CVE-2022-39249)

  - Matrix JavaScript SDK is the Matrix Client-Server software development kit (SDK) for JavaScript. Prior to     version 19.7.0, an attacker cooperating with a malicious homeserver could interfere with the verification     flow between two users, injecting its own cross-signing user identity in place of one of the users'     identities. This would lead to the other device trusting/verifying the user identity under the control of     the homeserver instead of the intended one. The vulnerability is a bug in the matrix-js-sdk, caused by     checking and signing user identities and devices in two separate steps, and inadequately fixing the keys     to be signed between those steps. Even though the attack is partly made possible due to the design     decision of treating cross-signing user identities as Matrix devices on the server side (with their device     ID set to the public part of the user identity key), no other examined implementations were vulnerable.
    Starting with version 19.7.0, the matrix-js-sdk has been modified to double check that the key signed is     the one that was verified instead of just referencing the key by ID. An additional check has been made to     report an error when one of the device ID matches a cross-signing key. As this attack requires     coordination between a malicious homeserver and an attacker, those who trust their homeservers do not need     a particular workaround. (CVE-2022-39250)

  - Matrix Javascript SDK is the Matrix Client-Server SDK for JavaScript. Prior to version 19.7.0, an attacker     cooperating with a malicious homeserver can construct messages that legitimately appear to have come from     another person, without any indication such as a grey shield. Additionally, a sophisticated attacker     cooperating with a malicious homeserver could employ this vulnerability to perform a targeted attack in     order to send fake to-device messages appearing to originate from another user. This can allow, for     example, to inject the key backup secret during a self-verification, to make a targeted device start using     a malicious key backup spoofed by the homeserver. These attacks are possible due to a protocol confusion     vulnerability that accepts to-device messages encrypted with Megolm instead of Olm. Starting with version     19.7.0, matrix-js-sdk has been modified to only accept Olm-encrypted to-device messages. Out of caution,     several other checks have been audited or added. This attack requires coordination between a malicious     home server and an attacker, so those who trust their home servers do not need a workaround.
    (CVE-2022-39251)

  - When injecting an HTML base element, some requests would ignore the CSP's base-uri settings and accept the     injected element's base instead. This vulnerability affects Firefox ESR < 102.3, Thunderbird < 102.3, and     Firefox < 105. (CVE-2022-40956)

  - Inconsistent data in instruction and data cache when creating wasm code could lead to a potentially     exploitable crash.<br>*This bug only affects Firefox on ARM64 platforms.*. This vulnerability affects     Firefox ESR < 102.3, Thunderbird < 102.3, and Firefox < 105. (CVE-2022-40957)

  - By injecting a cookie with certain special characters, an attacker on a shared subdomain which is not a     secure context could set and thus overwrite cookies from a secure context, leading to session fixation and     other attacks. This vulnerability affects Firefox ESR < 102.3, Thunderbird < 102.3, and Firefox < 105.
    (CVE-2022-40958)

  - During iframe navigation, certain pages did not have their FeaturePolicy fully initialized leading to a     bypass that leaked device permissions into untrusted subdocuments. This vulnerability affects Firefox ESR     < 102.3, Thunderbird < 102.3, and Firefox < 105. (CVE-2022-40959)

  - Concurrent use of the URL parser with non-UTF-8 data was not thread-safe. This could lead to a use-after-     free causing a potentially exploitable crash. This vulnerability affects Firefox ESR < 102.3, Thunderbird     < 102.3, and Firefox < 105. (CVE-2022-40960)

  - Mozilla developers Nika Layzell, Timothy Nikkel, Sebastian Hengst, Andreas Pehrson, and the Mozilla     Fuzzing Team reported memory safety bugs present in Firefox 104 and Firefox ESR 102.2. 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.3, Thunderbird < 102.3, and     Firefox < 105. (CVE-2022-40962)

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

The remote AlmaLinux 9 host has a package installed that is affected by multiple vulnerabilities as referenced in the ALSA-2022:7178 advisory.

  - Matrix Javascript SDK is the Matrix Client-Server SDK for JavaScript. Starting with version 17.1.0-rc.1,     improperly formed beacon events can disrupt or impede the matrix-js-sdk from functioning properly,     potentially impacting the consumer's ability to process data safely. Note that the matrix-js-sdk can     appear to be operating normally but be excluding or corrupting runtime data presented to the consumer.
    This is patched in matrix-js-sdk v19.7.0. Redacting applicable events, waiting for the sync processor to     store data, and restarting the client are possible workarounds. Alternatively, redacting the applicable     events and clearing all storage will fix the further perceived issues. Downgrading to an unaffected     version, noting that such a version may be subject to other vulnerabilities, will additionally resolve the     issue. (CVE-2022-39236)

  - Matrix Javascript SDK is the Matrix Client-Server SDK for JavaScript. Prior to version 19.7.0, an attacker     cooperating with a malicious homeserver can construct messages appearing to have come from another person.
    Such messages will be marked with a grey shield on some platforms, but this may be missing in others. This     attack is possible due to the matrix-js-sdk implementing a too permissive key forwarding strategy on the     receiving end. Starting with version 19.7.0, the default policy for accepting key forwards has been made     more strict in the matrix-js-sdk. matrix-js-sdk will now only accept forwarded keys in response to     previously issued requests and only from own, verified devices. The SDK now sets a `trusted` flag on the     decrypted message upon decryption, based on whether the key used to decrypt the message was received from     a trusted source. Clients need to ensure that messages decrypted with a key with `trusted = false` are     decorated appropriately, for example, by showing a warning for such messages. This attack requires     coordination between a malicious homeserver and an attacker, and those who trust your homeservers do not     need a workaround. (CVE-2022-39249)

  - Matrix JavaScript SDK is the Matrix Client-Server software development kit (SDK) for JavaScript. Prior to     version 19.7.0, an attacker cooperating with a malicious homeserver could interfere with the verification     flow between two users, injecting its own cross-signing user identity in place of one of the users'     identities. This would lead to the other device trusting/verifying the user identity under the control of     the homeserver instead of the intended one. The vulnerability is a bug in the matrix-js-sdk, caused by     checking and signing user identities and devices in two separate steps, and inadequately fixing the keys     to be signed between those steps. Even though the attack is partly made possible due to the design     decision of treating cross-signing user identities as Matrix devices on the server side (with their device     ID set to the public part of the user identity key), no other examined implementations were vulnerable.
    Starting with version 19.7.0, the matrix-js-sdk has been modified to double check that the key signed is     the one that was verified instead of just referencing the key by ID. An additional check has been made to     report an error when one of the device ID matches a cross-signing key. As this attack requires     coordination between a malicious homeserver and an attacker, those who trust their homeservers do not need     a particular workaround. (CVE-2022-39250)

  - Matrix Javascript SDK is the Matrix Client-Server SDK for JavaScript. Prior to version 19.7.0, an attacker     cooperating with a malicious homeserver can construct messages that legitimately appear to have come from     another person, without any indication such as a grey shield. Additionally, a sophisticated attacker     cooperating with a malicious homeserver could employ this vulnerability to perform a targeted attack in     order to send fake to-device messages appearing to originate from another user. This can allow, for     example, to inject the key backup secret during a self-verification, to make a targeted device start using     a malicious key backup spoofed by the homeserver. These attacks are possible due to a protocol confusion     vulnerability that accepts to-device messages encrypted with Megolm instead of Olm. Starting with version     19.7.0, matrix-js-sdk has been modified to only accept Olm-encrypted to-device messages. Out of caution,     several other checks have been audited or added. This attack requires coordination between a malicious     home server and an attacker, so those who trust their home servers do not need a workaround.
    (CVE-2022-39251)

  - A same-origin policy violation could have allowed the theft of cross-origin URL entries, leaking the     result of a redirect, via <code>performance.getEntries()</code>.  (CVE-2022-42927)

  - Certain types of allocations were missing annotations that, if the Garbage Collector was in a specific     state, could have lead to memory corruption and a potentially exploitable crash.  (CVE-2022-42928)

  - If a website called <code>window.print()</code> in a particular way, it could cause a denial of service of     the browser, which may persist beyond browser restart depending on the user's session restore settings.
    (CVE-2022-42929)

  - Mozilla developers Ashley Hale and the Mozilla Fuzzing Team reported memory safety bugs present in     Thunderbird 102.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-2022-42932)

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

The remote Oracle Linux 8 host has a package installed that is affected by multiple vulnerabilities as referenced in the ELSA-2022-7190 advisory.

    [102.4.0-1.0.1]
    - Replaced thunderbird-redhat-default-prefs.js with thunderbird-oracle-default-prefs.js

    [102.4.0-1]
    - Update to 102.4.0 build1

Tenable has extracted the preceding description block directly from the Oracle Linux 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 remote Oracle Linux 7 host has a package installed that is affected by multiple vulnerabilities as referenced in the ELSA-2022-7184 advisory.

    - Fix for expat CVE-2022-40674

Tenable has extracted the preceding description block directly from the Oracle Linux 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 remote Oracle Linux 9 host has a package installed that is affected by multiple vulnerabilities as referenced in the ELSA-2022-7178 advisory.

    [102.4.0-1]
    - Update to 102.4.0 build1

Tenable has extracted the preceding description block directly from the Oracle Linux 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 remote AlmaLinux 8 host has a package installed that is affected by multiple vulnerabilities as referenced in the ALSA-2022:7190 advisory.

  - Matrix Javascript SDK is the Matrix Client-Server SDK for JavaScript. Starting with version 17.1.0-rc.1,     improperly formed beacon events can disrupt or impede the matrix-js-sdk from functioning properly,     potentially impacting the consumer's ability to process data safely. Note that the matrix-js-sdk can     appear to be operating normally but be excluding or corrupting runtime data presented to the consumer.
    This is patched in matrix-js-sdk v19.7.0. Redacting applicable events, waiting for the sync processor to     store data, and restarting the client are possible workarounds. Alternatively, redacting the applicable     events and clearing all storage will fix the further perceived issues. Downgrading to an unaffected     version, noting that such a version may be subject to other vulnerabilities, will additionally resolve the     issue. (CVE-2022-39236)

  - Matrix Javascript SDK is the Matrix Client-Server SDK for JavaScript. Prior to version 19.7.0, an attacker     cooperating with a malicious homeserver can construct messages appearing to have come from another person.
    Such messages will be marked with a grey shield on some platforms, but this may be missing in others. This     attack is possible due to the matrix-js-sdk implementing a too permissive key forwarding strategy on the     receiving end. Starting with version 19.7.0, the default policy for accepting key forwards has been made     more strict in the matrix-js-sdk. matrix-js-sdk will now only accept forwarded keys in response to     previously issued requests and only from own, verified devices. The SDK now sets a `trusted` flag on the     decrypted message upon decryption, based on whether the key used to decrypt the message was received from     a trusted source. Clients need to ensure that messages decrypted with a key with `trusted = false` are     decorated appropriately, for example, by showing a warning for such messages. This attack requires     coordination between a malicious homeserver and an attacker, and those who trust your homeservers do not     need a workaround. (CVE-2022-39249)

  - Matrix JavaScript SDK is the Matrix Client-Server software development kit (SDK) for JavaScript. Prior to     version 19.7.0, an attacker cooperating with a malicious homeserver could interfere with the verification     flow between two users, injecting its own cross-signing user identity in place of one of the users'     identities. This would lead to the other device trusting/verifying the user identity under the control of     the homeserver instead of the intended one. The vulnerability is a bug in the matrix-js-sdk, caused by     checking and signing user identities and devices in two separate steps, and inadequately fixing the keys     to be signed between those steps. Even though the attack is partly made possible due to the design     decision of treating cross-signing user identities as Matrix devices on the server side (with their device     ID set to the public part of the user identity key), no other examined implementations were vulnerable.
    Starting with version 19.7.0, the matrix-js-sdk has been modified to double check that the key signed is     the one that was verified instead of just referencing the key by ID. An additional check has been made to     report an error when one of the device ID matches a cross-signing key. As this attack requires     coordination between a malicious homeserver and an attacker, those who trust their homeservers do not need     a particular workaround. (CVE-2022-39250)

  - Matrix Javascript SDK is the Matrix Client-Server SDK for JavaScript. Prior to version 19.7.0, an attacker     cooperating with a malicious homeserver can construct messages that legitimately appear to have come from     another person, without any indication such as a grey shield. Additionally, a sophisticated attacker     cooperating with a malicious homeserver could employ this vulnerability to perform a targeted attack in     order to send fake to-device messages appearing to originate from another user. This can allow, for     example, to inject the key backup secret during a self-verification, to make a targeted device start using     a malicious key backup spoofed by the homeserver. These attacks are possible due to a protocol confusion     vulnerability that accepts to-device messages encrypted with Megolm instead of Olm. Starting with version     19.7.0, matrix-js-sdk has been modified to only accept Olm-encrypted to-device messages. Out of caution,     several other checks have been audited or added. This attack requires coordination between a malicious     home server and an attacker, so those who trust their home servers do not need a workaround.
    (CVE-2022-39251)

  - A same-origin policy violation could have allowed the theft of cross-origin URL entries, leaking the     result of a redirect, via <code>performance.getEntries()</code>.  (CVE-2022-42927)

  - Certain types of allocations were missing annotations that, if the Garbage Collector was in a specific     state, could have lead to memory corruption and a potentially exploitable crash.  (CVE-2022-42928)

  - If a website called <code>window.print()</code> in a particular way, it could cause a denial of service of     the browser, which may persist beyond browser restart depending on the user's session restore settings.
    (CVE-2022-42929)

  - Mozilla developers Ashley Hale and the Mozilla Fuzzing Team reported memory safety bugs present in     Thunderbird 102.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-2022-42932)

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

The remote Redhat Enterprise Linux 8 host has a package installed that is affected by multiple vulnerabilities as referenced in the RHSA-2022:7182 advisory.

    Mozilla Thunderbird is a standalone mail and newsgroup client.

    This update upgrades Thunderbird to version 102.4.0.

    Security Fix(es):

    * Mozilla: Matrix SDK bundled with Thunderbird vulnerable to an impersonation attack by malicious server     administrators (CVE-2022-39249)

    * Mozilla: Matrix SDK bundled with Thunderbird vulnerable to a device verification attack (CVE-2022-39250)

    * Mozilla: Matrix SDK bundled with Thunderbird vulnerable to an impersonation attack (CVE-2022-39251)

    * Mozilla: Same-origin policy violation could have leaked cross-origin URLs (CVE-2022-42927)

    * Mozilla: Memory Corruption in JS Engine (CVE-2022-42928)

    * Mozilla: Matrix SDK bundled with Thunderbird vulnerable to a data corruption issue (CVE-2022-39236)

    * Mozilla: Denial of Service via window.print (CVE-2022-42929)

    * Mozilla: Memory safety bugs fixed in Firefox ESR 102.4 and Thunderbird 102.4 (CVE-2022-42932)

    For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and     other related information, refer to the CVE page(s) listed in the References section.

Tenable has extracted the preceding description block directly from the Red Hat Enterprise Linux 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 remote Redhat Enterprise Linux 7 host has a package installed that is affected by multiple vulnerabilities as referenced in the RHSA-2022:7184 advisory.

    Mozilla Thunderbird is a standalone mail and newsgroup client.

    This update upgrades Thunderbird to version 102.4.0.

    Security Fix(es):

    * Mozilla: Matrix SDK bundled with Thunderbird vulnerable to an impersonation attack by malicious server     administrators (CVE-2022-39249)

    * Mozilla: Matrix SDK bundled with Thunderbird vulnerable to a device verification attack (CVE-2022-39250)

    * Mozilla: Matrix SDK bundled with Thunderbird vulnerable to an impersonation attack (CVE-2022-39251)

    * Mozilla: Same-origin policy violation could have leaked cross-origin URLs (CVE-2022-42927)

    * Mozilla: Memory Corruption in JS Engine (CVE-2022-42928)

    * Mozilla: Matrix SDK bundled with Thunderbird vulnerable to a data corruption issue (CVE-2022-39236)

    * Mozilla: Denial of Service via window.print (CVE-2022-42929)

    * Mozilla: Memory safety bugs fixed in Firefox ESR 102.4 and Thunderbird 102.4 (CVE-2022-42932)

    For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and     other related information, refer to the CVE page(s) listed in the References section.

Tenable has extracted the preceding description block directly from the Red Hat Enterprise Linux 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 remote Redhat Enterprise Linux 8 host has a package installed that is affected by multiple vulnerabilities as referenced in the RHSA-2022:7190 advisory.

    Mozilla Thunderbird is a standalone mail and newsgroup client.

    This update upgrades Thunderbird to version 102.4.0.

    Security Fix(es):

    * Mozilla: Matrix SDK bundled with Thunderbird vulnerable to an impersonation attack by malicious server     administrators (CVE-2022-39249)

    * Mozilla: Matrix SDK bundled with Thunderbird vulnerable to a device verification attack (CVE-2022-39250)

    * Mozilla: Matrix SDK bundled with Thunderbird vulnerable to an impersonation attack (CVE-2022-39251)

    * Mozilla: Same-origin policy violation could have leaked cross-origin URLs (CVE-2022-42927)

    * Mozilla: Memory Corruption in JS Engine (CVE-2022-42928)

    * Mozilla: Matrix SDK bundled with Thunderbird vulnerable to a data corruption issue (CVE-2022-39236)

    * Mozilla: Denial of Service via window.print (CVE-2022-42929)

    * Mozilla: Memory safety bugs fixed in Firefox ESR 102.4 and Thunderbird 102.4 (CVE-2022-42932)

    For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and     other related information, refer to the CVE page(s) listed in the References section.

Tenable has extracted the preceding description block directly from the Red Hat Enterprise Linux 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 remote Redhat Enterprise Linux 8 host has a package installed that is affected by multiple vulnerabilities as referenced in the RHSA-2022:7181 advisory.

    Mozilla Thunderbird is a standalone mail and newsgroup client.

    This update upgrades Thunderbird to version 102.4.0.

    Security Fix(es):

    * Mozilla: Matrix SDK bundled with Thunderbird vulnerable to an impersonation attack by malicious server     administrators (CVE-2022-39249)

    * Mozilla: Matrix SDK bundled with Thunderbird vulnerable to a device verification attack (CVE-2022-39250)

    * Mozilla: Matrix SDK bundled with Thunderbird vulnerable to an impersonation attack (CVE-2022-39251)

    * Mozilla: Same-origin policy violation could have leaked cross-origin URLs (CVE-2022-42927)

    * Mozilla: Memory Corruption in JS Engine (CVE-2022-42928)

    * Mozilla: Matrix SDK bundled with Thunderbird vulnerable to a data corruption issue (CVE-2022-39236)

    * Mozilla: Denial of Service via window.print (CVE-2022-42929)

    * Mozilla: Memory safety bugs fixed in Firefox ESR 102.4 and Thunderbird 102.4 (CVE-2022-42932)

    For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and     other related information, refer to the CVE page(s) listed in the References section.

Tenable has extracted the preceding description block directly from the Red Hat Enterprise Linux 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 remote Redhat Enterprise Linux 8 host has a package installed that is affected by multiple vulnerabilities as referenced in the RHSA-2022:7183 advisory.

    Mozilla Thunderbird is a standalone mail and newsgroup client.

    This update upgrades Thunderbird to version 102.4.0.

    Security Fix(es):

    * Mozilla: Matrix SDK bundled with Thunderbird vulnerable to an impersonation attack by malicious server     administrators (CVE-2022-39249)

    * Mozilla: Matrix SDK bundled with Thunderbird vulnerable to a device verification attack (CVE-2022-39250)

    * Mozilla: Matrix SDK bundled with Thunderbird vulnerable to an impersonation attack (CVE-2022-39251)

    * Mozilla: Same-origin policy violation could have leaked cross-origin URLs (CVE-2022-42927)

    * Mozilla: Memory Corruption in JS Engine (CVE-2022-42928)

    * Mozilla: Matrix SDK bundled with Thunderbird vulnerable to a data corruption issue (CVE-2022-39236)

    * Mozilla: Denial of Service via window.print (CVE-2022-42929)

    * Mozilla: Memory safety bugs fixed in Firefox ESR 102.4 and Thunderbird 102.4 (CVE-2022-42932)

    For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and     other related information, refer to the CVE page(s) listed in the References section.

Tenable has extracted the preceding description block directly from the Red Hat Enterprise Linux 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 remote Redhat Enterprise Linux 9 host has a package installed that is affected by multiple vulnerabilities as referenced in the RHSA-2022:7178 advisory.

    Mozilla Thunderbird is a standalone mail and newsgroup client.

    This update upgrades Thunderbird to version 102.4.0.

    Security Fix(es):

    * Mozilla: Matrix SDK bundled with Thunderbird vulnerable to an impersonation attack by malicious server     administrators (CVE-2022-39249)

    * Mozilla: Matrix SDK bundled with Thunderbird vulnerable to a device verification attack (CVE-2022-39250)

    * Mozilla: Matrix SDK bundled with Thunderbird vulnerable to an impersonation attack (CVE-2022-39251)

    * Mozilla: Same-origin policy violation could have leaked cross-origin URLs (CVE-2022-42927)

    * Mozilla: Memory Corruption in JS Engine (CVE-2022-42928)

    * Mozilla: Matrix SDK bundled with Thunderbird vulnerable to a data corruption issue (CVE-2022-39236)

    * Mozilla: Denial of Service via window.print (CVE-2022-42929)

    * Mozilla: Memory safety bugs fixed in Firefox ESR 102.4 and Thunderbird 102.4 (CVE-2022-42932)

    For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and     other related information, refer to the CVE page(s) listed in the References section.

Tenable has extracted the preceding description block directly from the Red Hat Enterprise Linux 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 mozilla-thunderbird installed on the remote host is prior to 102.3.1. It is, therefore, affected by multiple vulnerabilities as referenced in the SSA:2022-273-01 advisory.

  - Matrix Javascript SDK is the Matrix Client-Server SDK for JavaScript. Starting with version 17.1.0-rc.1,     improperly formed beacon events can disrupt or impede the matrix-js-sdk from functioning properly,     potentially impacting the consumer's ability to process data safely. Note that the matrix-js-sdk can     appear to be operating normally but be excluding or corrupting runtime data presented to the consumer.
    This is patched in matrix-js-sdk v19.7.0. Redacting applicable events, waiting for the sync processor to     store data, and restarting the client are possible workarounds. Alternatively, redacting the applicable     events and clearing all storage will fix the further perceived issues. Downgrading to an unaffected     version, noting that such a version may be subject to other vulnerabilities, will additionally resolve the     issue. (CVE-2022-39236)

  - Matrix Javascript SDK is the Matrix Client-Server SDK for JavaScript. Prior to version 19.7.0, an attacker     cooperating with a malicious homeserver can construct messages appearing to have come from another person.
    Such messages will be marked with a grey shield on some platforms, but this may be missing in others. This     attack is possible due to the matrix-js-sdk implementing a too permissive key forwarding strategy on the     receiving end. Starting with version 19.7.0, the default policy for accepting key forwards has been made     more strict in the matrix-js-sdk. matrix-js-sdk will now only accept forwarded keys in response to     previously issued requests and only from own, verified devices. The SDK now sets a `trusted` flag on the     decrypted message upon decryption, based on whether the key used to decrypt the message was received from     a trusted source. Clients need to ensure that messages decrypted with a key with `trusted = false` are     decorated appropriately, for example, by showing a warning for such messages. This attack requires     coordination between a malicious homeserver and an attacker, and those who trust your homeservers do not     need a workaround. (CVE-2022-39249)

  - Matrix JavaScript SDK is the Matrix Client-Server software development kit (SDK) for JavaScript. Prior to     version 19.7.0, an attacker cooperating with a malicious homeserver could interfere with the verification     flow between two users, injecting its own cross-signing user identity in place of one of the users'     identities. This would lead to the other device trusting/verifying the user identity under the control of     the homeserver instead of the intended one. The vulnerability is a bug in the matrix-js-sdk, caused by     checking and signing user identities and devices in two separate steps, and inadequately fixing the keys     to be signed between those steps. Even though the attack is partly made possible due to the design     decision of treating cross-signing user identities as Matrix devices on the server side (with their device     ID set to the public part of the user identity key), no other examined implementations were vulnerable.
    Starting with version 19.7.0, the matrix-js-sdk has been modified to double check that the key signed is     the one that was verified instead of just referencing the key by ID. An additional check has been made to     report an error when one of the device ID matches a cross-signing key. As this attack requires     coordination between a malicious homeserver and an attacker, those who trust their homeservers do not need     a particular workaround. (CVE-2022-39250)

  - Matrix Javascript SDK is the Matrix Client-Server SDK for JavaScript. Prior to version 19.7.0, an attacker     cooperating with a malicious homeserver can construct messages that legitimately appear to have come from     another person, without any indication such as a grey shield. Additionally, a sophisticated attacker     cooperating with a malicious homeserver could employ this vulnerability to perform a targeted attack in     order to send fake to-device messages appearing to originate from another user. This can allow, for     example, to inject the key backup secret during a self-verification, to make a targeted device start using     a malicious key backup spoofed by the homeserver. These attacks are possible due to a protocol confusion     vulnerability that accepts to-device messages encrypted with Megolm instead of Olm. Starting with version     19.7.0, matrix-js-sdk has been modified to only accept Olm-encrypted to-device messages. Out of caution,     several other checks have been audited or added. This attack requires coordination between a malicious     home server and an attacker, so those who trust their home servers do not need a workaround.
    (CVE-2022-39251)

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 Thunderbird installed on the remote macOS or Mac OS X host is prior to 102.3.1. It is, therefore, affected by a vulnerability as referenced in the mfsa2022-43 advisory.

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 Thunderbird installed on the remote Windows host is prior to 102.3.1. It is, therefore, affected by a vulnerability as referenced in the mfsa2022-43 advisory.

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 FreeBSD installed on the remote host is prior to tested version. It is, therefore, affected by multiple vulnerabilities as referenced in the cb902a77-3f43-11ed-9402-901b0e9408dc advisory.

  - Matrix Javascript SDK is the Matrix Client-Server SDK for JavaScript. Prior to version 19.7.0, an attacker     cooperating with a malicious homeserver can construct messages that legitimately appear to have come from     another person, without any indication such as a grey shield. Additionally, a sophisticated attacker     cooperating with a malicious homeserver could employ this vulnerability to perform a targeted attack in     order to send fake to-device messages appearing to originate from another user. This can allow, for     example, to inject the key backup secret during a self-verification, to make a targeted device start using     a malicious key backup spoofed by the homeserver. These attacks are possible due to a protocol confusion     vulnerability that accepts to-device messages encrypted with Megolm instead of Olm. Starting with version     19.7.0, matrix-js-sdk has been modified to only accept Olm-encrypted to-device messages. Out of caution,     several other checks have been audited or added. This attack requires coordination between a malicious     home server and an attacker, so those who trust their home servers do not need a workaround.
    (CVE-2022-39251)

  - Matrix Javascript SDK is the Matrix Client-Server SDK for JavaScript. Starting with version 17.1.0-rc.1,     improperly formed beacon events can disrupt or impede the matrix-js-sdk from functioning properly,     potentially impacting the consumer's ability to process data safely. Note that the matrix-js-sdk can     appear to be operating normally but be excluding or corrupting runtime data presented to the consumer.
    This is patched in matrix-js-sdk v19.7.0. Redacting applicable events, waiting for the sync processor to     store data, and restarting the client are possible workarounds. Alternatively, redacting the applicable     events and clearing all storage will fix the further perceived issues. Downgrading to an unaffected     version, noting that such a version may be subject to other vulnerabilities, will additionally resolve the     issue. (CVE-2022-39236)

  - Matrix Javascript SDK is the Matrix Client-Server SDK for JavaScript. Prior to version 19.7.0, an attacker     cooperating with a malicious homeserver can construct messages appearing to have come from another person.
    Such messages will be marked with a grey shield on some platforms, but this may be missing in others. This     attack is possible due to the matrix-js-sdk implementing a too permissive key forwarding strategy on the     receiving end. Starting with version 19.7.0, the default policy for accepting key forwards has been made     more strict in the matrix-js-sdk. matrix-js-sdk will now only accept forwarded keys in response to     previously issued requests and only from own, verified devices. The SDK now sets a `trusted` flag on the     decrypted message upon decryption, based on whether the key used to decrypt the message was received from     a trusted source. Clients need to ensure that messages decrypted with a key with `trusted = false` are     decorated appropriately, for example, by showing a warning for such messages. This attack requires     coordination between a malicious homeserver and an attacker, and those who trust your homeservers do not     need a workaround. (CVE-2022-39249)

  - Matrix JavaScript SDK is the Matrix Client-Server software development kit (SDK) for JavaScript. Prior to     version 19.7.0, an attacker cooperating with a malicious homeserver could interfere with the verification     flow between two users, injecting its own cross-signing user identity in place of one of the users'     identities. This would lead to the other device trusting/verifying the user identity under the control of     the homeserver instead of the intended one. The vulnerability is a bug in the matrix-js-sdk, caused by     checking and signing user identities and devices in two separate steps, and inadequately fixing the keys     to be signed between those steps. Even though the attack is partly made possible due to the design     decision of treating cross-signing user identities as Matrix devices on the server side (with their device     ID set to the public part of the user identity key), no other examined implementations were vulnerable.
    Starting with version 19.7.0, the matrix-js-sdk has been modified to double check that the key signed is     the one that was verified instead of just referencing the key by ID. An additional check has been made to     report an error when one of the device ID matches a cross-signing key. As this attack requires     coordination between a malicious homeserver and an attacker, those who trust their homeservers do not need     a particular workaround. (CVE-2022-39250)

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
225002	Linux Distros Unpatched Vulnerability : CVE-2022-39249	Nessus	Misc.	high
208577	CentOS 7 : thunderbird (RHSA-2022:7184)	Nessus	CentOS Local Security Checks	high
168453	Amazon Linux 2 : thunderbird (ALAS-2022-1900)	Nessus	Amazon Linux Local Security Checks	high
167823	Rocky Linux 8 : thunderbird (RLSA-2022:7190)	Nessus	Rocky Linux Local Security Checks	high
167286	Ubuntu 18.04 LTS / 20.04 LTS / 22.04 LTS : Thunderbird vulnerabilities (USN-5724-1)	Nessus	Ubuntu Local Security Checks	high
166777	Scientific Linux Security Update : thunderbird on SL7.x x86_64 (2022:7184)	Nessus	Scientific Linux Local Security Checks	high
166745	GLSA-202210-35 : Mozilla Thunderbird: Multiple Vulnerabilities	Nessus	Gentoo Local Security Checks	high
166692	SUSE SLED15 / SLES15 Security Update : MozillaThunderbird (SUSE-SU-2022:3800-1)	Nessus	SuSE Local Security Checks	high
166615	AlmaLinux 9 : thunderbird (ALSA-2022:7178)	Nessus	Alma Linux Local Security Checks	high
166594	Oracle Linux 8 : thunderbird (ELSA-2022-7190)	Nessus	Oracle Linux Local Security Checks	high
166575	Oracle Linux 7 : thunderbird (ELSA-2022-7184)	Nessus	Oracle Linux Local Security Checks	high
166573	Oracle Linux 9 : thunderbird (ELSA-2022-7178)	Nessus	Oracle Linux Local Security Checks	high
166522	AlmaLinux 8 : thunderbird (ALSA-2022:7190)	Nessus	Alma Linux Local Security Checks	high
166490	RHEL 8 : thunderbird (RHSA-2022:7182)	Nessus	Red Hat Local Security Checks	high
166486	RHEL 7 : thunderbird (RHSA-2022:7184)	Nessus	Red Hat Local Security Checks	high
166485	RHEL 8 : thunderbird (RHSA-2022:7190)	Nessus	Red Hat Local Security Checks	high
166484	RHEL 8 : thunderbird (RHSA-2022:7181)	Nessus	Red Hat Local Security Checks	high
166483	RHEL 8 : thunderbird (RHSA-2022:7183)	Nessus	Red Hat Local Security Checks	high
166482	RHEL 9 : thunderbird (RHSA-2022:7178)	Nessus	Red Hat Local Security Checks	high
165598	Slackware Linux 15.0 / current mozilla-thunderbird Multiple Vulnerabilities (SSA:2022-273-01)	Nessus	Slackware Local Security Checks	high
165571	Mozilla Thunderbird < 102.3.1	Nessus	MacOS X Local Security Checks	high
165570	Mozilla Thunderbird < 102.3.1	Nessus	Windows	high
165517	FreeBSD : Matrix clients -- several vulnerabilities (cb902a77-3f43-11ed-9402-901b0e9408dc)	Nessus	FreeBSD Local Security Checks	high

Detections

Analytics

CVE-2022-39249

high

Tenable Plugins

high

high

high

high

high

high

high

high

high

high

high

high

high

high

high

high

high

high

high

high

high

high

high