An out of bounds write in ANGLE could have allowed an attacker to corrupt memory leading to a potentially exploitable 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.
A Linux user opening the print preview dialog could have caused the browser to crash.
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 phishing site could have repurposed an about: dialog to show phishing content with an incorrect origin in the address bar.
A bug in popup notifications delay calculation could have made it possible for an attacker to trick a user into granting permissions.
A malicious devtools extension could have been used to escalate privileges.
In specific HSTS configurations an attacker could have bypassed HSTS on a subdomain.
Memory safety bugs present in Firefox 121, Firefox ESR 115.6, and Thunderbird 115.6. 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.
Vulmon