You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Path to vulnerable library: /node_modules/connect-query/node_modules/qs/package.json
Dependency Hierarchy:
firebase-tools-7.1.0.tgz (Root Library)
superstatic-6.0.4.tgz
connect-query-1.0.0.tgz
❌ qs-6.4.0.tgz (Vulnerable Library)
Found in base branch: master
Vulnerability Details
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: [email protected]" in its release description, is not vulnerable).
mend-for-github-combot
changed the title
CVE-2022-24999 (Medium) detected in multiple libraries
CVE-2022-24999 (High) detected in multiple libraries
Nov 30, 2022
CVE-2022-24999 - High Severity Vulnerability
Vulnerable Libraries - qs-6.5.2.tgz, qs-6.7.0.tgz, qs-6.4.0.tgz
qs-6.5.2.tgz
A querystring parser that supports nesting and arrays, with a depth limit
Library home page: https://registry.npmjs.org/qs/-/qs-6.5.2.tgz
Path to dependency file: /package.json
Path to vulnerable library: /node_modules/request/node_modules/qs/package.json
Dependency Hierarchy:
qs-6.7.0.tgz
A querystring parser that supports nesting and arrays, with a depth limit
Library home page: https://registry.npmjs.org/qs/-/qs-6.7.0.tgz
Path to dependency file: /package.json
Path to vulnerable library: /node_modules/qs/package.json
Dependency Hierarchy:
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: /node_modules/connect-query/node_modules/qs/package.json
Dependency Hierarchy:
Found in base branch: master
Vulnerability Details
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: [email protected]" 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:
Suggested Fix
Type: Upgrade version
Origin: https://www.cve.org/CVERecord?id=CVE-2022-24999
Release Date: 2022-11-26
Fix Resolution (qs): 6.5.3
Direct dependency fix Resolution (firebase-tools): 7.1.1
Fix Resolution (qs): 6.5.3
Direct dependency fix Resolution (firebase-tools): 7.1.1
Fix Resolution (qs): 6.5.3
Direct dependency fix Resolution (firebase-tools): 7.1.1
⛑️ Automatic Remediation will be attempted for this issue.
The text was updated successfully, but these errors were encountered: