| CVE-2021-43535 |
A use-after-free could have occured when an HTTP2 session object was released on a different thread, leading to memory…
|
Non notée
|
8 déc. 2021 |
| CVE-2021-43536 |
Under certain circumstances, asynchronous functions could have caused a navigation to fail but expose the target URL
|
Non notée
|
8 déc. 2021 |
| CVE-2021-43537 |
An incorrect type conversion of sizes from 64bit to 32bit integers allowed an attacker to corrupt memory leading to a…
|
Non notée
|
8 déc. 2021 |
| CVE-2021-43538 |
By misusing a race in our notification code, an attacker could have forcefully hidden the notification for pages that…
|
Non notée
|
8 déc. 2021 |
| CVE-2021-43539 |
Failure to correctly record the location of live pointers across wasm instance calls resulted in a GC occurring within…
|
Non notée
|
8 déc. 2021 |
| CVE-2021-43540 |
WebExtensions with the correct permissions were able to create and install ServiceWorkers for third-party websites…
|
Non notée
|
8 déc. 2021 |
| CVE-2021-43541 |
When invoking protocol handlers for external protocols, a supplied parameter URL containing spaces was not properly…
|
Non notée
|
8 déc. 2021 |
| CVE-2021-43542 |
Using XMLHttpRequest, an attacker could have identified installed applications by probing error messages for loading…
|
Non notée
|
8 déc. 2021 |
| CVE-2021-43543 |
Documents loaded with the CSP sandbox directive could have escaped the sandbox's script restriction by embedding…
|
Non notée
|
8 déc. 2021 |
| CVE-2021-43544 |
When receiving a URL through a SEND intent, Firefox would have searched for the text, but subsequent usages of the…
|
Non notée
|
8 déc. 2021 |
| CVE-2021-43545 |
Using the Location API in a loop could have caused severe application hangs and crashes
|
Non notée
|
8 déc. 2021 |
| CVE-2021-43546 |
It was possible to recreate previous cursor spoofing attacks against users with a zoomed native cursor
|
Non notée
|
8 déc. 2021 |
| CVE-2021-29991 |
Firefox incorrectly accepted a newline in a HTTP/3 header, interpretting it as two separate headers
|
Non notée
|
3 nov. 2021 |
| CVE-2021-29993 |
Firefox for Android allowed navigations through the `intent://` protocol, which could be used to cause crashes and UI…
|
Non notée
|
3 nov. 2021 |
| CVE-2021-38491 |
Mixed-content checks were unable to analyze opaque origins which led to some mixed content being loaded
|
Non notée
|
3 nov. 2021 |
| CVE-2021-38492 |
When delegating navigations to the operating system, Firefox would accept the `mk` scheme which might allow attackers to…
|
Non notée
|
3 nov. 2021 |
| CVE-2021-38493 |
Mozilla developers reported memory safety bugs present in Firefox 91 and Firefox ESR 78.13
|
Non notée
|
3 nov. 2021 |
| CVE-2021-38494 |
Mozilla developers reported memory safety bugs present in Firefox 91
|
Non notée
|
3 nov. 2021 |
| CVE-2021-38496 |
During operations on MessageTasks, a task may have been removed while it was still scheduled, resulting in memory…
|
Non notée
|
3 nov. 2021 |
| CVE-2021-38497 |
Through use of reportValidity() and window.open(), a plain-text validation message could have been overlaid on another…
|
Non notée
|
3 nov. 2021 |
| CVE-2021-38498 |
During process shutdown, a document could have caused a use-after-free of a languages service object, leading to…
|
Non notée
|
3 nov. 2021 |
| CVE-2021-38499 |
Mozilla developers reported memory safety bugs present in Firefox 92
|
Non notée
|
3 nov. 2021 |
| CVE-2021-38500 |
Mozilla developers reported memory safety bugs present in Firefox 92 and Firefox ESR 91.1
|
Non notée
|
3 nov. 2021 |
| CVE-2021-38501 |
Mozilla developers reported memory safety bugs present in Firefox 92 and Firefox ESR 91.1
|
Non notée
|
3 nov. 2021 |
| CVE-2021-29980 |
Uninitialized memory in a canvas object could have caused an incorrect free() leading to memory corruption and a…
|
Non notée
|
17 août 2021 |