[Aikido] Fix 4 security issues in lodash, @aws-sdk/client-sts, @aws-sdk/client-cloudfront and 3 more#22
Open
aikido-autofix[bot] wants to merge 1 commit intomainfrom
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 vulnerabilities in lodash, js-yaml, and AWS SDK, mitigating potential remote code execution risks.
✅ Code not affected by breaking changes.
The breaking change in
@smithy/config-resolver(dropping Node.js 16 support) does not affect this codebase. The package is only a transitive dependency brought in through the AWS SDK clients used byoclif, which is itself a dependency of@asyncapi/cli.The codebase does not directly import or use
@smithy/config-resolver, and the dependency chain already requires Node.js >= 18.0.0 (enforced by theoclifpackage). Therefore, the Node.js 16 support removal has no practical impact on this project.✅ 4 CVEs resolved by this upgrade
This PR will resolve the following CVEs: