Skip to content

fix(deps): update dependency express to ~4.20.0 [security]#1993

Open
renovate[bot] wants to merge 1 commit intodevelopfrom
renovate/npm-express-vulnerability
Open

fix(deps): update dependency express to ~4.20.0 [security]#1993
renovate[bot] wants to merge 1 commit intodevelopfrom
renovate/npm-express-vulnerability

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Mar 29, 2024

This PR contains the following updates:

Package Change Age Confidence
express (source) ~4.18.3~4.20.0 age confidence

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 the location 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 within res.redirect().

Patches

expressjs/express@0867302
expressjs/express@0b74695

An initial fix went out with express@4.19.0, we then patched a feature regression in 4.19.1 and added improved handling for the bypass in 4.19.2.

Workarounds

The fix for this involves pre-parsing the url string with either require('node:url').parse or new URL. These are steps you can take on your own before passing the user input string to res.location or res.redirect.

Resources

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 code

Patches

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:

  1. The attacker MUST control the input to response.redirect()
  2. express MUST NOT redirect before the template appears
  3. the browser MUST NOT complete redirection before:
  4. the user MUST click on the link in the template

Release Notes

expressjs/express (express)

v4.20.0

Compare Source

==========

  • deps: serve-static@​0.16.0
    • Remove link renderization in html while redirecting
  • deps: send@​0.19.0
    • Remove link renderization in html while redirecting
  • deps: body-parser@​0.6.0
    • add depth option to customize the depth level in the parser
    • IMPORTANT: The default depth level for parsing URL-encoded data is now 32 (previously was Infinity)
  • Remove link renderization in html while using res.redirect
  • deps: path-to-regexp@​0.1.10
    • Adds support for named matching groups in the routes using a regex
    • Adds backtracking protection to parameters without regexes defined
  • deps: encodeurl@~2.0.0
    • Removes encoding of \, |, and ^ to align better with URL spec
  • Deprecate passing options.maxAge and options.expires to res.clearCookie
    • Will be ignored in v5, clearCookie will set a cookie with an expires in the past to instruct clients to delete the cookie

v4.19.2

Compare Source

==========

  • Improved fix for open redirect allow list bypass

v4.19.1

Compare Source

==========

  • Allow passing non-strings to res.location with new encoding handling checks

v4.19.0

Compare Source

==========

  • Prevent open redirect allow list bypass due to encodeurl
  • deps: cookie@​0.6.0

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.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot force-pushed the renovate/npm-express-vulnerability branch 4 times, most recently from d4d6aa5 to 2ec6fac Compare April 6, 2024 21:37
@renovate renovate bot force-pushed the renovate/npm-express-vulnerability branch 3 times, most recently from e33c780 to c6aac9e Compare April 17, 2024 15:40
@renovate renovate bot force-pushed the renovate/npm-express-vulnerability branch 3 times, most recently from c99e97e to 41e34cd Compare April 26, 2024 06:29
@renovate renovate bot force-pushed the renovate/npm-express-vulnerability branch 5 times, most recently from 7d9e5b6 to ef76c54 Compare May 11, 2024 06:41
@renovate renovate bot force-pushed the renovate/npm-express-vulnerability branch 2 times, most recently from d2f2128 to b561e10 Compare May 16, 2024 14:12
@renovate renovate bot force-pushed the renovate/npm-express-vulnerability branch 3 times, most recently from 64d328e to 6c9180b Compare June 20, 2024 18:25
@renovate renovate bot force-pushed the renovate/npm-express-vulnerability branch 2 times, most recently from c47821f to 8012d73 Compare July 5, 2024 09:02
@renovate renovate bot force-pushed the renovate/npm-express-vulnerability branch from 8012d73 to bd46e62 Compare July 11, 2024 01:08
@renovate renovate bot force-pushed the renovate/npm-express-vulnerability branch from bd46e62 to a5833bb Compare July 24, 2024 15:05
@renovate renovate bot force-pushed the renovate/npm-express-vulnerability branch from a5833bb to c3c2067 Compare August 6, 2024 17:37
@renovate renovate bot force-pushed the renovate/npm-express-vulnerability branch 5 times, most recently from 19d3f55 to 3714f15 Compare August 20, 2024 18:38
@renovate renovate bot force-pushed the renovate/npm-express-vulnerability branch 9 times, most recently from 5c724d2 to 6455e47 Compare September 21, 2024 07:06
@renovate renovate bot changed the title fix(deps): update dependency express to ~4.19.0 [security] fix(deps): update dependency express to ~4.20.0 [security] Sep 21, 2024
@renovate renovate bot force-pushed the renovate/npm-express-vulnerability branch 6 times, most recently from 6e4b284 to b352fb9 Compare September 28, 2024 19:36
@renovate renovate bot force-pushed the renovate/npm-express-vulnerability branch 3 times, most recently from 2f9ad68 to d81befb Compare October 12, 2024 12:03
@renovate renovate bot force-pushed the renovate/npm-express-vulnerability branch 4 times, most recently from cd6b9de to cd60f8b Compare October 21, 2024 17:34
@renovate renovate bot force-pushed the renovate/npm-express-vulnerability branch 4 times, most recently from 327f9e3 to 4143ae1 Compare October 24, 2024 21:20
@coderabbitai
Copy link

coderabbitai bot commented Feb 24, 2025

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Note

Other AI code review bot(s) detected

CodeRabbit has detected other AI code review bot(s) in this pull request and will avoid duplicating their findings in the review comments. This may lead to a less comprehensive review.


Comment @coderabbitai help to get the list of available commands and usage tips.

encodeurl "~1.0.2"
escape-html "~1.0.3"
parseurl "~1.3.3"
send "0.18.0"
Copy link

Choose a reason for hiding this comment

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

There appears to be a dependency version inconsistency in the yarn.lock file. The serve-static@1.16.0 package is still referencing send@0.18.0, but the Express 4.20.0 update includes send@0.19.0. This mismatch could potentially prevent the security fixes from being fully applied or cause compatibility issues.

Consider running yarn install again after merging to ensure the dependency tree is properly resolved, or manually verify that the correct version of send is being used in the final build.

Suggested change
send "0.18.0"
send "0.19.0"

Spotted by Diamond

Fix in Graphite


Is this helpful? React 👍 or 👎 to let us know.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants