Skip to content

Conversation

@azurelinux-security
Copy link
Contributor

@azurelinux-security azurelinux-security commented Jan 5, 2026

Auto Patch ruby for CVE-2025-61594.

Autosec pipeline run -> https://dev.azure.com/mariner-org/mariner/_build/results?buildId=1018930&view=results

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 (./LICENSES-AND-NOTICES/SPECS/data/licenses.json, ./LICENSES-AND-NOTICES/SPECS/LICENSES-MAP.md, ./LICENSES-AND-NOTICES/SPECS/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
  • Ready to merge

Summary

What does the PR accomplish, why was it needed?

Change Log
Does this affect the toolchain?

YES/NO

Associated issues
  • N/A
Links to CVEs
Test Methodology

@microsoft-github-policy-service microsoft-github-policy-service bot added Packaging 3.0-dev PRs Destined for AzureLinux 3.0 labels Jan 5, 2026
@Kanishk-Bansal Kanishk-Bansal marked this pull request as ready for review January 5, 2026 13:14
@Kanishk-Bansal Kanishk-Bansal requested a review from a team as a code owner January 5, 2026 13:14
Copy link
Contributor

@suresh-thelkar suresh-thelkar left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The patch file CVE-2025-61594.patch only contains the first patch from the upstream fix, which is actually the patch for CVE-2025-27221 (not CVE-2025-61594).

What's Missing:

The upstream fix for CVE-2025-61594 consists of two patches:

Patch 1 (included):

  • Commit: d58589cae1b3c5fa2432b95fa28ed12793077935
  • Fixes CVE-2025-27221 (the original vulnerability)
  • Clears user info when setting authority info

Patch 2 (MISSING): ⚠️

  • Commit: Part of 7e521b2da0833d964aab43019e735aea674e1c2c
  • Actually fixes CVE-2025-61594 (the bypass vulnerability)
  • Adds the authority accessor method and modifies the merge method to use it
  • This is the critical part that prevents credential leakage when using the + operator to combine URIs

After fixing the above, also make sure that all the GitHub Checks passes.

@archana25-ms
Copy link
Contributor

The CVE-2025-61594.patch has been considered from ruby/uri@20157e3 as the uri version in azl 3.0 ruby-3.3.5 is 0.13.1.

@archana25-ms
Copy link
Contributor

Buddy Build link: https://dev.azure.com/mariner-org/mariner/_build/results?buildId=1023027&view=results

Buddy Build result is successful

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants