CVSS3
Attack Vector
NETWORK
Attack Complexity
LOW
Privileges Required
NONE
User Interaction
NONE
Scope
UNCHANGED
Confidentiality Impact
HIGH
Integrity Impact
HIGH
Availability Impact
HIGH
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS
Percentile
70.3%
In multiple cases browser prompts could have been obscured by popups controlled by content. These could have led to potential user confusion and spoofing attacks.
An out-of-bound read could have led to a crash in the RLBox Expat driver.
A missing delay in popup notifications could have made it possible for an attacker to trick a user into granting permissions.
Service workers could reveal script base URL due to dynamic import().
A maliciously crafted favicon could have led to an out of memory crash.
Documents were incorrectly assuming an ordering of principal objects when ensuring we were loading an appropriately privileged principal. In certain circumstances it might have been possible to cause a document to be loaded with a higher privileged principal than intended.
A type checking bug would have led to invalid code being compiled.
An attacker could have positioned a datalist element to obscure the address bar.
When reading a file, an uninitialized value could have been used as read limit.
A race condition during dav1d decoding could have led to an out-of-bounds memory access, potentially leading to memory corruption and execution of malicious code.
Protocol handlers ms-cxh and ms-cxh-full could have been leveraged to trigger a denial of service.Note: This attack only affects Windows. Other operating systems are not affected.
Mozilla developers and community members Gabriele Svelto, Andrew Osmond, Emily McDonough, Sebastian Hengst, Andrew McCreight and the Mozilla Fuzzing Team reported memory safety bugs present in Firefox 112 and Firefox ESR 102.10. 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.
Mozilla developers and community members Ronald Crane, Andrew McCreight, Randell Jesup and the Mozilla Fuzzing Team reported memory safety bugs present in Firefox 112. 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.
bugzilla.mozilla.org/buglist.cgi?bug_id=1540883%2C1751943%2C1814856%2C1820210%2C1821480%2C1827019%2C1827024%2C1827144%2C1827359%2C1830186
bugzilla.mozilla.org/buglist.cgi?bug_id=1746479%2C1806852%2C1815987%2C1820359%2C1823568%2C1824803%2C1824834%2C1825170%2C1827020%2C1828130
bugzilla.mozilla.org/show_bug.cgi?id=1646034
bugzilla.mozilla.org/show_bug.cgi?id=1753339
bugzilla.mozilla.org/show_bug.cgi?id=1753341
bugzilla.mozilla.org/show_bug.cgi?id=1767194
bugzilla.mozilla.org/show_bug.cgi?id=1776755
bugzilla.mozilla.org/show_bug.cgi?id=1814560
bugzilla.mozilla.org/show_bug.cgi?id=1814790
bugzilla.mozilla.org/show_bug.cgi?id=1819796
bugzilla.mozilla.org/show_bug.cgi?id=1823379
bugzilla.mozilla.org/show_bug.cgi?id=1824892
bugzilla.mozilla.org/show_bug.cgi?id=1826116
bugzilla.mozilla.org/show_bug.cgi?id=1826622
bugzilla.mozilla.org/show_bug.cgi?id=1826666
bugzilla.mozilla.org/show_bug.cgi?id=1828716