[Aikido] Fix 5 security issues in lodash, @aws-sdk/client-sts, @aws-sdk/client-cloudfront and 4 more#24
Closed
aikido-autofix[bot] wants to merge 1 commit intomainfrom
Closed
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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.
Upgrades multiple dependencies to address prototype pollution, ReDoS, and AWS SDK configuration vulnerabilities that could enable remote code execution and service disruption.
✅ Code not affected by breaking changes.
No breaking changes from these package upgrades affect this codebase.
Both
minimatchand@smithy/config-resolverare transitive dependencies that are not directly imported or used in the application code. The breaking changes are limited to Node.js version requirements:minimatch10.x requires Node.js 20 or 22+@smithy/config-resolver4.x requires Node.js 18+Since the codebase already depends on
@oclif/corev3.27.0 which requires Node.js >=18.0.0, the project must already be running on Node.js 18 or higher. If the project is running on Node.js 18 or 19, upgradingminimatchto 10.x would require upgrading to Node.js 20+. However, the@smithy/config-resolverupgrade would be compatible with the current setup.The actual risk depends on the Node.js version being used in production. If already on Node.js 20+, there is no risk. If on Node.js 18-19, only the
minimatchupgrade would require a Node.js version bump.✅ 5 CVEs resolved by this upgrade
This PR will resolve the following CVEs: