Vulnerabilities

Memory safety bugs present in Firefox 122.

The incorrect object was checked for NULL in the built-in profiler, potentially leading to invalid memory access and undefined behavior.

When opening a website using the `firefox://` protocol handler, SameSite cookies were not properly respected.

The `fetch()` API and navigation incorrectly shared the same cache, as the cache key did not include the optional headers `fetch()` may contain.

Memory safety bugs present in Firefox 122, Firefox ESR 115.7, and Thunderbird 115.7.

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

Set-Cookie response headers were being incorrectly honored in multipart HTTP responses.

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 g…

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.

A website could have obscured the fullscreen notification by using a dropdown select input element.

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

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.