chore(deps): security dependency updates #4
Conversation
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
1 participant
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.
Summary
This PR updates npm dependencies to resolve Dependabot-reported security vulnerabilities. Changes are limited to dependency/version bumps and lockfile updates (no intended runtime behavior changes beyond security fixes).
What changed
Updated dependencies flagged by Dependabot
Updated package-lock.json accordingly
Security issues resolved (Dependabot)
Critical
form-data: unsafe random function used for boundary selection
High
ip: SSRF / improper categorization of public vs private IPs
qs: arrayLimit bypass via bracket notation leading to potential DoS (memory exhaustion)
semver: Regular Expression DoS (ReDoS)
cross-spawn: ReDoS (multiple advisories)
axios: possible SSRF / credential leakage via absolute URL
axios: DoS due to missing data size checks
Moderate
tar: DoS when parsing tar files due to missing folder count validation
lodash: prototype pollution in _.unset / _.omit
@octokit/request: ReDoS via regex catastrophic backtracking
@octokit/plugin-paginate-rest: ReDoS via regex catastrophic backtracking
@octokit/request-error: ReDoS via regex catastrophic backtracking
js-yaml: prototype pollution in merge (<<) (multiple advisories)
Low
@smithy/config-resolver: defense-in-depth enhancement for region parameter handling
formidable: relies on hexoid to prevent guessing filenames for untrusted executable content
diff (jsdiff): DoS in parsePatch / applyPatch
tmp: symlink write via dir parameter
brace-expansion: ReDoS (multiple advisories)
Testing / Verification
CI / local checks: (fill in) npm test, npm run build, npm run lint