Search for packages
| purl | pkg:npm/express@3.0.0-alpha5 |
| Vulnerability | Summary | Fixed by |
|---|---|---|
|
VCID-8jr1-tn77-dfds
Aliases: CVE-2014-6393 GHSA-gpvr-g6gh-9mc2 |
No Charset in Content-Type Header Express do not specify a charset field in the content-type header while displaying level response messages. The lack of enforcing user's browser to set correct charset, could be leveraged by an attacker to perform a cross-site scripting attack, using non-standard encodings, like UTF-7. |
Affected by 5 other vulnerabilities. Affected by 3 other vulnerabilities. |
|
VCID-axqm-hk9c-53gn
Aliases: CVE-2024-29041 GHSA-rv95-896h-c2vc |
Express.js Open Redirect in malformed URLs ### 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`](https://github.com/pillarjs/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`. ### Resources https://github.com/expressjs/express/pull/5539 https://github.com/koajs/koa/issues/1800 https://expressjs.com/en/4x/api.html#res.location |
Affected by 1 other vulnerability. Affected by 1 other vulnerability. |
|
VCID-bcuh-2e2c-53gy
Aliases: CVE-2022-24999 GHSA-hrpp-h998-j3pp |
qs vulnerable to Prototype Pollution qs before 6.10.3 allows attackers to cause a Node process hang because an `__ proto__` key can be used. In many typical web framework use cases, an unauthenticated remote attacker can place the attack payload in the query string of the URL that is used to visit the application, such as `a[__proto__]=b&a[__proto__]&a[length]=100000000`. The fix was backported to qs 6.9.7, 6.8.3, 6.7.3, 6.6.1, 6.5.3, 6.4.1, 6.3.3, and 6.2.4. |
Affected by 2 other vulnerabilities. |
|
VCID-fevu-q6th-9beb
Aliases: CVE-2024-43796 GHSA-qw6h-vgh9-j6wx |
express vulnerable to XSS via response.redirect() ### 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() 1. express MUST NOT redirect before the template appears 1. the browser MUST NOT complete redirection before: 1. the user MUST click on the link in the template |
Affected by 0 other vulnerabilities. Affected by 1 other vulnerability. |
|
VCID-hyrv-e649-23fr
Aliases: CVE-2024-10491 GHSA-cm5g-3pgc-8rg4 |
Express ressource injection A vulnerability has been identified in the Express response.links function, allowing for arbitrary resource injection in the Link header when unsanitized data is used. The issue arises from improper sanitization in `Link` header values, which can allow a combination of characters like `,`, `;`, and `<>` to preload malicious resources. This vulnerability is especially relevant for dynamic parameters. |
Affected by 4 other vulnerabilities. |
| Vulnerability | Summary | Aliases |
|---|---|---|
| This package is not known to fix vulnerabilities. | ||