[Medium] Upgrade ruby to 3.1.7 to fix CVE-2024-39908

[kevin-b-lockwood]

Merge Checklist

All boxes should be checked before merging the PR (just tick any boxes which don't apply to this PR)

• The toolchain has been rebuilt successfully (or no changes were made to it)
• The toolchain/worker package manifests are up-to-date
• Any updated packages successfully build (or no packages were changed)
• Packages depending on static components modified in this PR (Golang, *-static subpackages, etc.) have had their Release tag incremented.
• Package tests (%check section) have been verified with RUN_CHECK=y for existing SPEC files, or added to new SPEC files
• All package sources are available
• cgmanifest files are up-to-date and sorted (./cgmanifest.json, ./toolkit/scripts/toolchain/cgmanifest.json, .github/workflows/cgmanifest.json)
• LICENSE-MAP files are up-to-date (./SPECS/LICENSES-AND-NOTICES/data/licenses.json, ./SPECS/LICENSES-AND-NOTICES/LICENSES-MAP.md, ./SPECS/LICENSES-AND-NOTICES/LICENSE-EXCEPTIONS.PHOTON)
• All source files have up-to-date hashes in the *.signatures.json files
• sudo make go-tidy-all and sudo make go-test-coverage pass
• Documentation has been updated to match any changes to the build system
• If you are adding/removing a .spec file that has multiple-versions supported, please add @microsoft/cbl-mariner-multi-package-reviewers team as reviewer (Eg. golang has 2 versions 1.18, 1.21+)
• Ready to merge

---

Summary

Upgrade ruby to 3.3.2 to fix CVE-2024-39908

Also delete obsolete or irrelevant patches

This is my first time upgrading ruby, please let me know if there's something
I messed up or missed.

Change Log

• Edit CVE-2023-36617 to remove redundant patch (partly fixed by upgrade)
• Remove patches that were obviated by the upgrade:
  • CVE-2024-27280
  • CVE-2024-27281
  • CVE-2024-27282
  • CVE-2024-35176
  • CVE-2024-41946
  • CVE-2024-49761
  • CVE-2025-27219
  • CVE-2025-27220
  • CVE-2025-27221

Does this affect the toolchain?

NO

Links to CVEs

• https://nvd.nist.gov/vuln/detail/CVE-2024-39908

Test Methodology

• Local build

[kgodara912]

At this stage of project, major version upgrade may cause stability issues. It is better to check once the minor version release notes corresponding to ruby-3.1.7 and see if that is good enough to fix the CVE.

[kevin-b-lockwood]

At this stage of project, major version upgrade may cause stability issues. It is better to check once the minor version release notes corresponding to ruby-3.1.7 and see if that is good enough to fix the CVE.

I was going off of the triage notes:

which told me to upgrade to 3.3.2. I can look at 3.1.7 if that is preferred.

[Kanishk-Bansal]

This CVE affects REXML gem 3.3.1 or prior
v3.1.7 has REXML-3.3.4 which solves our purpose!

Nice finding @kgodara912

[kevin-b-lockwood]

Ok, I'll pivot and update to 3.1.7 instead.

[Kanishk-Bansal]

remove all #Patch in SPECS

[kgodara912]

Buddy build. Minor version upgrade for ruby. Please correct above PR description with proper CVE numbers and what patches removed correctly.

[kgodara912]

Minor version upgrade. The one, non-removed patch, is upgraded with following upstream references,

https://github.com/ruby/uri/commit/9010ee2536adda10a0555ae1ed6fe2f5808e6bf1
https://github.com/ruby/uri/commit/9d7bcef1e6ad23c9c6e4932f297fb737888144c8

Buddy build is fine. LGTM.

[kgodara912]

Please check the above versions specified, do they also need new numbers based on the new ruby version? For e.g. is zlib_version 2.1.1 still valid or it needs upgraded number, similarly for others as well.

[kevin-b-lockwood]

I believe these are correct, I ran the get_gem_versions.sh script and didn't see a change, but I can run it again and double check if you wish.

[kgodara912]

LGTM as developer verified that bundled versions are correct.