[Aikido] Fix 4 security issues in lodash, js-yaml, @asyncapi/parser and 7 more#21
Closed
aikido-autofix[bot] wants to merge 1 commit intomainfrom
Closed
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
There was a problem hiding this comment.
3 Open source vulnerabilities detected - high severity
Aikido detected 3 vulnerabilities across 2 packages, it includes 2 high and 1 low vulnerabilities.
Remediation Aikido suggests bumping the vulnerable packages to a safe version.
View details in Aikido Security
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, YAML parsing, and AWS SDK configuration vulnerabilities that could enable remote code execution and improper API routing.
✅ Code not affected by breaking changes.
No breaking changes from either package upgrade affect this codebase.
js-yaml (3.14.1 => 4.1.1):
The codebase does not directly import or use
js-yamljs-yamlis only used as a transitive dependency through@asyncapi/parser@2.1.2The installed version of
@asyncapi/parser@2.1.2already depends onjs-yaml@^4.1.0The package.json includes an override forcing
js-yaml@<=4.1.1to use version4.1.1, meaning the codebase is already using js-yaml 4.xNo code uses deprecated methods like
safeLoad,safeDump,DEFAULT_SAFE_SCHEMA, orSchema.create@smithy/config-resolver (3.0.12 => 4.4.0):
This package is not directly used in the codebase
It appears only as a transitive dependency in AWS SDK packages
The codebase does not import or use any AWS SDK packages
The breaking change (dropping Node.js 16 support) is not relevant since the package is not directly used
✅ 4 CVEs resolved by this upgrade
This PR will resolve the following CVEs: