| CVE-2024-8381 |
A potentially exploitable type confusion could be triggered when looking up a property name on an object being used as…
|
9.8
Critique
|
3 sept. 2024 |
| CVE-2024-7529 |
The date picker could partially obscure security prompts
|
8.1
Élevée
|
6 août 2024 |
| CVE-2024-7526 |
ANGLE failed to initialize parameters which lead to reading from uninitialized memory
|
7.5
Élevée
|
6 août 2024 |
| CVE-2024-7525 |
It was possible for a web extension with minimal permissions to create a `StreamFilter` which could be used to read…
|
9.1
Critique
|
6 août 2024 |
| CVE-2024-7528 |
Incorrect garbage collection interaction in IndexedDB could have led to a use-after-free
|
9.8
Critique
|
6 août 2024 |
| CVE-2024-7527 |
Unexpected marking work at the start of sweeping could have led to a use-after-free
|
8.8
Élevée
|
6 août 2024 |
| CVE-2024-7522 |
Editor code failed to check an attribute value
|
9.1
Critique
|
6 août 2024 |
| CVE-2024-7521 |
Incomplete WebAssembly exception handing could have led to a use-after-free
|
9.8
Critique
|
6 août 2024 |
| CVE-2024-7520 |
A type confusion bug in WebAssembly could be leveraged by an attacker to potentially achieve code execution
|
8.8
Élevée
|
6 août 2024 |
| CVE-2024-7519 |
Insufficient checks when processing graphics shared memory could have led to memory corruption
|
8.8
Élevée
|
6 août 2024 |
| CVE-2024-6602 |
A mismatch between allocator and deallocator could have led to memory corruption
|
9.8
Critique
|
9 juil. 2024 |
| CVE-2024-6603 |
In an out-of-memory scenario an allocation could fail but free would have been called on the pointer afterwards…
|
7.4
Élevée
|
9 juil. 2024 |
| CVE-2024-5700 |
Memory safety bugs present in Firefox 126, Firefox ESR 115.11, and Thunderbird 115.11
|
7.0
Élevée
|
11 juin 2024 |
| CVE-2024-5696 |
By manipulating the text in an `<input>` tag, an attacker could have caused corrupt memory leading to a…
|
8.6
Élevée
|
11 juin 2024 |
| CVE-2024-5693 |
Offscreen Canvas did not properly track cross-origin tainting, which could be used to access image data from another…
|
6.1
Moyenne
|
11 juin 2024 |
| CVE-2024-5688 |
If a garbage collection was triggered at the right time, a use-after-free could have occurred during object transplant
|
8.1
Élevée
|
11 juin 2024 |
| CVE-2024-5702 |
Memory corruption in the networking stack could have led to a potentially exploitable crash
|
7.5
Élevée
|
11 juin 2024 |
| CVE-2024-4770 |
When saving a page to PDF, certain font styles could have led to a potential use-after-free crash
|
8.8
Élevée
|
14 mai 2024 |
| CVE-2024-4769 |
When importing resources using Web Workers, error messages would distinguish the difference between…
|
5.9
Moyenne
|
14 mai 2024 |
| CVE-2024-4777 |
Memory safety bugs present in Firefox 125, Firefox ESR 115.10, and Thunderbird 115.10
|
7.5
Élevée
|
14 mai 2024 |
| CVE-2024-4367 |
A type check was missing when handling fonts in PDF.js, which would allow arbitrary JavaScript execution in the PDF.js…
|
5.6
Moyenne
|
14 mai 2024 |
| CVE-2024-3864 |
Memory safety bug present in Firefox 124, Firefox ESR 115.9, and Thunderbird 115.9
|
8.1
Élevée
|
16 avr. 2024 |
| CVE-2024-3859 |
On 32-bit versions there were integer-overflows that led to an out-of-bounds-read that potentially could be triggered by…
|
5.9
Moyenne
|
16 avr. 2024 |
| CVE-2024-3857 |
The JIT created incorrect code for arguments in certain cases
|
7.8
Élevée
|
16 avr. 2024 |
| CVE-2024-3854 |
In some code patterns the JIT incorrectly optimized switch statements and generated code with out-of-bounds-reads
|
8.8
Élevée
|
16 avr. 2024 |