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
46.8%
It was possible for certain browser prompts and dialogs to be activated or dismissed unintentionally by the user due to an insufficient activation-delay.
Using iterative requests an attacker was able to learn the size of an opaque response, as well as the contents of a server-supplied Vary header.
An attacker with temporary script access to a site could have set a cookie containing invalid characters using document.cookie that could have led to unknown errors.
Drivers are not always robust to extremely large draw calls and in some cases this scenario could have led to a crash.
A malicious installed WebExtension could open arbitrary URLs, which under the right circumstance could be leveraged to collect sensitive user data.
A website could have obscured the full screen notification by using the file open dialog. This could have led to user confusion and possible spoofing attacks. Note: This issue only affected macOS operating systems. Other operating systems are unaffected.
The executable file warning was not presented when downloading .msix, .msixbundle, .appx, and .appxbundle files, which can run commands on a user’s computer. Note: This issue only affected Windows operating systems. Other operating systems are unaffected.
During garbage collection extra operations were performed on a object that should not be. This could have led to a potentially exploitable crash.
A malicious web site can enter fullscreen mode while simultaneously triggering a WebAuthn prompt. This could have obscured the fullscreen notification and could have been leveraged in a spoofing attack.
Memory safety bugs present in Firefox 118, Firefox ESR 115.3, and Thunderbird 115.3. 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.
Memory safety bugs present in Firefox 118. 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=1690111%2C1721904%2C1851803%2C1854068
bugzilla.mozilla.org/buglist.cgi?bug_id=1836607%2C1840918%2C1848694%2C1848833%2C1850191%2C1850259%2C1852596%2C1853201%2C1854002%2C1855306%2C1855640%2C1856695
bugzilla.mozilla.org/show_bug.cgi?id=1738426
bugzilla.mozilla.org/show_bug.cgi?id=1802057
bugzilla.mozilla.org/show_bug.cgi?id=1823720
bugzilla.mozilla.org/show_bug.cgi?id=1830820
bugzilla.mozilla.org/show_bug.cgi?id=1836705
bugzilla.mozilla.org/show_bug.cgi?id=1845739
bugzilla.mozilla.org/show_bug.cgi?id=1846205
bugzilla.mozilla.org/show_bug.cgi?id=1847180
bugzilla.mozilla.org/show_bug.cgi?id=1852729