NSSToken
objects were referenced via direct points, and could have been accessed in an unsafe way on different threads, leading to a use-after-free and potentially exploitable crash.
If a compromised content process sent an unexpected number of WebAuthN Extensions in a Register command to the parent process, an out of bounds write would have occurred leading to memory corruption and a potentially exploitable crash.
After a VR Process is destroyed, a reference to it may have been retained and used, leading to a use-after-free and potentially exploitable crash.
By using a link with rel="localization"
a use-after-free could have been triggered by destroying an object during JavaScript execution and then referencing the object through a freed pointer, leading to a potential exploitable crash.
When generating the assembly code for MLoadTypedArrayElementHole
, an incorrect AliasSet was used. In conjunction with another vulnerability this could have been used for an out of bounds memory read.
Due to a layout change, iframe contents could have been rendered outside of its border. This could have led to user confusion or spoofing attacks.
The rust regex crate did not properly prevent crafted regular expressions from taking an arbitrary amount of time during parsing. If an attacker was able to supply input to this crate, they could have caused a denial of service in the browser.
Mozilla developers and community members Nika Layzell (ni? for response), the Mozilla Fuzzing Team, Andrew McCreight, Gabriele Svelto (pto) reported memory safety bugs present in Firefox 98 and Firefox ESR 91.7. 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.