| CVE-2022-45420 |
Use tables inside of an iframe, an attacker could have caused iframe contents to be rendered outside the boundaries of…
|
6.5
Medium
|
Dec 22, 2022 |
| CVE-2022-45409 |
The garbage collector could have been aborted in several states and zones and GCRuntime::finishCollection may not have…
|
8.8
High
|
Dec 22, 2022 |
| CVE-2022-45419 |
If the user added a security exception for an invalid TLS certificate, opened an ongoing TLS connection with a server…
|
6.5
Medium
|
Dec 22, 2022 |
| CVE-2022-45408 |
Through a series of popups that reuse windowName, an attacker can cause a window to go fullscreen without the user…
|
6.5
Medium
|
Dec 22, 2022 |
| CVE-2022-45407 |
If an attacker loaded a font using FontFace() on a background worker, a use-after-free could have occurred, leading to a…
|
7.5
High
|
Dec 22, 2022 |
| CVE-2022-45418 |
If a custom mouse cursor is specified in CSS, under certain circumstances the cursor could have been drawn over the…
|
6.1
Medium
|
Dec 22, 2022 |
| CVE-2022-45417 |
Service Workers did not detect Private Browsing Mode correctly in all cases, which could have led to Service Workers…
|
4.3
Medium
|
Dec 22, 2022 |
| CVE-2022-45406 |
If an out-of-memory condition occurred when creating a JavaScript global, a JavaScript realm may be deleted while…
|
9.8
Critical
|
Dec 22, 2022 |
| CVE-2022-45405 |
Freeing arbitrary nsIInputStream's on a different thread than creation could have led to a use-after-free and…
|
6.5
Medium
|
Dec 22, 2022 |
| CVE-2022-45416 |
Keyboard events reference strings like "KeyA" that were at fixed, known, and widely-spread addresses
|
6.5
Medium
|
Dec 22, 2022 |
| CVE-2022-45415 |
When downloading an HTML file, if the title of the page was formatted as a filename with a malicious extension,…
|
7.8
High
|
Dec 22, 2022 |
| CVE-2022-45404 |
Through a series of popup and window.print() calls, an attacker can cause a window to go fullscreen without the user…
|
6.5
Medium
|
Dec 22, 2022 |
| CVE-2022-45413 |
Using the S.browser_fallback_url parameter parameter, an attacker could redirect a user to a URL and cause…
|
6.1
Medium
|
Dec 22, 2022 |
| CVE-2022-45403 |
Service Workers should not be able to infer information about opaque cross-origin responses; but timing information…
|
6.5
Medium
|
Dec 22, 2022 |
| CVE-2022-42927 |
A same-origin policy violation could have allowed the theft of cross-origin URL entries, leaking the result of a…
|
8.1
High
|
Dec 22, 2022 |
| CVE-2022-42932 |
Mozilla developers Ashley Hale and the Mozilla Fuzzing Team reported memory safety bugs present in Firefox 105 and…
|
8.8
High
|
Dec 22, 2022 |
| CVE-2022-42931 |
Logins saved by Firefox should be managed by the Password Manager component which uses encryption to save files on-disk
|
3.3
Low
|
Dec 22, 2022 |
| CVE-2022-42930 |
If two Workers were simultaneously initializing their CacheStorage, a data race could have occurred in the…
|
7.1
High
|
Dec 22, 2022 |
| CVE-2022-42929 |
If a website called `window.print()` in a particular way, it could cause a denial of service of the browser, which may…
|
6.5
Medium
|
Dec 22, 2022 |
| CVE-2022-42928 |
Certain types of allocations were missing annotations that, if the Garbage Collector was in a specific state, could have…
|
8.8
High
|
Dec 22, 2022 |
| CVE-2022-40962 |
Mozilla developers Nika Layzell, Timothy Nikkel, Sebastian Hengst, Andreas Pehrson, and the Mozilla Fuzzing Team…
|
8.8
High
|
Dec 22, 2022 |
| CVE-2022-40961 |
During startup, a graphics driver with an unexpected name could lead to a stack-buffer overflow causing a potentially…
|
6.5
Medium
|
Dec 22, 2022 |
| CVE-2022-40960 |
Concurrent use of the URL parser with non-UTF-8 data was not thread-safe
|
6.5
Medium
|
Dec 22, 2022 |
| CVE-2022-40959 |
During iframe navigation, certain pages did not have their FeaturePolicy fully initialized leading to a bypass that…
|
6.5
Medium
|
Dec 22, 2022 |
| CVE-2022-40958 |
By injecting a cookie with certain special characters, an attacker on a shared subdomain which is not a secure context…
|
6.5
Medium
|
Dec 22, 2022 |