| CVE-2024-4769 |
When importing resources using Web Workers, error messages would distinguish the difference between…
|
5.9
Moyenne
|
14 mai 2024 |
| CVE-2024-4768 |
A bug in popup notifications' interaction with WebAuthn made it easier for an attacker to trick a user into granting…
|
6.1
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-4767 |
If the `browser.privatebrowsing.autostart` preference is enabled, IndexedDB files were not properly deleted when the…
|
4.3
Moyenne
|
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-3302 |
There was no limit to the number of HTTP/2 CONTINUATION frames that would be processed
|
3.7
Faible
|
16 avr. 2024 |
| CVE-2024-3865 |
Memory safety bugs present in Firefox 124
|
8.1
Élevée
|
16 avr. 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-3863 |
The executable file warning was not presented when downloading .xrm-ms files
|
9.8
Critique
|
16 avr. 2024 |
| CVE-2024-3862 |
The MarkStack assignment operator, part of the JavaScript engine, could access uninitialized memory if it were used in a…
|
5.3
Moyenne
|
16 avr. 2024 |
| CVE-2024-3861 |
If an AlignedBuffer were assigned to itself, the subsequent self-move could result in an incorrect reference count and…
|
4.0
Moyenne
|
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-3858 |
It was possible to mutate a JavaScript object so that the JIT could crash while tracing it
|
7.5
Élevée
|
16 avr. 2024 |
| CVE-2024-3860 |
An out-of-memory condition during object initialization could result in an empty shape list
|
6.2
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-3856 |
A use-after-free could occur during WASM execution if garbage collection ran during the creation of an array
|
8.8
Élevée
|
16 avr. 2024 |
| CVE-2024-3855 |
In certain cases the JIT incorrectly optimized MSubstr operations, which led to out-of-bounds reads
|
6.5
Moyenne
|
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 |
| CVE-2024-3853 |
A use-after-free could result if a JavaScript realm was in the process of being initialized when a garbage collection…
|
7.5
Élevée
|
16 avr. 2024 |
| CVE-2024-3852 |
GetBoundName could return the wrong version of an object when JIT optimizations were applied
|
7.5
Élevée
|
16 avr. 2024 |
| CVE-2024-31392 |
If an insecure element was added to a page after a delay, Firefox would not replace the secure icon with a mixed content…
|
7.5
Élevée
|
3 avr. 2024 |
| CVE-2024-29944 |
An attacker was able to inject an event handler into a privileged object that would allow arbitrary JavaScript execution…
|
8.4
Élevée
|
22 mars 2024 |
| CVE-2024-29943 |
An attacker was able to perform an out-of-bounds read or write on a JavaScript object by fooling range-based bounds…
|
9.8
Critique
|
22 mars 2024 |
| CVE-2024-2615 |
Memory safety bugs present in Firefox 123
|
9.8
Critique
|
19 mars 2024 |
| CVE-2024-2614 |
Memory safety bugs present in Firefox 123, Firefox ESR 115.8, and Thunderbird 115.8
|
8.8
Élevée
|
19 mars 2024 |