Update mozjs102 to 102.11.0

Bug #2018905 reported by Jeremy Bícha
258
This bug affects 1 person
Affects Status Importance Assigned to Milestone
mozjs102 (Ubuntu)
Fix Released
Undecided
Unassigned
Jammy
Fix Released
Undecided
Unassigned
Kinetic
Fix Released
Undecided
Unassigned
Lunar
Fix Released
Undecided
Unassigned

Bug Description

Impact
------
mozjs102 is the SpiderMonkey JavaScript engine from Firefox ESR. It is used by gjs to power GNOME Shell and some GNOME apps.

There are new Firefox 102 ESR releases monthly until the end of August.
https://whattrainisitnow.com/calendar/

This bug tracks updating Ubuntu 23.04 from 102.10.0 to 102.11.0,
Ubuntu 22.10 from 102.3.0 to 102.11.0,
and backporting this package to Ubuntu 22.04 LTS.

Security Impact
---------------
I looked through
https://github.com/mozilla/gecko-dev/commits/esr102/js
and searched for referenced bug numbers in
https://www.mozilla.org/en-US/security/advisories/mfsa2023-17/

and found two CVEs for Ubuntu 23.04

Ubuntu 22.10 wasn't updated recently, so I listed 7 more CVEs there from previous Mozilla Advisories.
Also, note that there are 4 more CVEs from 102.6.0-0ubuntu0.22.10.1 which was only pushed to -proposed and not to -security. (We ran into an issue with updating gjs for Ubuntu 22.04 LTS but that doesn't need to block updating mozjs102 by itself.)

Test Case
---------
https://wiki.ubuntu.com/DesktopTeam/TestPlans/gjs

Security Sponsoring
-------------------
sudo apt install git-buildpackage

mkdir ../tarballs; cd ../tarballs
pull-lp-source mozjs102 mantic
# That avoids needing to recreate the original tarball from pristine-tar which takes a while. Also, running lintian takes a while.
cd ..
gbp clone https://salsa.debian.org/gnome-team/mozjs
cd mozjs
git checkout ubuntu/102/lunar
gbp buildpackage --git-builder="debuild --no-lintian -S -nc" --git-tarball-dir=../tarballs

git checkout ubuntu/102/kinetic
gbp buildpackage --git-builder="debuild --no-lintian -S -nc -v102.3.0-1" --git-tarball-dir=../tarballs

git checkout ubuntu/102/jammy
gbp buildpackage --git-builder="debuild --no-lintian -S -nc" --git-tarball-dir=../tarballs

Initial Testing Done
--------------------
I built the package locally.
I installed the library package on Ubuntu 23.04 and successfully completed the Test Case.

Other Info
----------
I think it would be helpful to also push this update to Ubuntu 22.04 LTS even though we don't have any packages there using mozjs102 yet, since it is still a goal to update gjs there to use mozjs102. See LP: #1993214

It needs to go into `main` for Ubuntu 22.04 LTS but I think this will happen automatically since there is already a version in jammy-proposed in main.

Jeremy Bícha (jbicha)
Changed in mozjs102 (Ubuntu):
status: New → Incomplete
Jeremy Bícha (jbicha)
description: updated
Changed in mozjs102 (Ubuntu):
importance: Wishlist → Undecided
Changed in mozjs102 (Ubuntu Jammy):
status: New → Incomplete
Changed in mozjs102 (Ubuntu Kinetic):
status: New → Incomplete
Changed in mozjs102 (Ubuntu Lunar):
status: New → Incomplete
Jeremy Bícha (jbicha)
description: updated
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package mozjs102 - 102.11.0-1

---------------
mozjs102 (102.11.0-1) unstable; urgency=high

  * New upstream release (LP: #2018905)
    - CVE-2023-32205: Browser prompts could have been obscured by popups
    - CVE-2023-32206: Crash in RLBox Expat driver
    - CVE-2023-32207: Potential permissions request bypass via clickjacking
    - CVE-2023-32211: Content process crash due to invalid wasm code
    - CVE-2023-32212: Potential spoof due to obscured address bar
    - CVE-2023-32213: Potential memory corruption in FileReader::DoReadData()
    - CVE-2023-32214: Potential DoS via exposed protocol handlers
    - CVE-2023-32215: Memory safety bugs

 -- Jeremy Bícha <email address hidden> Mon, 08 May 2023 11:59:12 -0400

Changed in mozjs102 (Ubuntu):
status: Incomplete → Fix Released
Jeremy Bícha (jbicha)
description: updated
description: updated
Changed in mozjs102 (Ubuntu Jammy):
status: Incomplete → Confirmed
Changed in mozjs102 (Ubuntu Kinetic):
status: Incomplete → Confirmed
Changed in mozjs102 (Ubuntu Lunar):
status: Incomplete → Confirmed
information type: Public → Public Security
description: updated
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package mozjs102 - 102.11.0-0ubuntu0.23.04.1

---------------
mozjs102 (102.11.0-0ubuntu0.23.04.1) lunar-security; urgency=high

  * SECURITY UPDATE: New upstream release (LP: #2018905)
    - CVE-2023-32211: Content process crash due to invalid wasm code
    - CVE-2023-32215: Memory safety bugs

 -- Jeremy Bícha <email address hidden> Tue, 09 May 2023 11:30:19 -0400

Changed in mozjs102 (Ubuntu Lunar):
status: Confirmed → Fix Released
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package mozjs102 - 102.11.0-0ubuntu0.22.04.1

---------------
mozjs102 (102.11.0-0ubuntu0.22.04.1) jammy-security; urgency=medium

  * SECURITY UPDATE: Backport to Ubuntu 22.04 LTS (LP: #2018905)
    - CVE-2023-32211: Content process crash due to invalid wasm code
    - CVE-2023-32215: Memory safety bugs
    - CVE-2023-29536: Invalid free from JavaScript code
    - CVE-2023-29548: Incorrect optimization result on ARM64
    - CVE-2023-29550: Memory safety bugs
    - CVE-2023-29535: Potential Memory Corruption following Garbage Collector
      compaction
    - CVE-2023-25751: Incorrect code generation during JIT compilation
    - CVE-2023-25739: Use-after-free in mozilla::dom::ScriptLoadContext
    - CVE-2023-25735: Potential use-after-free from compartment mismatch

 -- Jeremy Bícha <email address hidden> Tue, 09 May 2023 11:30:19 -0400

Changed in mozjs102 (Ubuntu Jammy):
status: Confirmed → Fix Released
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package mozjs102 - 102.11.0-0ubuntu0.22.10.1

---------------
mozjs102 (102.11.0-0ubuntu0.22.10.1) kinetic-security; urgency=medium

  * SECURITY UPDATE: New upstream release (LP: #2018905)
    - CVE-2023-32211: Content process crash due to invalid wasm code
    - CVE-2023-32215: Memory safety bugs
    - CVE-2023-29536: Invalid free from JavaScript code
    - CVE-2023-29548: Incorrect optimization result on ARM64
    - CVE-2023-29550: Memory safety bugs
    - CVE-2023-29535: Potential Memory Corruption following Garbage Collector
      compaction
    - CVE-2023-25751: Incorrect code generation during JIT compilation
    - CVE-2023-25739: Use-after-free in mozilla::dom::ScriptLoadContext
    - CVE-2023-25735: Potential use-after-free from compartment mismatch

 -- Jeremy Bícha <email address hidden> Tue, 09 May 2023 11:30:19 -0400

Changed in mozjs102 (Ubuntu Kinetic):
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public Security information  
Everyone can see this security related information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.