Skip to content

[High] Patch libsoup for CVE-2025-4476, CVE-2025-32907 #13853

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Conversation

kevin-b-lockwood
Copy link
Contributor

@kevin-b-lockwood kevin-b-lockwood commented May 21, 2025

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

Patch libsoup for CVE-2025-4476, CVE-2025-32907

Change Log
Does this affect the toolchain?

NO

Links to CVEs
Test Methodology
  • Local build

@kevin-b-lockwood kevin-b-lockwood requested a review from a team as a code owner May 21, 2025 23:00
@microsoft-github-policy-service microsoft-github-policy-service bot added Packaging 3.0-dev PRs Destined for AzureLinux 3.0 labels May 21, 2025
@kevin-b-lockwood kevin-b-lockwood force-pushed the kevin-b-lockwood/libsoup-3.0-CVE branch from a786fb7 to b74461a Compare June 3, 2025 23:23
@kevin-b-lockwood kevin-b-lockwood requested a review from mfrw June 4, 2025 23:50
@kevin-b-lockwood kevin-b-lockwood changed the title [Medium] Patch libsoup for CVE-2025-4476 [High] Patch libsoup for CVE-2025-4476, CVE-2025-32907 Jun 13, 2025
@kevin-b-lockwood kevin-b-lockwood force-pushed the kevin-b-lockwood/libsoup-3.0-CVE branch from b74461a to a4c772c Compare June 13, 2025 18:35
@kevin-b-lockwood kevin-b-lockwood changed the base branch from 3.0-dev to fasttrack/3.0 June 13, 2025 18:35
@microsoft-github-policy-service microsoft-github-policy-service bot added the fasttrack/3.0 PRs Destined for Azure Linux 3.0 label Jun 13, 2025
@kevin-b-lockwood
Copy link
Contributor Author

Re-targeted fasttrack/3.0 because this PR now has a high priority CVE attached to it now

@Kanishk-Bansal
Copy link
Contributor

/azurepipelines run

Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@Kanishk-Bansal Kanishk-Bansal removed the 3.0-dev PRs Destined for AzureLinux 3.0 label Jun 13, 2025
@Kanishk-Bansal
Copy link
Contributor

Buddy Build

@Kanishk-Bansal Kanishk-Bansal added the CVEFixReadyForMaintainerReview When a CVE fix has been reviewed by release manager and is ready for stable maintainer review label Jun 16, 2025
@jslobodzian jslobodzian merged commit 5472414 into microsoft:fasttrack/3.0 Jun 16, 2025
24 of 29 checks passed
CBL-Mariner-Bot pushed a commit that referenced this pull request Jun 16, 2025
@CBL-Mariner-Bot
Copy link
Collaborator

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CVEFixReadyForMaintainerReview When a CVE fix has been reviewed by release manager and is ready for stable maintainer review fasttrack/3.0 PRs Destined for Azure Linux 3.0 Packaging security
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants