In general, these flaws cannot be exploited through email in the Thunderbird product because scripting is disabled when reading mail, but are potentially risks in browser or browser-like contexts.
Under certain conditions, when running the nsDocShell destructor, a race condition can cause a use-after-free.
Under certain conditions, when handling a ReadableStream, a race condition can cause a use-after-free.
When reading from areas partially or fully outside the source resource with WebGL's copyTexSubImage
method, the specification requires the returned values be zero. Previously, this memory was uninitialized, leading to potentially sensitive data disclosure.
On 32-bit builds, an out of bounds write could have occurred when processing an image larger than 4 GB in GMPDecodeData
. It is possible that with enough effort this could have been exploited to run arbitrary code.
Mozilla developers Tyson Smith and Christian Holler reported memory safety bugs present in Firefox 74 and Firefox ESR 68.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.