🚨 [security] [node] Update multer 1.4.5-lts.1 → 2.0.2 (major) #495
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
depfu
bot
force-pushed
the
depfu/update/node/npm/multer-2.0.2
branch
10 times, most recently
from
04370d2 to
3893de1
Compare
depfu
bot
force-pushed
the
depfu/update/node/npm/multer-2.0.2
branch
18 times, most recently
from
8e43cac to
65ff606
Compare
depfu
bot
force-pushed
the
depfu/update/node/npm/multer-2.0.2
branch
from
e258851 to
765a2dc
Compare
depfu
bot
force-pushed
the
depfu/update/node/npm/multer-2.0.2
branch
from
765a2dc to
7ef4e17
Compare
depfu
bot
force-pushed
the
depfu/update/node/npm/multer-2.0.2
branch
from
7ef4e17 to
6902ef0
Compare
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.
Welcome to Depfu 👋
This is one of the first three pull requests with dependency updates we've sent your way. We tried to start with a few easy patch-level updates. Hopefully your tests will pass and you can merge this pull request without too much risk. This should give you an idea how Depfu works in general.
After you merge your first pull request, we'll send you a few more. We'll never open more than seven PRs at the same time so you're not getting overwhelmed with updates.
Let us know if you have any questions. Thanks so much for giving Depfu a try!
🚨 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.5-lts.1 → 2.0.2) · Repo · Changelog
Security Advisories 🚨
🚨 Multer vulnerable to Denial of Service via unhandled exception from malformed request
🚨 Multer vulnerable to Denial of Service via unhandled exception
🚨 Multer vulnerable to Denial of Service via memory leaks from unclosed streams
🚨 Multer vulnerable to Denial of Service from maliciously crafted requests
Release Notes
2.0.1
2.0.0
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 2 commits:
🔖 2.0.2🥅 improve error handlingCommits
See the full diff on Github. The new version differs by 2 commits:
2.0.0[email protected] (#61)🗑️ core-util-is (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 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