It was possible to mutate a JavaScript object so that the JIT could crash while tracing it. This vulnerability affects Firefox < 125.

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

    Multiple vulnerabilities have been discovered in Mozilla Firefox. Please review the CVE identifiers     referenced below for details.

Tenable has extracted the preceding description block directly from the Gentoo 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 Fedora 40 host has a package installed that is affected by multiple vulnerabilities as referenced in the FEDORA-2024-c6a1d4e0ec advisory.

    - New upstream release (125.0)

    ----

    - New upstream release (124.0.2)

Tenable has extracted the preceding description block directly from the Fedora 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 Ubuntu 20.04 LTS host has packages installed that are affected by multiple vulnerabilities as referenced in the USN-6747-1 advisory.

    Multiple security issues were discovered in Firefox. If a user were tricked into opening a specially     crafted website, an attacker could potentially exploit these to cause a denial of service, obtain     sensitive information across domains, or execute arbitrary code. (CVE-2024-3852, CVE-2024-3864,     CVE-2024-3865)

    Bartek Nowotarski discovered that Firefox did not properly limit HTTP/2 CONTINUATION frames. An attacker     could potentially exploit this issue to cause a denial of service. (CVE-2024-3302)

    Gary Kwong discovered that Firefox did not properly manage memory when running garbage collection during     realm initialization. An attacker could potentially exploit this issue to cause a denial of service, or     execute arbitrary code. (CVE-2024-3853)

    Lukas Bernhard discovered that Firefox did not properly manage memory during JIT optimisations, leading to     an out-of-bounds read vulnerability. An attacker could possibly use this issue to cause a denial of     service or expose sensitive information. (CVE-2024-3854, CVE-2024-3855)

    Nan Wang discovered that Firefox did not properly manage memory during WASM garbage collection. An     attacker could potentially exploit this issue to cause a denial of service, or execute arbitrary code.
    (CVE-2024-3856)

    Lukas Bernhard discovered that Firefox did not properly manage memory when handling JIT created code     during garbage collection. An attacker could potentially exploit this issue to cause a denial of service,     or execute arbitrary code. (CVE-2024-3857)

    Lukas Bernhard discovered that Firefox did not properly manage memory when tracing in JIT. An attacker     could potentially exploit this issue to cause a denial of service. (CVE-2024-3858)

    Ronald Crane discovered that Firefox did not properly manage memory in the OpenType sanitizer on 32-bit     devices, leading to an out-of-bounds read

    vulnerability. An attacker could possibly use this issue to cause a denial of service or expose sensitive     information. (CVE-2024-3859)

    Garry Kwong discovered that Firefox did not properly manage memory when tracing empty shape lists in JIT.
    An attacker could potentially exploit

    this issue to cause a denial of service. (CVE-2024-3860)

    Ronald Crane discovered that Firefox did not properly manage memory when handling an AlignedBuffer. An     attacker could potentially exploit this

    issue to cause denial of service, or execute arbitrary code.

    (CVE-2024-3861)

    Ronald Crane discovered that Firefox did not properly manage memory when handling code in MarkStack. An     attacker could possibly use this issue to cause a denial of service or execute arbitrary code.
    (CVE-2024-3862)

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 Fedora 38 host has a package installed that is affected by multiple vulnerabilities as referenced in the FEDORA-2024-966e16bfa3 advisory.

    - New upstream release (125.0)

