Skip to content

[Medium] Patch nodejs for CVE-2025-23167 #14333

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

Open
wants to merge 2 commits into
base: 3.0-dev
Choose a base branch
from

Conversation

akhila-guruju
Copy link
Contributor

@akhila-guruju akhila-guruju commented Jul 17, 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 nodejs for CVE-2025-23167
Astrolabe Patch Reference: nodejs/node#48981
Upstream patch reference: nodejs/node@a7b8e85
Patch Modified: Yes

  • no need to patch for doc/contributing/maintaining/maintaining-dependencies.md as no version information is given in code for other deps also.
  • Since azl is using llhttp v8.1.2 and the upstream patch is for an earlier version, v8.1.1, some changes are already included in azl.
Change Log
  • new file: SPECS/nodejs/CVE-2025-23167.patch
  • modified: SPECS/nodejs/nodejs.spec
Does this affect the toolchain?

NO

Associated issues
  • #xxxx
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 Jul 17, 2025
@akhila-guruju akhila-guruju changed the title checking build for nodejs with patch [Medium] Patch nodejs for CVE-2025-23167 Jul 18, 2025
@akhila-guruju akhila-guruju changed the title [Medium] Patch nodejs for CVE-2025-23167 checking build for nodejs after applying patch Jul 18, 2025
@akhila-guruju akhila-guruju changed the title checking build for nodejs after applying patch [Medium] Patch nodejs for CVE-2025-23167 Jul 24, 2025
@akhila-guruju akhila-guruju marked this pull request as ready for review July 24, 2025 07:17
@akhila-guruju akhila-guruju requested a review from a team as a code owner July 24, 2025 07:17
@Malateshk007 Malateshk007 requested a review from kgodara912 July 28, 2025 05:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
3.0-dev PRs Destined for AzureLinux 3.0 Packaging
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant