Express.js Open Redirect in malformed URLs
Affected releases · express
- 4.x4.0.0 – 4.19.1Fixed in 4.19.2
- 3.x and older0.14.0 – 3.21.2No fix, no longer updated
On 4.x, the newest line:
npm install express@4.19.2Not affected
5.0.0 – 5.3.0
6 releases, latest
Affected
4.0.0 – 4.19.1
86 releases
Fixed
4.19.2 – 4.22.3
9 releases
Affected
3.0.0 – 3.21.2
96 releases
Affected
2.0.0 – 2.5.11
39 releases
Affected
1.0.0 – 1.0.8
9 releases
Affected
0.14.0 – 0.14.1
2 releases
Is your project affected?
Paste your package.json, or type the range you declare for express. It is read in your browser and sent nowhere.
What happens
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
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