🚨 [security] Update express 4.18.3 → 4.19.2 (minor) #405
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.
🚨 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 update. Please take a good look at what changed and the test results before merging this pull request.
What changed?
✳️ express (4.18.3 → 4.19.2) · Repo · Changelog
Security Advisories 🚨
🚨 Express.js Open Redirect in malformed URLs
Release Notes
4.19.2
4.19.0
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 13 commits:
4.19.2
Improved fix for open redirect allow list bypass
4.19.1
Allow passing non-strings to res.location with new encoding handling checks fixes #5554 #5555
fixed un-edited version in history.md for 4.19.0
build: fix build due to inconsistent supertest behavior in older versions
4.19.0
Prevent open redirect allow list bypass due to encodeurl
Add note on how to update docs for new release (#5541)
deps: cookie@0.6.0
docs: loosen TC activity rules
docs: nominating @wesleytodd to be project captian
docs: update release date
🆕 cookie (added, 0.6.0)
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