| 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-7518 |
Select options could obscure the fullscreen notification dialog
|
6.5
Moyenne
|
6 août 2024 |
| CVE-2024-6615 |
Memory safety bugs present in Firefox 127 and Thunderbird 127
|
8.8
Élevée
|
9 juil. 2024 |
| CVE-2024-6612 |
CSP violations generated links in the console tab of the developer tools, pointing to the violating resource
|
5.3
Moyenne
|
9 juil. 2024 |
| CVE-2024-6614 |
The frame iterator could get stuck in a loop when encountering certain wasm frames leading to incorrect stack traces
|
4.3
Moyenne
|
9 juil. 2024 |
| CVE-2024-6613 |
The frame iterator could get stuck in a loop when encountering certain wasm frames leading to incorrect stack traces
|
5.5
Moyenne
|
9 juil. 2024 |
| CVE-2024-6611 |
A nested iframe, triggering a cross-site navigation, could send SameSite=Strict or Lax cookies
|
9.8
Critique
|
9 juil. 2024 |
| CVE-2024-6610 |
Form validation popups could capture escape key presses
|
6.3
Moyenne
|
9 juil. 2024 |
| CVE-2024-6609 |
When almost out-of-memory an elliptic curve key which was never allocated could have been freed again
|
8.8
Élevée
|
9 juil. 2024 |
| CVE-2024-6608 |
It was possible to move the cursor using pointerlock from an iframe
|
4.3
Moyenne
|
9 juil. 2024 |
| CVE-2024-6607 |
It was possible to prevent a user from exiting pointerlock when pressing escape and to overlay customValidity…
|
8.8
Élevée
|
9 juil. 2024 |
| CVE-2024-6606 |
Clipboard code failed to check the index on an array access
|
8.2
Élevée
|
9 juil. 2024 |
| CVE-2024-6602 |
A mismatch between allocator and deallocator could have led to memory corruption
|
9.8
Critique
|
9 juil. 2024 |
| CVE-2024-6604 |
Memory safety bugs present in Firefox 127, Firefox ESR 115.12, and Thunderbird 115.12
|
7.5
Élevée
|
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-6601 |
A race condition could lead to a cross-origin container obtaining permissions of the top-level origin
|
4.7
Moyenne
|
9 juil. 2024 |
| CVE-2024-6600 |
Due to large allocation checks in Angle for GLSL shaders being too lenient an out-of-bounds access could occur when…
|
6.3
Moyenne
|
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-5691 |
By tricking the browser with a `X-Frame-Options` header, a sandboxed iframe could have presented a button that, if…
|
4.7
Moyenne
|
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-5692 |
On Windows 10, when using the 'Save As' functionality, an attacker could have tricked the browser into saving the file…
|
6.5
Moyenne
|
11 juin 2024 |
| CVE-2024-5690 |
By monitoring the time certain operations take, an attacker could have guessed which external protocol handlers were…
|
4.3
Moyenne
|
11 juin 2024 |