Out of bound write due to lazy initialization. A WebGL framebuffer was not
initialized early enough, resulting in memory corruption and an out of bound
Use-after-free in Responsive Design Mode. When Responsive Design Mode was
enabled, it used references to objects that were previously freed. We
presume that with enough effort this could have been exploited to run
Secure Lock icon could have been spoofed. Through complicated navigations
with new windows, an HTTP page could have inherited a secure lock icon from
an HTTPS page.
Blob URLs may have been granted additional privileges. 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.
Arbitrary FTP command execution on FTP servers using an encoded URL. 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.
Incorrect size computation in WebAssembly JIT could lead to null-reads. The
WebAssembly JIT could miscalculate the size of a return type, which could
lead to a null read and result in a crash.
Note: This issue only affected x86-32 platforms. Other platforms are
Port blocking could be bypassed. 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.
Dead tracker, closing.