| 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-1936 |
The encrypted subject of an email message could be incorrectly and permanently assigned to an arbitrary other email…
|
7.5
Élevée
|
4 mars 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-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-0743 |
An unchecked return value in TLS handshake code could have caused a potentially exploitable crash
|
7.5
Élevée
|
23 janv. 2024 |
| CVE-2024-0753 |
In specific HSTS configurations an attacker could have bypassed HSTS on a subdomain
|
6.5
Moyenne
|
23 janv. 2024 |
| CVE-2024-0755 |
Memory safety bugs present in Firefox 121, Firefox ESR 115.6, and Thunderbird 115.6
|
8.8
Élevée
|
23 janv. 2024 |
| CVE-2024-0751 |
A malicious devtools extension could have been used to escalate privileges
|
8.8
Élevée
|
23 janv. 2024 |
| CVE-2024-0750 |
A bug in popup notifications delay calculation could have made it possible for an attacker to trick a user into granting…
|
8.8
Élevée
|
23 janv. 2024 |
| CVE-2024-0749 |
A phishing site could have repurposed an `about:` dialog to show phishing content with an incorrect origin in the…
|
4.3
Moyenne
|
23 janv. 2024 |
| CVE-2024-0747 |
When a parent page loaded a child in an iframe with `unsafe-inline`, the parent Content Security Policy could have…
|
6.5
Moyenne
|
23 janv. 2024 |
| CVE-2024-0746 |
A Linux user opening the print preview dialog could have caused the browser to crash
|
6.5
Moyenne
|
23 janv. 2024 |
| CVE-2024-0742 |
It was possible for certain browser prompts and dialogs to be activated or dismissed unintentionally by the user due…
|
4.3
Moyenne
|
23 janv. 2024 |
| CVE-2024-0741 |
An out of bounds write in ANGLE could have allowed an attacker to corrupt memory leading to a potentially exploitable…
|
6.5
Moyenne
|
23 janv. 2024 |
| CVE-2023-6864 |
Memory safety bugs present in Firefox 120, Firefox ESR 115.5, and Thunderbird 115.5
|
Non notée
|
19 déc. 2023 |
| CVE-2023-6863 |
The `ShutdownObserver()` was susceptible to potentially undefined behavior due to its reliance on a dynamic type that…
|
Non notée
|
19 déc. 2023 |
| CVE-2023-6862 |
A use-after-free was identified in the `nsDNSService::Init`
|
Non notée
|
19 déc. 2023 |
| CVE-2023-6861 |
The `nsWindow::PickerOpen(void)` method was susceptible to a heap buffer overflow when running in headless mode
|
Non notée
|
19 déc. 2023 |
| CVE-2023-6860 |
The `VideoBridge` allowed any content process to use textures produced by remote decoders
|
Non notée
|
19 déc. 2023 |