MGASA-2023-0146

Updated firefox and libwebp packages fix security vulnerabilities:

Unexpected data returned from the Safe Browsing API could have led to memory corruption and a potentially exploitable crash (CVE-2023-1945).

A website could have obscured the fullscreen notification by using a combination of window.open, fullscreen requests, window.name assignments, and setInterval calls. This could have led to user confusion and possible spoofing attacks (CVE-2023-29533).

Following a Garbage Collector compaction, weak maps may have been accessed before they were correctly traced. This resulted in memory corruption and a potentially exploitable crash (CVE-2023-29535).

An attacker could, via JavaScript code, cause the memory manager to incorrectly free a pointer that addresses attacker-controlled memory, resulting in an assertion, memory corruption, or a potentially exploitable crash (CVE-2023-29536).

When handling the filename directive in the Content-Disposition header, the filename would be truncated if the filename contained a NULL character. This could have led to reflected file download attacks potentially tricking users to install malware (CVE-2023-29539).

Firefox did not properly handle downloads of files ending in .desktop, which can be interpreted to run attacker-controlled commands (CVE-2023-29541).

Mozilla developers Andrew Osmond, Sebastian Hengst, Andrew McCreight, and the Mozilla Fuzzing Team reported memory safety bugs present in Firefox ESR 102.9. Some of these bugs showed evidence of memory corruption and we presume that with enough effort some of these could have been exploited to run arbitrary code (CVE-2023-29550).

A double-free in libwebp could have led to memory corruption and a potentially exploitable crash (MFSA-TMP-2023-0001).