Bugs fixes in "mozjs102"
| Origin | Bug number | Title | Date fixed |
|---|---|---|---|
| CVE | CVE-2022-40957 | Inconsistent data in instruction and data cache when creating wasm code could lead to a potentially exploitable crash.<br>*This bug only affects Fire | 2023-02-06 |
| Launchpad | 1993214 | [jammy] Update gjs to 1.74 using mozjs102 102.3 | 2023-02-06 |
| CVE | CVE-2022-45409 | The garbage collector could have been aborted in several states and zones and <code>GCRuntime::finishCollection</code> may not have been called, lead | 2023-01-14 |
| CVE | CVE-2022-45406 | If an out-of-memory condition occurred when creating a JavaScript global, a JavaScript realm may be deleted while references to it lived on in a Base | 2023-01-14 |
| CVE | CVE-2022-42932 | Mozilla developers Ashley Hale and the Mozilla Fuzzing Team reported memory safety bugs present in Thunderbird 102.3. Some of these bugs showed evide | 2023-01-14 |
| CVE | CVE-2022-42928 | Certain types of allocations were missing annotations that, if the Garbage Collector was in a specific state, could have lead to memory corruption an | 2023-01-14 |
| CVE | CVE-2022-40957 | Inconsistent data in instruction and data cache when creating wasm code could lead to a potentially exploitable crash.<br>*This bug only affects Fire | 2023-01-14 |
| Launchpad | 1993214 | [jammy] Update gjs to 1.74 using mozjs102 102.3 | 2023-01-14 |
About
-
Send Feedback to @ubuntu_updates
