Vulnerabilities

Memory safety bugs present in Firefox 127 and Thunderbird 127.

The frame iterator could get stuck in a loop when encountering certain wasm frames leading to incorrect stack traces.

The frame iterator could get stuck in a loop when encountering certain wasm frames leading to incorrect stack traces.

CSP violations generated links in the console tab of the developer tools, pointing to the violating resource.

A nested iframe, triggering a cross-site navigation, could send SameSite=Strict or Lax cookies.

Form validation popups could capture escape key presses.

When almost out-of-memory an elliptic curve key which was never allocated could have been freed again.

It was possible to move the cursor using pointerlock from an iframe.

It was possible to prevent a user from exiting pointerlock when pressing escape and to overlay customValidity notifications from a `<select>` element over certain permission prompts.

Clipboard code failed to check the index on an array access.

Memory safety bugs present in Firefox 127, Firefox ESR 115.12, and Thunderbird 115.12.

In an out-of-memory scenario an allocation could fail but free would have been called on the pointer afterwards leading to memory corruption.

A mismatch between allocator and deallocator could have led to memory corruption.

A race condition could lead to a cross-origin container obtaining permissions of the top-level origin.

Due to large allocation checks in Angle for GLSL shaders being too lenient an out-of-bounds access could occur when allocating more than 8192 ints in private shader memory on macOS.