Tenable has extracted the preceding description block directly from the Fedora 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 Fedora 39 host has a package installed that is affected by multiple vulnerabilities as referenced in the FEDORA-2024-121f5cec9f advisory.

    - New upstream release (125.0)

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

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

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

  - GetBoundName could return the wrong version of an object when JIT optimizations were applied.
    (CVE-2024-3852)

  - A use-after-free could result if a JavaScript realm was in the process of being initialized when a garbage     collection started. (CVE-2024-3853)

  - In some code patterns the JIT incorrectly optimized switch statements and generated code with out-of-     bounds-reads. (CVE-2024-3854)

  - In certain cases the JIT incorrectly optimized MSubstr operations, which led to out-of-bounds reads.
    (CVE-2024-3855)

  - A use-after-free could occur during WASM execution if garbage collection ran during the creation of an     array. (CVE-2024-3856)

  - The JIT created incorrect code for arguments in certain cases. This led to potential use-after-free     crashes during garbage collection. (CVE-2024-3857)

  - It was possible to mutate a JavaScript object so that the JIT could crash while tracing it.
    (CVE-2024-3858)

  - On 32-bit versions there were integer-overflows that led to an out-of-bounds-read that potentially could     be triggered by a malformed OpenType font. (CVE-2024-3859)

  - An out-of-memory condition during object initialization could result in an empty shape list. If the JIT     subsequently traced the object it would crash. (CVE-2024-3860)

  - If an AlignedBuffer were assigned to itself, the subsequent self-move could result in an incorrect     reference count and later use-after-free. (CVE-2024-3861)

  - The MarkStack assignment operator, part of the JavaScript engine, could access uninitialized memory if it     were used in a self-assignment. (CVE-2024-3862)

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

  - There was no limit to the number of HTTP/2 CONTINUATION frames that would be processed. A server could     abuse this to create an Out of Memory condition in the browser. (CVE-2024-3302)

  - Memory safety bug present in Firefox 124, Firefox ESR 115.9, and Thunderbird 115.9. This bug showed     evidence of memory corruption and we presume that with enough effort this could have been exploited to run     arbitrary code. (CVE-2024-3864)

  - Memory safety bugs present in Firefox 124. 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-3865)

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

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

  - GetBoundName could return the wrong version of an object when JIT optimizations were applied.
    (CVE-2024-3852)

  - A use-after-free could result if a JavaScript realm was in the process of being initialized when a garbage     collection started. (CVE-2024-3853)

  - In some code patterns the JIT incorrectly optimized switch statements and generated code with out-of-     bounds-reads. (CVE-2024-3854)

  - In certain cases the JIT incorrectly optimized MSubstr operations, which led to out-of-bounds reads.
    (CVE-2024-3855)

  - A use-after-free could occur during WASM execution if garbage collection ran during the creation of an     array. (CVE-2024-3856)

  - The JIT created incorrect code for arguments in certain cases. This led to potential use-after-free     crashes during garbage collection. (CVE-2024-3857)

  - It was possible to mutate a JavaScript object so that the JIT could crash while tracing it.
    (CVE-2024-3858)

  - On 32-bit versions there were integer-overflows that led to an out-of-bounds-read that potentially could     be triggered by a malformed OpenType font. (CVE-2024-3859)

  - An out-of-memory condition during object initialization could result in an empty shape list. If the JIT     subsequently traced the object it would crash. (CVE-2024-3860)

  - If an AlignedBuffer were assigned to itself, the subsequent self-move could result in an incorrect     reference count and later use-after-free. (CVE-2024-3861)

  - The MarkStack assignment operator, part of the JavaScript engine, could access uninitialized memory if it     were used in a self-assignment. (CVE-2024-3862)

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

  - There was no limit to the number of HTTP/2 CONTINUATION frames that would be processed. A server could     abuse this to create an Out of Memory condition in the browser. (CVE-2024-3302)

  - Memory safety bug present in Firefox 124, Firefox ESR 115.9, and Thunderbird 115.9. This bug showed     evidence of memory corruption and we presume that with enough effort this could have been exploited to run     arbitrary code. (CVE-2024-3864)

  - Memory safety bugs present in Firefox 124. 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-3865)

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
205525	GLSA-202408-02 : Mozilla Firefox: Multiple Vulnerabilities	Nessus	Gentoo Local Security Checks	critical
194573	Fedora 40 : firefox (2024-c6a1d4e0ec)	Nessus	Fedora Local Security Checks	critical
193788	Ubuntu 20.04 LTS : Firefox vulnerabilities (USN-6747-1)	Nessus	Ubuntu Local Security Checks	high
193669	Fedora 38 : firefox (2024-966e16bfa3)	Nessus	Fedora Local Security Checks	critical
193396	Fedora 39 : firefox (2024-121f5cec9f)	Nessus	Fedora Local Security Checks	critical
193366	Mozilla Firefox < 125.0	Nessus	Windows	critical
193365	Mozilla Firefox < 125.0	Nessus	MacOS X Local Security Checks	critical

Detections

Analytics

CVE-2024-3858

high

Tenable Plugins

critical

critical

high

critical

critical

critical

critical