Vulnerabilities

Some WASM source files could have caused a crash when loaded in devtools.

A use-after-free crash could have occurred on macOS if a Firefox update were being applied on a very busy system.

A compromised content process could have updated the document URI.

The WebAudio `OscillatorNode` object was susceptible to a stack buffer overflow.

In some circumstances, JIT compiled code could have dereferenced a wild pointer value.

An unchecked return value in TLS handshake code could have caused a potentially exploitable crash.

Memory safety bugs present in Firefox 121, Firefox ESR 115.6, and Thunderbird 115.6.

In specific HSTS configurations an attacker could have bypassed HSTS on a subdomain.

A malicious devtools extension could have been used to escalate privileges.

A bug in popup notifications delay calculation could have made it possible for an attacker to trick a user into granting permissions.

A phishing site could have repurposed an `about:` dialog to show phishing content with an incorrect origin in the address bar.

When a parent page loaded a child in an iframe with `unsafe-inline`, the parent Content Security Policy could have overridden the child Content Security Policy.

A Linux user opening the print preview dialog could have caused the browser to crash.

It was possible for certain browser prompts and dialogs to be activated or dismissed unintentionally by the user due to an incorrect timestamp used to prevent input after page load.

An out of bounds write in ANGLE could have allowed an attacker to corrupt memory leading to a potentially exploitable crash.