The `fetch()` API and navigation incorrectly shared the same cache, as the cache key did not include the optional headers `fetch()` may contain. Under the correct circumstances, an attacker may have been able to poison the local browser cache by priming it with a `fetch()` response controlled by the additional headers. Upon navigation to the same URL, the user would see the cached response instead of the expected response. This vulnerability affects Firefox < 123.

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

  - When storing and re-accessing data on a networking channel, the length of buffers may have been confused,     resulting in an out-of-bounds memory read. This vulnerability affects Firefox < 123, Firefox ESR < 115.8,     and Thunderbird < 115.8. (CVE-2024-1546)

  - Through a series of API calls and redirects, an attacker-controlled alert dialog could have been displayed     on another website (with the victim website's URL shown). This vulnerability affects Firefox < 123,     Firefox ESR < 115.8, and Thunderbird < 115.8. (CVE-2024-1547)

  - A website could have obscured the fullscreen notification by using a dropdown select input element. This     could have led to user confusion and possible spoofing attacks. This vulnerability affects Firefox < 123,     Firefox ESR < 115.8, and Thunderbird < 115.8. (CVE-2024-1548)

  - If a website set a large custom cursor, portions of the cursor could have overlapped with the permission     dialog, potentially resulting in user confusion and unexpected granted permissions. This vulnerability     affects Firefox < 123, Firefox ESR < 115.8, and Thunderbird < 115.8. (CVE-2024-1549)

  - A malicious website could have used a combination of exiting fullscreen mode and `requestPointerLock` to     cause the user's mouse to be re-positioned unexpectedly, which could have led to user confusion and     inadvertently granting permissions they did not intend to grant. This vulnerability affects Firefox < 123,     Firefox ESR < 115.8, and Thunderbird < 115.8. (CVE-2024-1550)

  - Set-Cookie response headers were being incorrectly honored in multipart HTTP responses. If an attacker     could control the Content-Type response header, as well as control part of the response body, they could     inject Set-Cookie response headers that would have been honored by the browser. This vulnerability affects     Firefox < 123, Firefox ESR < 115.8, and Thunderbird < 115.8. (CVE-2024-1551)

  - Incorrect code generation could have led to unexpected numeric conversions and potential undefined     behavior.*Note:* This issue only affects 32-bit ARM devices. This vulnerability affects Firefox < 123,     Firefox ESR < 115.8, and Thunderbird < 115.8. (CVE-2024-1552)

  - Memory safety bugs present in Firefox 122, Firefox ESR 115.7, and Thunderbird 115.7. 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 < 123, Firefox ESR < 115.8, and     Thunderbird < 115.8. (CVE-2024-1553)

  - The `fetch()` API and navigation incorrectly shared the same cache, as the cache key did not include the     optional headers `fetch()` may contain. Under the correct circumstances, an attacker may have been able to     poison the local browser cache by priming it with a `fetch()` response controlled by the additional     headers. Upon navigation to the same URL, the user would see the cached response instead of the expected     response. This vulnerability affects Firefox < 123. (CVE-2024-1554)

  - When opening a website using the `firefox://` protocol handler, SameSite cookies were not properly     respected. This vulnerability affects Firefox < 123. (CVE-2024-1555)

  - The incorrect object was checked for NULL in the built-in profiler, potentially leading to invalid memory     access and undefined behavior. *Note:* This issue only affects the application when the profiler is     running. This vulnerability affects Firefox < 123. (CVE-2024-1556)

  - Memory safety bugs present in Firefox 122. 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 < 123. (CVE-2024-1557)

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

    - New upstream release (123.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 Ubuntu 20.04 LTS host has packages installed that are affected by multiple vulnerabilities as referenced in the USN-6649-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-1547, CVE-2024-1548,     CVE-2024-1549, CVE-2024-1550, CVE-2024-1553, CVE-2024-1554, CVE-2024-1555, CVE-2024-1557)

    Alfred Peters discovered that Firefox did not properly manage memory when storing and re-accessing data on     a networking channel. An attacker could potentially exploit this issue to cause a denial of service.
    (CVE-2024-1546)

    Johan Carlsson discovered that Firefox incorrectly handled Set-Cookie response headers in multipart HTTP     responses. An attacker could potentially exploit this issue to inject arbitrary cookie values.
    (CVE-2024-1551)

    Gary Kwong discovered that Firefox incorrectly generated codes on 32-bit ARM devices, which could lead to     unexpected numeric conversions or undefined behaviour. An attacker could possibly use this issue to cause     a denial of service. (CVE-2024-1552)

    Ronald Crane discovered that Firefox did not properly manage memory when accessing the built-in profiler.
    An attacker could potentially exploit this issue to cause a denial of service. (CVE-2024-1556)

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

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

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

  - When storing and re-accessing data on a networking channel, the length of buffers may have been confused,     resulting in an out-of-bounds memory read. (CVE-2024-1546)

  - Through a series of API calls and redirects, an attacker-controlled alert dialog could have been displayed     on another website (with the victim website's URL shown). (CVE-2024-1547)

  - The <code>fetch()</code> API and navigation incorrectly shared the same cache, as the cache key did not     include the optional headers <code>fetch()</code> may contain.  Under the correct circumstances, an     attacker may have been able to poison the local browser cache by priming it with a <code>fetch()</code>     response controlled by the additional headers. Upon navigation to the same URL, the user would see the     cached response instead of the expected response. (CVE-2024-1554)

  - A website could have obscured the fullscreen notification by using a dropdown select input element. This     could have led to user confusion and possible spoofing attacks. (CVE-2024-1548)

  - If a website set a large custom cursor, portions of the cursor could have overlapped with the permission     dialog, potentially resulting in user confusion and unexpected granted permissions. (CVE-2024-1549)

  - A malicious website could have used a combination of exiting fullscreen mode and     <code>requestPointerLock</code> to cause the user's mouse to be re-positioned unexpectedly, which could     have led to user confusion and inadvertently granting permissions they did not intend to grant.
    (CVE-2024-1550)

  - Set-Cookie response headers were being incorrectly honored in multipart HTTP responses. If an attacker     could control the Content-Type response header, as well as control part of the response body, they could     inject Set-Cookie response headers that would have been honored by the browser. (CVE-2024-1551)

  - When opening a website using the <code>firefox://</code> protocol handler, SameSite cookies were not     properly respected. (CVE-2024-1555)

  - The incorrect object was checked for NULL in the built-in profiler, potentially leading to invalid memory     access and undefined behavior. Note: This issue only affects the application when the profiler is running.
    (CVE-2024-1556)

  - Incorrect code generation could have led to unexpected numeric conversions and potential undefined     behavior. Note: This issue only affects 32-bit ARM devices. (CVE-2024-1552)

  - Memory safety bugs present in Firefox 122, Firefox ESR 115.7, and Thunderbird 115.7. 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-1553)

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

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

  - When storing and re-accessing data on a networking channel, the length of buffers may have been confused,     resulting in an out-of-bounds memory read. (CVE-2024-1546)

  - Through a series of API calls and redirects, an attacker-controlled alert dialog could have been displayed     on another website (with the victim website's URL shown). (CVE-2024-1547)

  - The <code>fetch()</code> API and navigation incorrectly shared the same cache, as the cache key did not     include the optional headers <code>fetch()</code> may contain.  Under the correct circumstances, an     attacker may have been able to poison the local browser cache by priming it with a <code>fetch()</code>     response controlled by the additional headers. Upon navigation to the same URL, the user would see the     cached response instead of the expected response. (CVE-2024-1554)

  - A website could have obscured the fullscreen notification by using a dropdown select input element. This     could have led to user confusion and possible spoofing attacks. (CVE-2024-1548)

  - If a website set a large custom cursor, portions of the cursor could have overlapped with the permission     dialog, potentially resulting in user confusion and unexpected granted permissions. (CVE-2024-1549)

  - A malicious website could have used a combination of exiting fullscreen mode and     <code>requestPointerLock</code> to cause the user's mouse to be re-positioned unexpectedly, which could     have led to user confusion and inadvertently granting permissions they did not intend to grant.
    (CVE-2024-1550)

  - Set-Cookie response headers were being incorrectly honored in multipart HTTP responses. If an attacker     could control the Content-Type response header, as well as control part of the response body, they could     inject Set-Cookie response headers that would have been honored by the browser. (CVE-2024-1551)

  - When opening a website using the <code>firefox://</code> protocol handler, SameSite cookies were not     properly respected. (CVE-2024-1555)

  - The incorrect object was checked for NULL in the built-in profiler, potentially leading to invalid memory     access and undefined behavior. Note: This issue only affects the application when the profiler is running.
    (CVE-2024-1556)

  - Incorrect code generation could have led to unexpected numeric conversions and potential undefined     behavior. Note: This issue only affects 32-bit ARM devices. (CVE-2024-1552)

  - Memory safety bugs present in Firefox 122, Firefox ESR 115.7, and Thunderbird 115.7. 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-1553)

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

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
194994	GLSA-202405-15 : Mozilla Firefox: Multiple Vulnerabilities	Nessus	Gentoo Local Security Checks	high
190912	Fedora 39 : firefox (2024-bc8ea2c2cb)	Nessus	Fedora Local Security Checks	high
190884	Ubuntu 20.04 LTS : Firefox vulnerabilities (USN-6649-1)	Nessus	Ubuntu Local Security Checks	high
190779	Mozilla Firefox < 123.0	Nessus	Windows	high
190778	Mozilla Firefox < 123.0	Nessus	MacOS X Local Security Checks	high

Detections

Analytics

CVE-2024-1554

critical

Tenable Plugins

high

high

high

high

high