Mozilla

Multiple race conditions in the font initialization could have led to memory corruption and execution of attacker-controlled code.

A wrong lowering instruction in the ARM64 Ion compiler resulted in a wrong optimization result.

Following a Garbage Collector compaction, weak maps may have been accessed before they were correctly traced.

Under specific circumstances a WebExtension may have received a <code>jar:file:///</code> URI instead of a <code>moz-extension:///</code> URI during a load request.

A website could have obscured the fullscreen notification by using a combination of <code>window.open</code>, fullscreen requests, <code>window.name</code> assignments, and <code>setInterval</code> calls.

Memory safety bugs present in Firefox 111.

Memory safety bugs present in Firefox 111 and Firefox ESR 102.9.

When handling the filename directive in the Content-Disposition header, the filename would be truncated if the filename contained a NULL character.

An attacker could cause the memory manager to incorrectly free a pointer that addresses attacker-controlled memory, resulting in an assertion, memory corruption, or a potentially exploitable crash.

An attacker could have caused memory corruption and a potentially exploitable use-after-free of a pointer in a global object's debugger vector.

Firefox did not properly handle downloads of files ending in <code>.desktop</code>, which can be interpreted to run attacker-controlled commands.

UXSS in Focus for iOS / Klar Webkit navigation.

Under certain circumstances, a call to the <code>bind</code> function may have resulted in the incorrect realm.

When a secure cookie existed in the Firefox cookie jar an insecure cookie for the same domain could have been created, when it should have silently failed.

If multiple instances of resource exhaustion occurred at the incorrect time, the garbage collector could have caused memory corruption and a potentially exploitable crash.

Using a redirect embedded into <code>sourceMappingUrls</code> could allow for navigation to external protocol links in sandboxed iframes without <code>allow-top-navigation-to-custom-protocols</code>.