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).
CVE-2022-24999 - High Severity Vulnerability
qs-6.3.2.tgz
A querystring parser that supports nesting and arrays, with a depth limit
Library home page: https://registry.npmjs.org/qs/-/qs-6.3.2.tgz
Path to dependency file: /package.json
Path to vulnerable library: /node_modules/codeclimate-test-reporter/node_modules/qs/package.json
Dependency Hierarchy: - next-4.2.3.tgz (Root Library) - glob-promise-3.2.0.tgz - codeclimate-test-reporter-0.5.0.tgz - request-2.79.0.tgz - :x: **qs-6.3.2.tgz** (Vulnerable Library)
qs-6.4.0.tgz
A querystring parser that supports nesting and arrays, with a depth limit
Library home page: https://registry.npmjs.org/qs/-/qs-6.4.0.tgz
Path to dependency file: /package.json
Path to vulnerable library: /package.json,/node_modules/qs/package.json
Dependency Hierarchy: - body-parser-1.17.2.tgz (Root Library) - :x: **qs-6.4.0.tgz** (Vulnerable Library)
qs-6.5.0.tgz
A querystring parser that supports nesting and arrays, with a depth limit
Library home page: https://registry.npmjs.org/qs/-/qs-6.5.0.tgz
Path to dependency file: /package.json
Path to vulnerable library: /node_modules/express/node_modules/qs/package.json
Dependency Hierarchy: - express-4.15.4.tgz (Root Library) - :x: **qs-6.5.0.tgz** (Vulnerable Library)
Found in HEAD commit: 3c5fb7d3f2932ae2023353faafd51bf99b953a5f
Found in base branch: master
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).
Publish Date: 2022-11-26
URL: CVE-2022-24999
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.Type: Upgrade version
Origin: https://www.cve.org/CVERecord?id=CVE-2022-24999
Release Date: 2022-11-26
Fix Resolution (qs): 6.3.3
Direct dependency fix Resolution (next): 4.3.0-canary.1
Fix Resolution (qs): 6.3.3
Direct dependency fix Resolution (body-parser): 1.18.0
Fix Resolution (qs): 6.3.3
Direct dependency fix Resolution (express): 4.15.5
Step up your Open Source Security Game with Mend here