| CVE-2024-2613 |
Data was not properly sanitized when decoding a QUIC ACK frame; this could have led to unrestricted memory consumption…
|
7.5
Élevée
|
19 mars 2024 |
| CVE-2024-2612 |
If an attacker could find a way to trigger a particular code path in `SafeRefPtr`, it could have triggered a crash or…
|
8.1
Élevée
|
19 mars 2024 |
| CVE-2024-2611 |
A missing delay on when pointer lock was used could have allowed a malicious page to trick a user into granting…
|
5.5
Moyenne
|
19 mars 2024 |
| CVE-2024-2610 |
Using a markup injection an attacker could have stolen nonce values
|
6.1
Moyenne
|
19 mars 2024 |
| CVE-2024-2609 |
The permission prompt input delay could expire while the window is not in focus
|
6.1
Moyenne
|
19 mars 2024 |
| CVE-2023-5388 |
NSS was susceptible to a timing side-channel attack when performing RSA decryption
|
6.5
Moyenne
|
19 mars 2024 |
| CVE-2024-2608 |
`AppendEncodedAttributeValue(), ExtraSpaceNeededForAttrEncoding()` and `AppendEncodedCharacters()` could have…
|
8.4
Élevée
|
19 mars 2024 |
| CVE-2024-2607 |
Return registers were overwritten which could have allowed an attacker to execute arbitrary code
|
8.1
Élevée
|
19 mars 2024 |
| CVE-2024-2606 |
Passing invalid data could have led to invalid wasm values being created, such as arbitrary integers turning into…
|
3.7
Faible
|
19 mars 2024 |
| CVE-2024-2605 |
An attacker could have leveraged the Windows Error Reporter to run arbitrary code on the system escaping the sandbox
|
5.9
Moyenne
|
19 mars 2024 |
| CVE-2024-26283 |
An attacker could have executed unauthorized scripts on top origin sites using a JavaScript URI when opening an external…
|
7.8
Élevée
|
22 févr. 2024 |
| CVE-2024-1557 |
Memory safety bugs present in Firefox 122
|
8.1
Élevée
|
20 févr. 2024 |
| CVE-2024-1556 |
The incorrect object was checked for NULL in the built-in profiler, potentially leading to invalid memory access and…
|
6.5
Moyenne
|
20 févr. 2024 |
| CVE-2024-1554 |
The `fetch()` API and navigation incorrectly shared the same cache, as the cache key did not include the optional…
|
9.8
Critique
|
20 févr. 2024 |
| CVE-2024-1553 |
Memory safety bugs present in Firefox 122, Firefox ESR 115.7, and Thunderbird 115.7
|
8.1
Élevée
|
20 févr. 2024 |
| CVE-2024-1555 |
When opening a website using the `firefox://` protocol handler, SameSite cookies were not properly respected
|
8.3
Élevée
|
20 févr. 2024 |
| CVE-2024-1552 |
Incorrect code generation could have led to unexpected numeric conversions and potential undefined behavior.*Note:* This…
|
7.5
Élevée
|
20 févr. 2024 |
| CVE-2024-1551 |
Set-Cookie response headers were being incorrectly honored in multipart HTTP responses
|
6.1
Moyenne
|
20 févr. 2024 |
| CVE-2024-1550 |
A malicious website could have used a combination of exiting fullscreen mode and `requestPointerLock` to cause the…
|
6.1
Moyenne
|
20 févr. 2024 |
| CVE-2024-1549 |
If a website set a large custom cursor, portions of the cursor could have overlapped with the permission dialog,…
|
6.1
Moyenne
|
20 févr. 2024 |
| CVE-2024-1548 |
A website could have obscured the fullscreen notification by using a dropdown select input element
|
4.3
Moyenne
|
20 févr. 2024 |
| CVE-2024-1547 |
Through a series of API calls and redirects, an attacker-controlled alert dialog could have been displayed on another…
|
6.5
Moyenne
|
20 févr. 2024 |
| CVE-2024-1546 |
When storing and re-accessing data on a networking channel, the length of buffers may have been confused, resulting in…
|
7.5
Élevée
|
20 févr. 2024 |
| CVE-2024-0752 |
A use-after-free crash could have occurred on macOS if a Firefox update were being applied on a very busy system
|
6.5
Moyenne
|
23 janv. 2024 |
| CVE-2024-0754 |
Some WASM source files could have caused a crash when loaded in devtools
|
6.5
Moyenne
|
23 janv. 2024 |