| CVE-2025-1935 |
A web page could trick a user into setting that site as the default handler for a custom URL protocol
|
4.3
Moyenne
|
4 mars 2025 |
| CVE-2025-1934 |
It was possible to interrupt the processing of a RegExp bailout and run additional JavaScript, potentially triggering…
|
6.5
Moyenne
|
4 mars 2025 |
| CVE-2025-1932 |
An inconsistent comparator in xslt/txNodeSorter could have resulted in potentially exploitable out-of-bounds access
|
8.1
Élevée
|
4 mars 2025 |
| CVE-2025-1931 |
It was possible to cause a use-after-free in the content process side of a WebTransport connection, leading to a…
|
7.5
Élevée
|
4 mars 2025 |
| CVE-2025-1933 |
On 64-bit CPUs, when the JIT compiles WASM i32 return values they can pick up bits from left over memory
|
7.6
Élevée
|
4 mars 2025 |
| CVE-2025-1930 |
On Windows, a compromised content process could use bad StreamData sent over AudioIPC to trigger a use-after-free in the…
|
8.8
Élevée
|
4 mars 2025 |
| CVE-2025-1017 |
Memory safety bugs present in Firefox 134, Thunderbird 134, Firefox ESR 128.6, and Thunderbird 128.6
|
9.8
Critique
|
4 févr. 2025 |
| CVE-2025-1016 |
Memory safety bugs present in Firefox 134, Thunderbird 134, Firefox ESR 115.19, Firefox ESR 128.6, Thunderbird 115.19,…
|
9.8
Critique
|
4 févr. 2025 |
| CVE-2025-1014 |
Certificate length was not properly checked when added to a certificate store
|
8.8
Élevée
|
4 févr. 2025 |
| CVE-2025-1013 |
A race condition could have led to private browsing tabs being opened in normal browsing windows
|
6.5
Moyenne
|
4 févr. 2025 |
| CVE-2025-1012 |
A race during concurrent delazification could have led to a use-after-free
|
9.8
Critique
|
4 févr. 2025 |
| CVE-2025-1011 |
A bug in WebAssembly code generation could have lead to a crash
|
9.8
Critique
|
4 févr. 2025 |
| CVE-2025-1010 |
An attacker could have caused a use-after-free via the Custom Highlight API, leading to a potentially exploitable crash
|
9.8
Critique
|
4 févr. 2025 |
| CVE-2025-1009 |
An attacker could have caused a use-after-free via crafted XSLT data, leading to a potentially exploitable crash
|
9.8
Critique
|
4 févr. 2025 |
| CVE-2025-0242 |
Memory safety bugs present in Firefox 133, Thunderbird 133, Firefox ESR 115.18, Firefox ESR 128.5, Thunderbird 115.18,…
|
6.5
Moyenne
|
7 janv. 2025 |
| CVE-2025-0243 |
Memory safety bugs present in Firefox 133, Thunderbird 133, Firefox ESR 128.5, and Thunderbird 128.5
|
5.1
Moyenne
|
7 janv. 2025 |
| CVE-2025-0241 |
When segmenting specially crafted text, segmentation would corrupt memory leading to a potentially exploitable crash
|
7.7
Élevée
|
7 janv. 2025 |
| CVE-2025-0240 |
Parsing a JavaScript module as JSON could, under some circumstances, cause cross-compartment access, which may result in…
|
4.0
Moyenne
|
7 janv. 2025 |
| CVE-2025-0239 |
When using Alt-Svc, ALPN did not properly validate certificates when the original server is redirecting to an insecure…
|
4.0
Moyenne
|
7 janv. 2025 |
| CVE-2025-0238 |
Assuming a controlled failed memory allocation, an attacker could have caused a use-after-free, leading to a potentially…
|
5.3
Moyenne
|
7 janv. 2025 |
| CVE-2025-0237 |
The WebChannel API, which is used to transport various information across processes, did not check the sending principal…
|
5.4
Moyenne
|
7 janv. 2025 |
| CVE-2024-11699 |
Memory safety bugs present in Firefox 132, Firefox ESR 128.4, and Thunderbird 128.4
|
8.8
Élevée
|
26 nov. 2024 |
| CVE-2024-11698 |
A flaw in handling fullscreen transitions may have inadvertently caused the application to become stuck in fullscreen…
|
9.8
Critique
|
26 nov. 2024 |
| CVE-2024-11696 |
The application failed to account for exceptions thrown by the `loadManifestFromFile` method during add-on signature…
|
5.4
Moyenne
|
26 nov. 2024 |
| CVE-2024-11704 |
A double-free issue could have occurred in `sec_pkcs7_decoder_start_decrypt()` when handling an error path
|
9.8
Critique
|
26 nov. 2024 |