Skip to content

🚨 [security] [backend] Update multer 1.4.3 → 2.0.2 (major) #419

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

Jump to bottom
Open
depfu wants to merge 1 commit into
base: main
Choose a base branch
from
Open

🚨 [security] [backend] Update multer 1.4.3 → 2.0.2 (major) #419

depfu wants to merge 1 commit into from

Conversation

@depfu
Copy link
Contributor

@depfu depfu bot commented Jul 18, 2025

🚨 Your current dependencies have known security vulnerabilities 🚨

This dependency update fixes known security vulnerabilities. Please see the details below and assess their impact carefully. We recommend to merge and deploy this as soon as possible!

Here is everything you need to know about this upgrade. Please take a good look at what changed and the test results before merging this pull request.

What changed?

✳️ multer (1.4.3 → 2.0.2) · Repo · Changelog

Security Advisories 🚨

🚨 Multer vulnerable to Denial of Service via unhandled exception from malformed request

Impact

A vulnerability in Multer versions >= 1.4.4-lts.1, < 2.0.2 allows an attacker to trigger a Denial of Service (DoS) by sending a malformed request. This request causes an unhandled exception, leading to a crash of the process.

Patches

Users should upgrade to 2.0.2

Workarounds

None

🚨 Multer vulnerable to Denial of Service via unhandled exception

Impact

A vulnerability in Multer versions >=1.4.4-lts.1, <2.0.1 allows an attacker to trigger a Denial of Service (DoS) by sending an upload file request with an empty string field name. This request causes an unhandled exception, leading to a crash of the process.

Patches

Users should upgrade to 2.0.1

Workarounds

None

References

35a3272
#1233
#1256

🚨 Multer vulnerable to Denial of Service via memory leaks from unclosed streams

Impact

Multer <2.0.0 is vulnerable to a resource exhaustion and memory leak issue due to improper stream handling. When the HTTP request stream emits an error, the internal busboy stream is not closed, violating Node.js stream safety guidance.

This leads to unclosed streams accumulating over time, consuming memory and file descriptors. Under sustained or repeated failure conditions, this can result in denial of service, requiring manual server restarts to recover. All users of Multer handling file uploads are potentially impacted.

Patches

Users should upgrade to 2.0.0

Workarounds

None

References

🚨 Multer vulnerable to Denial of Service from maliciously crafted requests

Impact

A vulnerability in Multer versions >=1.4.4-lts.1 allows an attacker to trigger a Denial of Service (DoS) by sending a malformed multi-part upload request. This request causes an unhandled exception, leading to a crash of the process.

Patches

Users should upgrade to 2.0.0

Workarounds

None

References

Release Notes

2.0.2

Important

Full Changelog: v2.0.1...v2.0.2

2.0.1

Important

What's Changed

New Contributors

Full Changelog: v2.0.0...v.2.0.1

2.0.0

Important

What's Changed

  • 🐛 drain stream. fixes regression in node 18, remove old CI, set minimum node version, fix readme badges, add .npmrc
  • fix: handle two busboy error events
  • ♻️ fully drain stream
  • 🥅 explicitly handle req error
  • 🚨 lint:fix
  • ⬆️ bump mocha
  • docs: include release 2.0.0 details

1.4.4 (from changelog)

  • Bugfix: Handle missing field names (#913)
  • Docs: Add Vietnamese translation (#803)
  • Docs: Improve Spanish translation (#948)

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by 68 commits:

↗️ busboy (indirect, 0.2.14 → 1.6.0) · Repo

Commits

See the full diff on Github. The new version differs by 31 commits:

↗️ concat-stream (indirect, 1.6.2 → 2.0.0) · Repo

Commits

See the full diff on Github. The new version differs by 2 commits:

↗️ mkdirp (indirect, 0.5.5 → 0.5.6) · Repo

Sorry, we couldn't find anything useful about this release.

↗️ readable-stream (indirect, 1.1.14 → 3.6.2) · Repo

Release Notes

3.6.2

What's Changed

Full Changelog: v3.6.1...v3.6.2

3.6.0

  • Fix babel loose mode for classes and update to Node v10.19.0 #428 by @ljharb

3.5.0

  • Update to Node v10.18.1 #420

2.3.8

What's Changed

  • fix undefined global for browser / service worker (v2.x branch) by @smeng9 in #499

Full Changelog: v2.3.7...v2.3.8

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ streamsearch (indirect, 0.1.2 → 1.1.0) · Repo

Commits

See the full diff on Github. The new version differs by 10 commits:

↗️ string_decoder (indirect, 0.10.31 → 1.3.0) · Repo

Commits

See the full diff on Github. The new version differs by 55 commits:

🗑️ core-util-is (removed)

🗑️ dicer (removed)

🗑️ isarray (removed)

🗑️ process-nextick-args (removed)

👉 No CI detected

You don't seem to have any Continuous Integration service set up!

Without a service that will test the Depfu branches and pull requests, we can't inform you if incoming updates actually work with your app. We think that this degrades the service we're trying to provide down to a point where it is more or less meaningless.

This is fine if you just want to give Depfu a quick try. If you want to really let Depfu help you keep your app up-to-date, we recommend setting up a CI system:

* [Circle CI](https://circleci.com), [Semaphore ](https://semaphoreci.com) and [Github Actions](https://docs.github.com/actions) are all excellent options. * If you use something like Jenkins, make sure that you're using the Github integration correctly so that it reports status data back to Github. * If you have already set up a CI for this repository, you might need to check your configuration. Make sure it will run on all new branches. If you don’t want it to run on every branch, you can whitelist branches starting with `depfu/`.

Depfu Status

Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with @depfu rebase.

All Depfu comment commands
@​depfu rebase
Rebases against your default branch and redoes this update
@​depfu recreate
Recreates this PR, overwriting any edits that you've made to it
@​depfu merge
Merges this PR once your tests are passing and conflicts are resolved
@​depfu cancel merge
Cancels automatic merging of this PR
@​depfu close
Closes this PR and deletes the branch
@​depfu reopen
Restores the branch and reopens this PR (if it's closed)
@​depfu pause
Ignores all future updates for this dependency and closes this PR
@​depfu pause [minor|major]
Ignores all future minor/major updates for this dependency and closes this PR
@​depfu resume
Future versions of this dependency will create PRs again (leaves this PR as is)

@depfu depfu bot added the depfu label Jul 18, 2025
@depfu depfu bot mentioned this pull request Jul 18, 2025
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

depfu

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant