Open
Conversation
Regenerate package-lock.json to resolve jws to safe version for CVE-2025-65945. Bump task patch version. AB#2339822
|
Azure Pipelines: Successfully started running 3 pipeline(s). |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Context
AB#2339822
CG Alert 342212
Vulnerability reported in jws 3.2.2 (CVE-2025-65945, High severity).
jws 3.2.2 is pulled in transitively via azure-arm-rest -> jsonwebtoken -> jws.
Safe version: jws 4.0.1
Task Name
AzureSpringCloudV0
Description
Regenerate package-lock.json to resolve jws to 4.0.1 (safe version) for CVE-2025-65945. Updated transitive dependencies including azure-arm-rest to latest version.
Risk Assessment (Low / Medium / High)
Low
Change Behind Feature Flag (Yes / No)
No - dependency version update only
Tech Design / Approach
Documentation Changes Required (Yes/No)
No
Unit Tests Added or Updated (Yes / No)
No - dependency update only, no code changes
Additional Testing Performed
Verified jws resolves to 4.0.1 in regenerated lock file.
Logging Added/Updated (Yes/No)
No
Telemetry Added/Updated (Yes/No)
No
Rollback Scenario and Process (Yes/No)
Revert the package-lock.json changes.
Dependency Impact Assessed and Regression Tested (Yes/No)
Yes - only transitive dependency versions changed.
Checklist