Vulnerabilities

A WebGL framebuffer was not initialized early enough, resulting in memory corruption and an out of bound write.

When Responsive Design Mode was enabled, it used references to objects that were previously freed.

By utilizing 3D CSS in conjunction with Javascript, content could have been rendered outside the webpage's viewport, resulting in a spoofing attack that could have been used for phishing or other attacks on a user.

Due to unexpected data type conversions, a use-after-free could have occurred when interacting with the font cache.

Through complicated navigations with new windows, an HTTP page could have inherited a secure lock icon from an HTTPS page.

If a Blob URL was loaded through some unusual user interaction, it could have been loaded by the System Principal and granted additional privileges that should not be granted to web content.

A race condition with requestPointerLock() and setTimeout() could have resulted in a user interacting with one tab when they believed they were on a separate tab.

A compromised content process could have performed session history manipulations it should not have been able to due to testing infrastructure that was not restricted to testing-only configurations.

When a user clicked on an FTP URL containing encoded newline characters (%0A and %0D), the newlines would have been interpreted as such and allowed arbitrary commands to be sent to the FTP server.

Lack of escaping allowed HTML injection when a webpage was viewed in Reader View.

The WebAssembly JIT could miscalculate the size of a return type, which could lead to a null read and result in a crash.

Ports that were written as an integer overflow above the bounds of a 16-bit integer could have bypassed port blocking restrictions when used in the Alt-Svc header.

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