*For some transitive vulnerabilities, there is no version of direct dependency with a fix. Check the "Details" section below to see if there is a version of transitive dependency where vulnerability is fixed.
**In some cases, Remediation PR cannot be created automatically for a vulnerability despite the availability of remediation
Path to dependency file: /nodeJs/Content-type/package.json
Path to vulnerable library: /nodeJs/Content-type/package.json,/nodeJs/Url-redirection-harder2/package.json,/nodeJs/Url-redirection/package.json,/nodeJs/Url-redirection-harder/package.json,/nodeJs/SessionPuzzle/package.json,/nodeJs/Ldap-Injection/package.json,/nodeJs/CMD-Blind/package.json,/nodeJs/Auth-Bypass/package.json,/nodeJs/Ratelimiting/package.json,/nodeJs/SSRF/package.json,/nodeJs/JWT-secret/package.json,/nodeJs/RFI/package.json,/nodeJs/JWT-null/package.json,/nodeJs/Prototype-Pollution/package.json,/nodeJs/RaceCondition/package.json,/nodeJs/Auth-Bypass-3/package.json,/nodeJs/Auth-Bypass-2/package.json,/nodeJs/SQLI-like/package.json,/nodeJs/Credentials-guessing-2/package.json,/nodeJs/DOS-regex/package.json,/nodeJs/CMD/package.json,/nodeJs/CORS/package.json,/nodeJs/LFI/package.json,/nodeJs/CSP/package.json,/nodeJs/Session-hijacking-xss/package.json,/nodeJs/CSSI/package.json,/nodeJs/Info-leakage-metadata/package.json,/nodeJs/Ldap-Injection-harder/package.json,/nodeJs/Credentials-guessing-1/package.json,/nodeJs/File-upload/package.json,/nodeJs/XSS-DOM-2/package.json,/nodeJs/SQLI-blind/package.json,/nodeJs/LFI-2/package.json,/nodeJs/Formula-Injection/package.json,/nodeJs/Auth-Bypass-simple/package.json,/nodeJs/XSS-DOM/package.json,/nodeJs/SQLI/package.json,/nodeJs/IDOR/package.json,/nodeJs/XSS-attribute/package.json,/nodeJs/ParameterBinding/package.json,/nodeJs/RaceCondition-file-write/package.json,/nodeJs/Auth-Bypass-1/package.json,/nodeJs/Info-leakage-comments/package.json,/nodeJs/CMD3/package.json,/nodeJs/CMD2/package.json,/nodeJs/CMD4/package.json,/nodeJs/CSRF-samesite/package.json,/nodeJs/XSS-url/package.json,/nodeJs/XXE/package.json,/nodeJs/CSRF-weak/package.json,/nodeJs/LFI-3/package.json
body-parser is Node.js body parsing middleware. body-parser <1.20.3 is vulnerable to denial of service when url encoding is enabled. A malicious actor using a specially crafted payload could flood the server with a large number of requests, resulting in denial of service. This issue is patched in 1.20.3.
qs before 6.10.3, as used in Express before 4.17.3 and other products, allows attackers to cause a Node process hang for an Express application because an __ proto__ key can be used. In many typical Express 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 (and therefore Express 4.17.3, which has "deps: qs@6.9.7" in its release description, is not vulnerable).
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`](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()`. The vulnerability is fixed in 4.19.2 and 5.0.0-beta.3.
Fast, unopinionated, minimalist web framework
Library home page: https://registry.npmjs.org/express/-/express-4.17.1.tgz
Found in HEAD commit: dbff3320673205dea2e0a4c513d54497ca905aab
Vulnerabilities
*For some transitive vulnerabilities, there is no version of direct dependency with a fix. Check the "Details" section below to see if there is a version of transitive dependency where vulnerability is fixed.
**In some cases, Remediation PR cannot be created automatically for a vulnerability despite the availability of remediation
Details
CVE-2024-45590
### Vulnerable Library - body-parser-1.19.0.tgzNode.js body parsing middleware
Library home page: https://registry.npmjs.org/body-parser/-/body-parser-1.19.0.tgz
Path to dependency file: /nodeJs/Content-type/package.json
Path to vulnerable library: /nodeJs/Content-type/package.json,/nodeJs/Url-redirection-harder2/package.json,/nodeJs/Url-redirection/package.json,/nodeJs/Url-redirection-harder/package.json,/nodeJs/SessionPuzzle/package.json,/nodeJs/Ldap-Injection/package.json,/nodeJs/CMD-Blind/package.json,/nodeJs/Auth-Bypass/package.json,/nodeJs/Ratelimiting/package.json,/nodeJs/SSRF/package.json,/nodeJs/JWT-secret/package.json,/nodeJs/RFI/package.json,/nodeJs/JWT-null/package.json,/nodeJs/Prototype-Pollution/package.json,/nodeJs/RaceCondition/package.json,/nodeJs/Auth-Bypass-3/package.json,/nodeJs/Auth-Bypass-2/package.json,/nodeJs/SQLI-like/package.json,/nodeJs/Credentials-guessing-2/package.json,/nodeJs/DOS-regex/package.json,/nodeJs/CMD/package.json,/nodeJs/CORS/package.json,/nodeJs/LFI/package.json,/nodeJs/CSP/package.json,/nodeJs/Session-hijacking-xss/package.json,/nodeJs/CSSI/package.json,/nodeJs/Info-leakage-metadata/package.json,/nodeJs/Ldap-Injection-harder/package.json,/nodeJs/Credentials-guessing-1/package.json,/nodeJs/File-upload/package.json,/nodeJs/XSS-DOM-2/package.json,/nodeJs/SQLI-blind/package.json,/nodeJs/LFI-2/package.json,/nodeJs/Formula-Injection/package.json,/nodeJs/Auth-Bypass-simple/package.json,/nodeJs/XSS-DOM/package.json,/nodeJs/SQLI/package.json,/nodeJs/IDOR/package.json,/nodeJs/XSS-attribute/package.json,/nodeJs/ParameterBinding/package.json,/nodeJs/RaceCondition-file-write/package.json,/nodeJs/Auth-Bypass-1/package.json,/nodeJs/Info-leakage-comments/package.json,/nodeJs/CMD3/package.json,/nodeJs/CMD2/package.json,/nodeJs/CMD4/package.json,/nodeJs/CSRF-samesite/package.json,/nodeJs/XSS-url/package.json,/nodeJs/XXE/package.json,/nodeJs/CSRF-weak/package.json,/nodeJs/LFI-3/package.json
Dependency Hierarchy: - express-4.17.1.tgz (Root Library) - :x: **body-parser-1.19.0.tgz** (Vulnerable Library)
Found in HEAD commit: dbff3320673205dea2e0a4c513d54497ca905aab
Found in base branch: master
### Vulnerability Detailsbody-parser is Node.js body parsing middleware. body-parser <1.20.3 is vulnerable to denial of service when url encoding is enabled. A malicious actor using a specially crafted payload could flood the server with a large number of requests, resulting in denial of service. This issue is patched in 1.20.3.
Publish Date: 2024-09-10
URL: CVE-2024-45590
### CVSS 3 Score Details (7.5)Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: None - Integrity Impact: None - Availability Impact: High
For more information on CVSS3 Scores, click here. ### Suggested FixType: Upgrade version
Origin: https://github.com/expressjs/body-parser/security/advisories/GHSA-qwcr-r2fm-qrc7
Release Date: 2024-09-10
Fix Resolution: body-parser - 1.20.3
CVE-2022-24999
### Vulnerable Library - qs-6.7.0.tgzA querystring parser that supports nesting and arrays, with a depth limit
Library home page: https://registry.npmjs.org/qs/-/qs-6.7.0.tgz
Dependency Hierarchy: - express-4.17.1.tgz (Root Library) - :x: **qs-6.7.0.tgz** (Vulnerable Library)
Found in HEAD commit: dbff3320673205dea2e0a4c513d54497ca905aab
Found in base branch: master
### Vulnerability Detailsqs before 6.10.3, as used in Express before 4.17.3 and other products, allows attackers to cause a Node process hang for an Express application because an __ proto__ key can be used. In many typical Express 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 (and therefore Express 4.17.3, which has "deps: qs@6.9.7" in its release description, is not vulnerable).
Publish Date: 2022-11-26
URL: CVE-2022-24999
### CVSS 3 Score Details (7.5)Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: None - Integrity Impact: None - Availability Impact: High
For more information on CVSS3 Scores, click here. ### Suggested FixType: Upgrade version
Origin: https://www.cve.org/CVERecord?id=CVE-2022-24999
Release Date: 2022-11-26
Fix Resolution (qs): 6.7.3
Direct dependency fix Resolution (express): 4.17.2
CVE-2024-29041
### Vulnerable Library - express-4.17.1.tgzFast, unopinionated, minimalist web framework
Library home page: https://registry.npmjs.org/express/-/express-4.17.1.tgz
Dependency Hierarchy: - :x: **express-4.17.1.tgz** (Vulnerable Library)
Found in HEAD commit: dbff3320673205dea2e0a4c513d54497ca905aab
Found in base branch: master
### Vulnerability DetailsExpress.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`](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()`. The vulnerability is fixed in 4.19.2 and 5.0.0-beta.3.
Publish Date: 2024-03-25
URL: CVE-2024-29041
### CVSS 3 Score Details (6.1)Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: Required - Scope: Changed - Impact Metrics: - Confidentiality Impact: Low - Integrity Impact: Low - Availability Impact: None
For more information on CVSS3 Scores, click here. ### Suggested FixType: Upgrade version
Origin: https://github.com/expressjs/express/security/advisories/GHSA-rv95-896h-c2vc
Release Date: 2024-03-25
Fix Resolution: 4.19.0