Skip to content

[Snyk] Security upgrade connect-multiparty from 1.0.1 to 2.2.0 #29

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
fengmk2 wants to merge 1 commit into
base: master
Choose a base branch
from
Open

[Snyk] Security upgrade connect-multiparty from 1.0.1 to 2.2.0 #29

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -21,7 +21,7 @@
"address": "0.0.3",
"body-parser": "1.0.0",
"connect": "2.12.0",
"connect-multiparty": "1.0.1",
"connect-multiparty": "2.2.0",
Copy link
Copy Markdown

@gemini-code-assist gemini-code-assist Bot Jul 13, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

high

The upgrade to connect-multiparty@2.2.0 does not resolve the prototype poisoning vulnerability SNYK-JS-QS-3153490 because it depends on a vulnerable version of qs.

connect-multiparty@2.2.0 depends on multiparty@~4.1.2, which in turn depends on qs@6.1.0. According to the Snyk advisory, qs@6.1.0 is still vulnerable. A fix for this branch is in qs@6.1.1 or later.

Recommend using npm overrides or replacing connect-multiparty with a maintained alternative like multer to address the vulnerability effectively.

"debug": "0.7.4",
"eventproxy": "0.2.6",
"finished": "1.1.1",
Expand Down