| CVE-2022-36319 |
When combining CSS properties for overflow and transform, the mouse cursor could interact with different coordinates…
|
7.5
Élevée
|
22 déc. 2022 |
| CVE-2022-36318 |
When visiting directory listings for `chrome://` URLs as source text, some parameters were reflected
|
5.3
Moyenne
|
22 déc. 2022 |
| CVE-2022-36314 |
When opening a Windows shortcut from the local filesystem, an attacker could supply a remote path that would lead to…
|
5.5
Moyenne
|
22 déc. 2022 |
| CVE-2022-34472 |
If there was a PAC URL set and the server that hosts the PAC was not reachable, OCSP requests would have been blocked,…
|
4.3
Moyenne
|
22 déc. 2022 |
| CVE-2022-34470 |
Session history navigations may have led to a use-after-free and potentially exploitable crash
|
9.8
Critique
|
22 déc. 2022 |
| CVE-2022-34481 |
In the nsTArray_Impl::ReplaceElementsAt() function, an integer overflow could have occurred when the number of…
|
8.8
Élevée
|
22 déc. 2022 |
| CVE-2022-34468 |
An iframe that was not permitted to run scripts could do so if the user clicked on a <code>javascript:</code> link
|
8.8
Élevée
|
22 déc. 2022 |
| CVE-2022-34479 |
A malicious website that could create a popup could have resized the popup to overlay the address bar with its own…
|
6.5
Moyenne
|
22 déc. 2022 |
| CVE-2022-34478 |
The ms-msdt, search, and search-ms protocols deliver content to Microsoft applications, bypassing the browser, when a…
|
6.5
Moyenne
|
22 déc. 2022 |
| CVE-2022-34484 |
The Mozilla Fuzzing Team reported potential vulnerabilities present in Thunderbird 91.10
|
8.8
Élevée
|
22 déc. 2022 |
| CVE-2022-31739 |
When downloading files on Windows, the % character was not escaped, which could have lead to a download incorrectly…
|
8.8
Élevée
|
22 déc. 2022 |
| CVE-2022-31738 |
When exiting fullscreen mode, an iframe could have confused the browser about the current state of fullscreen, resulting…
|
6.5
Moyenne
|
22 déc. 2022 |
| CVE-2022-31747 |
Mozilla developers Andrew McCreight, Nicolas B
|
9.8
Critique
|
22 déc. 2022 |
| CVE-2022-31737 |
A malicious webpage could have caused an out-of-bounds write in WebGL, leading to memory corruption and a potentially…
|
9.8
Critique
|
22 déc. 2022 |
| CVE-2022-31744 |
An attacker could have injected CSS into stylesheets accessible via internal URIs, such as resource:, and in doing so…
|
6.5
Moyenne
|
22 déc. 2022 |
| CVE-2022-31736 |
A malicious website could have learned the size of a cross-origin resource that supported Range requests
|
9.8
Critique
|
22 déc. 2022 |
| CVE-2022-31742 |
An attacker could have exploited a timing attack by sending a large number of allowCredential entries and detecting…
|
6.5
Moyenne
|
22 déc. 2022 |
| CVE-2022-31741 |
A crafted CMS message could have been processed incorrectly, leading to an invalid memory read, and potentially…
|
8.8
Élevée
|
22 déc. 2022 |
| CVE-2022-31740 |
On arm64, WASM code could have resulted in incorrect assembly generation leading to a register allocation problem, and a…
|
8.8
Élevée
|
22 déc. 2022 |
| CVE-2022-2505 |
Mozilla developers and the Mozilla Fuzzing Team reported memory safety bugs present in Firefox 102
|
8.8
Élevée
|
22 déc. 2022 |
| CVE-2022-2200 |
If an object prototype was corrupted by an attacker, they would have been able to set undesired attributes on a…
|
8.8
Élevée
|
22 déc. 2022 |
| CVE-2022-29917 |
Mozilla developers Andrew McCreight, Gabriele Svelto, Tom Ritter and the Mozilla Fuzzing Team reported memory safety…
|
9.8
Critique
|
22 déc. 2022 |
| CVE-2022-29916 |
Firefox behaved slightly differently for already known resources when loading CSS resources involving CSS variables
|
6.5
Moyenne
|
22 déc. 2022 |
| CVE-2022-29914 |
When reusing existing popups Firefox would have allowed them to cover the fullscreen notification UI, which could have…
|
6.5
Moyenne
|
22 déc. 2022 |
| CVE-2022-29912 |
Requests initiated through reader mode did not properly omit cookies with a SameSite attribute
|
6.1
Moyenne
|
22 déc. 2022 |