Vulnerabilities

Uninitialized memory in a canvas object could have caused an incorrect free() leading to memory corruption and a potentially exploitable crash.

An issue present in lowering/register allocation could have led to obscure but deterministic register confusion failures in JITted code that would lead to a potentially exploitable crash.

Due to incorrect JIT optimization, we incorrectly interpreted data from the wrong type of object, resulting in the potential leak of a single bit of memory.

Firefox for Android could get stuck in fullscreen mode and not exit it even after normal interactions that should cause it to exit.

Instruction reordering resulted in a sequence of instructions that would cause an object to be incorrectly considered during garbage collection.

A use-after-free vulnerability in media channels could have led to memory corruption and a potentially exploitable crash.

A suspected race condition when calling getaddrinfo led to memory corruption and a potentially exploitable crash.

After requesting multiple permissions, and closing the first permission panel, subsequent permission panels will be displayed in a different position but still record a click in the default location, making it possible t…

Firefox incorrectly treated an inline list-item element as a block element, resulting in an out of bounds read or memory corruption, and a potentially exploitable crash.

Mozilla developers reported memory safety bugs present in Firefox 90 and Firefox ESR 78.12.

Mozilla developers and community members reported memory safety bugs present in Firefox 90.