security: address actionable dependency vulnerabilities - #22
Merged
Conversation
Upgrade multer to 2.3.0 and cap field nesting so upload parsing cannot be used for denial of service.
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
multerfrom 2.1.1 to 2.3.0 (nested-field and aborted-upload DoS)Other audit findings were left unchanged: path-to-regexp ReDoS needs wildcard routes we do not define, uuid v3/v5/v6 is unused, qs/body-parser cases are not reachable, and frontend axios/react-router advisories apply to Node SSRF or Framework Mode which this SPA does not use.
Testing
npm test— 75 tests passednpm run buildsucceeded