Bug 1794064 Comment 18 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

This crash was a double-free memory corruption in the main process. It was possible to trigger it from sandboxed processes. Assuming exploitability, it could have let an attacker escape the sandbox. Avast has listed it under [https://nvd.nist.gov/vuln/detail/CVE-2022-4291](﷒0﷓) and Norton has published [two security advisories](https://support.norton.com/sp/static/external/tools/security-advisories.html): one listed as CVE-2022-4291, focused on the security vulnerability aspect, and one listed as NLOKSA1509, focused on the stability impact in Firefox.
This crash was a double-free memory corruption in the main process. It was possible to trigger it from sandboxed processes. Assuming exploitability, it could have let an attacker escape the sandbox. Avast has listed it under [CVE-2022-4291](https://nvd.nist.gov/vuln/detail/CVE-2022-4291) and Norton has published [two security advisories](https://support.norton.com/sp/static/external/tools/security-advisories.html): one listed as CVE-2022-4291, focused on the security vulnerability aspect, and one listed as NLOKSA1509, focused on the stability impact in Firefox.

Back to Bug 1794064 Comment 18