This bug was fixed in the package mozjs128 - 128.3.0-1
---------------
mozjs128 (128.3.0-1) unstable; urgency=high
* New upstream release (LP: #2083344)
- CVE-2024-9396 Potential memory corruption when cloning certain objects
- CVE-2024-9400 Potential memory corruption during JIT compilation
- CVE-2024-9402 Memory safety bugs
* Remove libatomic patch applied in new release
* Revert "Add -latomic to LDFLAGS to try to fix armel build"
-- Jeremy Bícha <[email protected]> Tue, 01 Oct 2024 11:46:49 -0400
** Changed in: mozjs128 (Ubuntu)
Status: New => Fix Released
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2024-9396
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2024-9400
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2024-9402
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2083344
Title:
Update oracular to new mozjs releases
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mozjs115/+bug/2083344/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
