Security Vulnerabilities fixed in Firefox 128 — Mozilla

An error in the ECMA-262 specification relating to Async Generators could have resulted in a type confusion, potentially leading to memory corruption and an exploitable crash.
Firefox Android allowed immediate interaction with permission prompts. This could be used for tapjacking.
Clipboard code failed to check the index on an array access. This could have lead to an out-of-bounds read.
It was possible to prevent a user from exiting pointerlock when pressing escape and to overlay customValidity notifications from a element over certain permission prompts. This could be used to confuse a user into giving a site unintended permissions.
It was possible to move the cursor using pointerlock from an iframe. This allowed moving the cursor outside of the viewport and the Firefox window.
When almost out-of-memory an elliptic curve key which was never allocated could have been freed again.
Form validation popups could capture escape key presses. Therefore, spamming form validation messages could be used to prevent users from exiting full-screen mode.
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 mac OS.
A race condition could lead to a cross-origin container obtaining permissions of the top-level origin.
A mismatch between allocator and deallocator could have lead to memory corruption.
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 nested iframe, triggering a cross-site navigation, could send SameSite=Strict or Lax cookies.
CSP violations generated links in the console tab of the developer tools, pointing to the violating resource. This caused a DNS prefetch which leaked that a CSP violation happened.
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.
Memory safety bugs present in Firefox 127, Firefox ESR 115.12, and Thunderbird 115.12. 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.
Memory safety bugs present in Firefox 127 and Thunderbird 127. 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.