Mozilla Firefox 127 : Memory safety bugs present in Firefox 126. 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.
Mozilla Firefox 127, Mozilla Firefox ESR 115.12 : Memory safety bugs present in Firefox 126, Firefox ESR 115.11. 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.
Mozilla Firefox 127 : In violation of spec, cookie prefixes such as __Secure were being ignored if they were not correctly capitalized - by spec they should be checked with a case-insensitive comparison. This could have resulted in the browser not correctly honoring the behaviors specified by the prefix.
Mozilla Firefox 127 : By manipulating the fullscreen feature while opening a data-list, an attacker could have overlaid a text box over the address bar. This could have led to user confusion and possible spoofing attacks.
Mozilla Firefox 127, Mozilla Firefox ESR 115.12 : By manipulating the text in an input tag, an attacker could have caused corrupt memory leading to a potentially exploitable crash.
Mozilla Firefox 127 : If an out-of-memory condition occurs at a specific point using allocations in the probabilistic heap checker, an assertion could have been triggered, and in rarer situations, memory corruption could have occurred.
Mozilla Firefox 127 : An attacker could have caused a use-after-free in the JavaScript engine to read memory in the JavaScript string section of the heap.
Mozilla Firefox 127, Mozilla Firefox ESR 115.12 : Offscreen Canvas did not properly track cross-origin tainting, which could be used to access image data from another site in violation of same-origin policy.
Mozilla Firefox 127, Mozilla Firefox ESR 115.12 : By tricking the browser with a X-Frame-Options header, a sandboxed iframe could have presented a button that, if clicked by a user, would bypass restrictions to open a new window.