`NSC_DeriveKey` inadvertently assumed that the `phKey` parameter is always non-NULL. When it was passed as NULL, a segmentation fault (SEGV) occurred, leading to crashes. This behavior conflicted with the PKCS#11 v3.0 specification, which allows `phKey` to be NULL for certain mechanisms. This vulnerability affects Firefox < 133 and Thunderbird < 133.

The version of Firefox installed on the remote macOS or Mac OS X host is prior to 133.0. It is, therefore, affected by multiple vulnerabilities as referenced in the mfsa2024-63 advisory.

  - Certain WebGL operations on Apple silicon M series devices could have lead to an out-of-bounds write and     memory corruption due to a flaw in Apple's GPU driver.   This bug only affected the application on Apple M     series hardware. Other platforms were unaffected. (CVE-2024-11691)

  - Malicious websites may have been able to user intent confirmation through tapjacking. This could have led     to users unknowingly approving the launch of external applications, potentially exposing them to     underlying vulnerabilities. (CVE-2024-11700)

  - An attacker could cause a select dropdown to be shown over another tab; this could have led to user     confusion and possible spoofing attacks. (CVE-2024-11692)

  - The incorrect domain may have been displayed in the address bar during an interrupted navigation attempt.
    This could have led to user confusion and possible spoofing attacks. (CVE-2024-11701)

  - Copying sensitive information from Private Browsing tabs on Android, such as passwords, may have     inadvertently stored data in the cloud-based clipboard history if enabled. (CVE-2024-11702)

  - The executable file warning was not presented when downloading .library-ms files.   Note: This issue only     affected Windows operating systems. Other operating systems are unaffected. (CVE-2024-11693)

  - Enhanced Tracking Protection's Strict mode may have inadvertently allowed a CSP `frame-src` bypass and     DOM-based XSS through the Google SafeFrame shim in the Web Compatibility extension. This issue could have     exposed users to malicious frames masquerading as legitimate content. (CVE-2024-11694)

  - A crafted URL containing Arabic script and whitespace characters could have hidden the true origin of the     page, resulting in a potential spoofing attack. (CVE-2024-11695)

  - On Android, Firefox may have inadvertently allowed viewing saved passwords without the required device PIN     authentication. (CVE-2024-11703)

  - The application failed to account for exceptions thrown by the `loadManifestFromFile` method during add-on     signature verification. This flaw, triggered by an invalid or unsupported extension manifest, could have     caused runtime errors that disrupted the signature validation process. As a result, the enforcement of     signature validation for unrelated add-ons may have been bypassed.  Signature validation in this context     is used to ensure that third-party applications on the user's computer have not tampered with the user's     extensions, limiting the impact of this issue. (CVE-2024-11696)

  - When handling keypress events, an attacker may have been able to trick a user into bypassing the Open     Executable File? confirmation dialog. This could have led to malicious code execution. (CVE-2024-11697)

  - A double-free issue could have occurred in `secpkcs7decoderstartdecrypt()` when handling an error path.
    Under specific conditions, the same symmetric key could have been freed twice, potentially leading to     memory corruption. (CVE-2024-11704)

  - A flaw in handling fullscreen transitions may have inadvertently caused the application to become stuck in     fullscreen mode when a modal dialog was opened during the transition. This issue left users unable to exit     fullscreen mode using standard actions like pressing Esc or accessing right-click menus, resulting in a     disrupted browsing experience until the browser is restarted.   This bug only affects the application when     running on macOS. Other operating systems are unaffected. (CVE-2024-11698)

  - <code>NSCDeriveKey</code> inadvertently assumed that the <code>phKey</code> parameter is always non-NULL.
    When it was passed as NULL, a segmentation fault (SEGV) occurred, leading to crashes. This behavior     conflicted with the PKCS#11 v3.0 specification, which allows <code>phKey</code> to be NULL for certain     mechanisms. (CVE-2024-11705)

  - A null pointer dereference may have inadvertently occurred in `pk12util`, and specifically in the     <code>SECASN1DecodeItemUtil</code> function, when handling malformed or improperly formatted input files.
    (CVE-2024-11706)

  - Missing thread synchronization primitives could have led to a data race on members of the PlaybackParams     structure. (CVE-2024-11708)

  - Memory safety bugs present in Firefox 132, Firefox ESR 128.4, and Thunderbird 128.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-2024-11699)

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

