Vulnerabilities

NSS has shown timing differences when performing DSA signatures, which was exploitable and could eventually leak private keys.

Mozilla developers reported memory safety bugs present in Firefox 76 and Firefox ESR 68.8.

When browsing a malicious page, a race condition in our SharedWorkerService could occur and lead to a potentially exploitable crash.

Mozilla Developer Iain Ireland discovered a missing type check during unboxed objects removal, resulting in a crash.

When performing add-on updates, certificate chains terminating in non-built-in-roots were rejected (even if they were legitimately added by an administrator.) This could have caused add-ons to become out-of-date silently…

When trying to connect to a STUN server, a race condition could have caused a use-after-free of a pointer, leading to memory corruption and a potentially exploitable crash.

When processing callbacks that occurred during window flushing in the parent process, the associated window may die; causing a use-after-free condition.

Due to confusion about ValueTags on JavaScript Objects, an object may pass through the type barrier, resulting in memory corruption and a potentially exploitable crash.

Manipulating individual parts of a URL object could have caused an out-of-bounds read, leaking process memory to malicious JavaScript.