CVE-2024-29041: Express.js Open Redirect in malformed URLs

Published Mar 25, 2024
·
Updated

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

https://github.com/expressjs/express/commit/0867302ddbde0e9463d0564fea5861feb708c2dd https://github.com/expressjs/express/commit/0b746953c4bd8e377123527db11f9cd866e39f94

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.

References

https://github.com/expressjs/express/pull/5539 https://github.com/koajs/koa/issues/1800 https://expressjs.com/en/4x/api.html#res.location

Other sources

Express.js Express could allow a remote attacker to conduct phishing attacks, caused by an open redirect vulnerability. An attacker could exploit this vulnerability using a specially crafted URL to redirect a victim to arbitrary Web sites.

IBM

Express.js minimalist web framework for node. Versions of Express.js prior to 4.19.0 and all pre-release alpha and beta versions of 5.0 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(). The vulnerability is fixed in 4.19.2 and 5.0.0-beta.3.

NVD

Express.js Open Redirect in malformed URLs

Microsoft

Affected Software

21 affected componentsFixes available
npm/express>=5.0.0-alpha.1<5.0.0-beta.3
5.0.0-beta.3
npm/express<4.19.2
4.19.2
IBM Data Virtualization on Cloud Pak for Data<=3.0
IBM Watson Query on Cloud Pak for Data<=2.2
IBM Watson Query on Cloud Pak for Data<=2.1
IBM Watson Query on Cloud Pak for Data<=2.0
IBM Data Virtualization on Cloud Pak for Data<=1.8
IBM Data Virtualization on Cloud Pak for Data<=1.7
Openjsf Express Node.js<4.19.2
Openjsf Express Node.js=5.0.0-alpha1
Openjsf Express Node.js=5.0.0-alpha2
Openjsf Express Node.js=5.0.0-alpha3
Openjsf Express Node.js=5.0.0-alpha4
Openjsf Express Node.js=5.0.0-alpha5
Openjsf Express Node.js=5.0.0-alpha6
Openjsf Express Node.js=5.0.0-alpha7
Openjsf Express Node.js=5.0.0-alpha8
Openjsf Express Node.js=5.0.0-beta1
Openjsf Express Node.js=5.0.0-beta2
Microsoft cbl2 reaper 3.1.1-8
Microsoft cbl2 reaper 3.1.1-9

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade npm/express to a version that resolves this vulnerability.

    Fixed in 5.0.0-beta.3
  2. Upgrade

    Upgrade npm/express to a version that resolves this vulnerability.

    Fixed in 4.19.2
  3. Upgrade

    Upgrade expressjs/express to a version that resolves this vulnerability.

    Fixed in 4.19.2
  4. Upgrade

    Upgrade expressjs/express to a version that resolves this vulnerability.

    Fixed in 5.0.0-beta.3
  5. Configuration

    If you control the application code path, pre-parse the user-provided URL string using either `require('node:url').parse` or `new URL` before passing it to `res.location()` or `res.redirect()`, since `res.location()` (and thus `res.redirect()`) uses malformed URL evaluation that can bypass allow list implementations.

    Express.js (res.location / res.redirect) URL parsing before calling res.location/res.redirect = pre-parse with either require('node:url').parse or new URL

Event History

Mar 25, 2024
Advisory Published
via GitHub·07:40 PM
CVE Published
via MITRE·08:20 PM
Data Sourced
via MITRE·08:20 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·09:15 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·09:15 PM
RemedyAffected Software
Apr 1, 2024
Data Sourced
via Microsoft·07:00 AM
DescriptionSeverityWeakness
Data Sourced
via Microsoft·07:00 AM
Affected Software
Updated
via Microsoft·07:00 AM
DescriptionSeverity
Jun 7, 2024
Data Sourced
via Red Hat·05:09 PM
DescriptionSeverityAffected Software
Aug 15, 2025
Data Sourced
via IBM·03:29 PM
DescriptionAffected Software

Parent advisories

This vulnerability appears in the following advisories.

Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2024-29041?

CVE-2024-29041 is classified as a moderate severity vulnerability due to the potential for open redirects.

2

How do I fix CVE-2024-29041?

To fix CVE-2024-29041, upgrade to Express.js version 4.19.2 or later, or 5.0.0-beta.3 or newer.

3

What are the affected versions for CVE-2024-29041?

CVE-2024-29041 affects Express.js versions prior to 4.19.2 and all pre-release versions before 5.0.0-beta.3.

4

What type of vulnerability is CVE-2024-29041?

CVE-2024-29041 is an open redirect vulnerability, which arises from improperly handling user-provided URLs.

5

Which applications might be impacted by CVE-2024-29041?

Applications using affected versions of Express.js, including IBM Controller and IBM Cognos Controller, might be impacted by CVE-2024-29041.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203