The version of Firefox installed on the remote Windows host is prior to 133.0. It is, therefore, affected by multiple vulnerabilities as referenced in the mfsa2024-63 advisory.

  - Certain WebGL operations on Apple silicon M series devices could have lead to an out-of-bounds write and     memory corruption due to a flaw in Apple's GPU driver.   This bug only affected the application on Apple M     series hardware. Other platforms were unaffected. (CVE-2024-11691)

  - Malicious websites may have been able to user intent confirmation through tapjacking. This could have led     to users unknowingly approving the launch of external applications, potentially exposing them to     underlying vulnerabilities. (CVE-2024-11700)

  - An attacker could cause a select dropdown to be shown over another tab; this could have led to user     confusion and possible spoofing attacks. (CVE-2024-11692)

  - The incorrect domain may have been displayed in the address bar during an interrupted navigation attempt.
    This could have led to user confusion and possible spoofing attacks. (CVE-2024-11701)

  - Copying sensitive information from Private Browsing tabs on Android, such as passwords, may have     inadvertently stored data in the cloud-based clipboard history if enabled. (CVE-2024-11702)

  - The executable file warning was not presented when downloading .library-ms files.   Note: This issue only     affected Windows operating systems. Other operating systems are unaffected. (CVE-2024-11693)

  - Enhanced Tracking Protection's Strict mode may have inadvertently allowed a CSP `frame-src` bypass and     DOM-based XSS through the Google SafeFrame shim in the Web Compatibility extension. This issue could have     exposed users to malicious frames masquerading as legitimate content. (CVE-2024-11694)

  - A crafted URL containing Arabic script and whitespace characters could have hidden the true origin of the     page, resulting in a potential spoofing attack. (CVE-2024-11695)

  - On Android, Firefox may have inadvertently allowed viewing saved passwords without the required device PIN     authentication. (CVE-2024-11703)

  - The application failed to account for exceptions thrown by the `loadManifestFromFile` method during add-on     signature verification. This flaw, triggered by an invalid or unsupported extension manifest, could have     caused runtime errors that disrupted the signature validation process. As a result, the enforcement of     signature validation for unrelated add-ons may have been bypassed.  Signature validation in this context     is used to ensure that third-party applications on the user's computer have not tampered with the user's     extensions, limiting the impact of this issue. (CVE-2024-11696)

  - When handling keypress events, an attacker may have been able to trick a user into bypassing the Open     Executable File? confirmation dialog. This could have led to malicious code execution. (CVE-2024-11697)

  - A double-free issue could have occurred in `secpkcs7decoderstartdecrypt()` when handling an error path.
    Under specific conditions, the same symmetric key could have been freed twice, potentially leading to     memory corruption. (CVE-2024-11704)

  - A flaw in handling fullscreen transitions may have inadvertently caused the application to become stuck in     fullscreen mode when a modal dialog was opened during the transition. This issue left users unable to exit     fullscreen mode using standard actions like pressing Esc or accessing right-click menus, resulting in a     disrupted browsing experience until the browser is restarted.   This bug only affects the application when     running on macOS. Other operating systems are unaffected. (CVE-2024-11698)

  - <code>NSCDeriveKey</code> inadvertently assumed that the <code>phKey</code> parameter is always non-NULL.
    When it was passed as NULL, a segmentation fault (SEGV) occurred, leading to crashes. This behavior     conflicted with the PKCS#11 v3.0 specification, which allows <code>phKey</code> to be NULL for certain     mechanisms. (CVE-2024-11705)

  - A null pointer dereference may have inadvertently occurred in `pk12util`, and specifically in the     <code>SECASN1DecodeItemUtil</code> function, when handling malformed or improperly formatted input files.
    (CVE-2024-11706)

  - Missing thread synchronization primitives could have led to a data race on members of the PlaybackParams     structure. (CVE-2024-11708)

  - Memory safety bugs present in Firefox 132, Firefox ESR 128.4, and Thunderbird 128.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-2024-11699)

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 133.0. It is, therefore, affected by multiple vulnerabilities as referenced in the mfsa2024-67 advisory.

  - Certain WebGL operations on Apple silicon M series devices could have lead to an out-of-bounds write and     memory corruption due to a flaw in Apple's GPU driver.   This bug only affected the application on Apple M     series hardware. Other platforms were unaffected. (CVE-2024-11691)

  - Malicious websites may have been able to user intent confirmation through tapjacking. This could have led     to users unknowingly approving the launch of external applications, potentially exposing them to     underlying vulnerabilities. (CVE-2024-11700)

  - An attacker could cause a select dropdown to be shown over another tab; this could have led to user     confusion and possible spoofing attacks. (CVE-2024-11692)

  - The incorrect domain may have been displayed in the address bar during an interrupted navigation attempt.
    This could have led to user confusion and possible spoofing attacks. (CVE-2024-11701)

  - Copying sensitive information from Private Browsing tabs on Android, such as passwords, may have     inadvertently stored data in the cloud-based clipboard history if enabled. (CVE-2024-11702)

  - The executable file warning was not presented when downloading .library-ms files.   Note: This issue only     affected Windows operating systems. Other operating systems are unaffected. (CVE-2024-11693)

  - Enhanced Tracking Protection's Strict mode may have inadvertently allowed a CSP `frame-src` bypass and     DOM-based XSS through the Google SafeFrame shim in the Web Compatibility extension. This issue could have     exposed users to malicious frames masquerading as legitimate content. (CVE-2024-11694)

  - A crafted URL containing Arabic script and whitespace characters could have hidden the true origin of the     page, resulting in a potential spoofing attack. (CVE-2024-11695)

  - The application failed to account for exceptions thrown by the `loadManifestFromFile` method during add-on     signature verification. This flaw, triggered by an invalid or unsupported extension manifest, could have     caused runtime errors that disrupted the signature validation process. As a result, the enforcement of     signature validation for unrelated add-ons may have been bypassed.  Signature validation in this context     is used to ensure that third-party applications on the user's computer have not tampered with the user's     extensions, limiting the impact of this issue. (CVE-2024-11696)

  - When handling keypress events, an attacker may have been able to trick a user into bypassing the Open     Executable File? confirmation dialog. This could have led to malicious code execution. (CVE-2024-11697)

  - A double-free issue could have occurred in `secpkcs7decoderstartdecrypt()` when handling an error path.
    Under specific conditions, the same symmetric key could have been freed twice, potentially leading to     memory corruption. (CVE-2024-11704)

  - A flaw in handling fullscreen transitions may have inadvertently caused the application to become stuck in     fullscreen mode when a modal dialog was opened during the transition. This issue left users unable to exit     fullscreen mode using standard actions like pressing Esc or accessing right-click menus, resulting in a     disrupted browsing experience until the browser is restarted.   This bug only affects the application when     running on macOS. Other operating systems are unaffected. (CVE-2024-11698)

  - <code>NSCDeriveKey</code> inadvertently assumed that the <code>phKey</code> parameter is always non-NULL.
    When it was passed as NULL, a segmentation fault (SEGV) occurred, leading to crashes. This behavior     conflicted with the PKCS#11 v3.0 specification, which allows <code>phKey</code> to be NULL for certain     mechanisms. (CVE-2024-11705)

  - A null pointer dereference may have inadvertently occurred in `pk12util`, and specifically in the     <code>SECASN1DecodeItemUtil</code> function, when handling malformed or improperly formatted input files.
    (CVE-2024-11706)

  - Missing thread synchronization primitives could have led to a data race on members of the PlaybackParams     structure. (CVE-2024-11708)

  - Memory safety bugs present in Firefox 132, Thunderbird 132, Firefox ESR 128.4, and Thunderbird 128.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-2024-11699)

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 Windows host is prior to 133.0. It is, therefore, affected by multiple vulnerabilities as referenced in the mfsa2024-67 advisory.

  - Certain WebGL operations on Apple silicon M series devices could have lead to an out-of-bounds write and     memory corruption due to a flaw in Apple's GPU driver.   This bug only affected the application on Apple M     series hardware. Other platforms were unaffected. (CVE-2024-11691)

  - Malicious websites may have been able to user intent confirmation through tapjacking. This could have led     to users unknowingly approving the launch of external applications, potentially exposing them to     underlying vulnerabilities. (CVE-2024-11700)

  - An attacker could cause a select dropdown to be shown over another tab; this could have led to user     confusion and possible spoofing attacks. (CVE-2024-11692)

  - The incorrect domain may have been displayed in the address bar during an interrupted navigation attempt.
    This could have led to user confusion and possible spoofing attacks. (CVE-2024-11701)

  - Copying sensitive information from Private Browsing tabs on Android, such as passwords, may have     inadvertently stored data in the cloud-based clipboard history if enabled. (CVE-2024-11702)

  - The executable file warning was not presented when downloading .library-ms files.   Note: This issue only     affected Windows operating systems. Other operating systems are unaffected. (CVE-2024-11693)

  - Enhanced Tracking Protection's Strict mode may have inadvertently allowed a CSP `frame-src` bypass and     DOM-based XSS through the Google SafeFrame shim in the Web Compatibility extension. This issue could have     exposed users to malicious frames masquerading as legitimate content. (CVE-2024-11694)

  - A crafted URL containing Arabic script and whitespace characters could have hidden the true origin of the     page, resulting in a potential spoofing attack. (CVE-2024-11695)

  - The application failed to account for exceptions thrown by the `loadManifestFromFile` method during add-on     signature verification. This flaw, triggered by an invalid or unsupported extension manifest, could have     caused runtime errors that disrupted the signature validation process. As a result, the enforcement of     signature validation for unrelated add-ons may have been bypassed.  Signature validation in this context     is used to ensure that third-party applications on the user's computer have not tampered with the user's     extensions, limiting the impact of this issue. (CVE-2024-11696)

  - When handling keypress events, an attacker may have been able to trick a user into bypassing the Open     Executable File? confirmation dialog. This could have led to malicious code execution. (CVE-2024-11697)

  - A double-free issue could have occurred in `secpkcs7decoderstartdecrypt()` when handling an error path.
    Under specific conditions, the same symmetric key could have been freed twice, potentially leading to     memory corruption. (CVE-2024-11704)

  - A flaw in handling fullscreen transitions may have inadvertently caused the application to become stuck in     fullscreen mode when a modal dialog was opened during the transition. This issue left users unable to exit     fullscreen mode using standard actions like pressing Esc or accessing right-click menus, resulting in a     disrupted browsing experience until the browser is restarted.   This bug only affects the application when     running on macOS. Other operating systems are unaffected. (CVE-2024-11698)

  - <code>NSCDeriveKey</code> inadvertently assumed that the <code>phKey</code> parameter is always non-NULL.
    When it was passed as NULL, a segmentation fault (SEGV) occurred, leading to crashes. This behavior     conflicted with the PKCS#11 v3.0 specification, which allows <code>phKey</code> to be NULL for certain     mechanisms. (CVE-2024-11705)

  - A null pointer dereference may have inadvertently occurred in `pk12util`, and specifically in the     <code>SECASN1DecodeItemUtil</code> function, when handling malformed or improperly formatted input files.
    (CVE-2024-11706)

  - Missing thread synchronization primitives could have led to a data race on members of the PlaybackParams     structure. (CVE-2024-11708)

  - Memory safety bugs present in Firefox 132, Thunderbird 132, Firefox ESR 128.4, and Thunderbird 128.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-2024-11699)

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
211873	Mozilla Firefox < 133.0	Nessus	MacOS X Local Security Checks	medium
211872	Mozilla Firefox < 133.0	Nessus	Windows	medium
211869	Mozilla Thunderbird < 133.0	Nessus	MacOS X Local Security Checks	medium
211868	Mozilla Thunderbird < 133.0	Nessus	Windows	medium

Detections

Analytics

CVE-2024-11705

critical

Tenable Plugins

medium

medium

medium

medium