-
Notifications
You must be signed in to change notification settings - Fork 7
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.
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
fix(deps): update dependency express to v4.20.0 [security] #234
Open
renovate
wants to merge
1
commit into
main
Choose a base branch
from
renovate/npm-express-vulnerability
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Conversation
This file contains 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
New and removed dependencies detected. Learn more about Socket for GitHub ↗︎
🚮 Removed packages: npm/[email protected] |
renovate
bot
force-pushed
the
renovate/npm-express-vulnerability
branch
from
April 17, 2024 12:55
bdd48cc
to
f38bab4
Compare
renovate
bot
force-pushed
the
renovate/npm-express-vulnerability
branch
3 times, most recently
from
May 10, 2024 14:19
a874c11
to
32e6a04
Compare
renovate
bot
force-pushed
the
renovate/npm-express-vulnerability
branch
from
May 22, 2024 15:06
32e6a04
to
1bb1623
Compare
renovate
bot
force-pushed
the
renovate/npm-express-vulnerability
branch
2 times, most recently
from
May 22, 2024 15:15
a69b238
to
1a351a9
Compare
renovate
bot
force-pushed
the
renovate/npm-express-vulnerability
branch
2 times, most recently
from
June 12, 2024 14:05
0f4ca1a
to
37a1f2b
Compare
renovate
bot
force-pushed
the
renovate/npm-express-vulnerability
branch
5 times, most recently
from
July 1, 2024 12:41
e869e2c
to
c20011d
Compare
renovate
bot
force-pushed
the
renovate/npm-express-vulnerability
branch
3 times, most recently
from
July 9, 2024 01:09
6d6e1a5
to
c56a0f5
Compare
renovate
bot
force-pushed
the
renovate/npm-express-vulnerability
branch
2 times, most recently
from
July 22, 2024 10:03
609ffbb
to
3eab9e4
Compare
renovate
bot
changed the title
fix(deps): update dependency express to v4.19.2 [security]
fix(deps): update dependency express to v4.20.0 [security]
Sep 11, 2024
renovate
bot
force-pushed
the
renovate/npm-express-vulnerability
branch
6 times, most recently
from
September 18, 2024 13:36
ee32811
to
0f7a2ca
Compare
renovate
bot
force-pushed
the
renovate/npm-express-vulnerability
branch
from
October 9, 2024 18:30
0f7a2ca
to
838e5d3
Compare
renovate
bot
force-pushed
the
renovate/npm-express-vulnerability
branch
3 times, most recently
from
November 6, 2024 23:19
ec95365
to
71d152f
Compare
Signed-off-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
renovate
bot
force-pushed
the
renovate/npm-express-vulnerability
branch
from
November 21, 2024 13:14
71d152f
to
9cc8221
Compare
renovate
bot
changed the title
fix(deps): update dependency express to v4.20.0 [security]
fix(deps): update dependency express to v4.20.0 [security] - autoclosed
Dec 8, 2024
renovate
bot
changed the title
fix(deps): update dependency express to v4.20.0 [security] - autoclosed
fix(deps): update dependency express to v4.20.0 [security]
Dec 8, 2024
renovate
bot
force-pushed
the
renovate/npm-express-vulnerability
branch
from
December 8, 2024 23:32
59ee860
to
9cc8221
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.
This PR contains the following updates:
4.18.3
->4.20.0
GitHub Vulnerability Alerts
CVE-2024-29041
Impact
Versions of Express.js prior to 4.19.2 and pre-release alpha and beta versions before 5.0.0-beta.3 are affected by an open redirect vulnerability using malformed URLs.
When a user of Express performs a redirect using a user-provided URL Express performs an encode using
encodeurl
on the contents before passing it to thelocation
header. This can cause malformed URLs to be evaluated in unexpected ways by common redirect allow list implementations in Express applications, leading to an Open Redirect via bypass of a properly implemented allow list.The main method impacted is
res.location()
but this is also called from withinres.redirect()
.Patches
expressjs/express@0867302
expressjs/express@0b74695
An initial fix went out with
[email protected]
, we then patched a feature regression in4.19.1
and added improved handling for the bypass in4.19.2
.Workarounds
The fix for this involves pre-parsing the url string with either
require('node:url').parse
ornew URL
. These are steps you can take on your own before passing the user input string tores.location
orres.redirect
.References
https://github.com/expressjs/express/pull/5539
https://github.com/koajs/koa/issues/1800
https://expressjs.com/en/4x/api.html#res.location
CVE-2024-43796
Impact
In express <4.20.0, passing untrusted user input - even after sanitizing it - to
response.redirect()
may execute untrusted codePatches
this issue is patched in express 4.20.0
Workarounds
users are encouraged to upgrade to the patched version of express, but otherwise can workaround this issue by making sure any untrusted inputs are safe, ideally by validating them against an explicit allowlist
Details
successful exploitation of this vector requires the following:
Express.js Open Redirect in malformed URLs
CVE-2024-29041 / GHSA-rv95-896h-c2vc
More information
Details
Impact
Versions of Express.js prior to 4.19.2 and pre-release alpha and beta versions before 5.0.0-beta.3 are affected by an open redirect vulnerability using malformed URLs.
When a user of Express performs a redirect using a user-provided URL Express performs an encode using
encodeurl
on the contents before passing it to thelocation
header. This can cause malformed URLs to be evaluated in unexpected ways by common redirect allow list implementations in Express applications, leading to an Open Redirect via bypass of a properly implemented allow list.The main method impacted is
res.location()
but this is also called from withinres.redirect()
.Patches
expressjs/express@0867302
expressjs/express@0b74695
An initial fix went out with
[email protected]
, we then patched a feature regression in4.19.1
and added improved handling for the bypass in4.19.2
.Workarounds
The fix for this involves pre-parsing the url string with either
require('node:url').parse
ornew URL
. These are steps you can take on your own before passing the user input string tores.location
orres.redirect
.References
https://github.com/expressjs/express/pull/5539
https://github.com/koajs/koa/issues/1800
https://expressjs.com/en/4x/api.html#res.location
Severity
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
References
This data is provided by OSV and the GitHub Advisory Database (CC-BY 4.0).
express vulnerable to XSS via response.redirect()
CVE-2024-43796 / GHSA-qw6h-vgh9-j6wx
More information
Details
Impact
In express <4.20.0, passing untrusted user input - even after sanitizing it - to
response.redirect()
may execute untrusted codePatches
this issue is patched in express 4.20.0
Workarounds
users are encouraged to upgrade to the patched version of express, but otherwise can workaround this issue by making sure any untrusted inputs are safe, ideally by validating them against an explicit allowlist
Details
successful exploitation of this vector requires the following:
Severity
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:L
References
This data is provided by OSV and the GitHub Advisory Database (CC-BY 4.0).
Release Notes
expressjs/express (express)
v4.20.0
Compare Source
==========
depth
option to customize the depth level in the parserdepth
level for parsing URL-encoded data is now32
(previously wasInfinity
)res.redirect
\
,|
, and^
to align better with URL specoptions.maxAge
andoptions.expires
tores.clearCookie
v4.19.2
Compare Source
==========
v4.19.1
Compare Source
==========
v4.19.0
Compare Source
Configuration
📅 Schedule: Branch creation - "" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.