CVE-2022-24999

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).

CVSS v3.0 7.5 HIGH

7.5^/10

CVSS v3.0 : HIGH

V3 Legend

Vector :

Exploitability : 3.9 / Impact : 3.6

Attack Vector NETWORK

Attack Complexity LOW

Privileges Required NONE

User Interaction NONE

Confidentiality Impact NONE

Integrity Impact NONE

Availability Impact HIGH

Scope UNCHANGED

References

Link	Resource
https://github.com/n8tz/CVE-2022-24999	Exploit Third Party Advisory
https://github.com/expressjs/express/releases/tag/4.17.3	Release Notes
https://github.com/ljharb/qs/pull/428	Issue Tracking Patch
https://lists.debian.org/debian-lts-announce/2023/01/msg00039.html	Mailing List Third Party Advisory

Configurations

Configuration 1 (hide)

OR	cpe:2.3:a:qs_project:qs::::::node.js::*
	cpe:2.3:a:qs_project:qs:6.4.0:::::node.js::
	cpe:2.3:a:qs_project:qs::::::node.js::*
	cpe:2.3:a:qs_project:qs:6.6.0:::::node.js::
	cpe:2.3:a:qs_project:qs::::::node.js::*
	cpe:2.3:a:qs_project:qs::::::node.js::*
	cpe:2.3:a:qs_project:qs::::::node.js::*
	cpe:2.3:a:qs_project:qs::::::node.js::*
	cpe:2.3:a:qs_project:qs::::::node.js::*

Configuration 2 (hide)

cpe:2.3:a:openjsf:express:*:*:*:*:*:node.js:*:*

Configuration 3 (hide)

cpe:2.3:o:debian:debian_linux:10.0:*:*:*:*:*:*:*

Information

Published : 2022-11-26 14:15

Updated : 2023-02-16 11:19

NVD link : CVE-2022-24999

Mitre link : CVE-2022-24999

JSON object : View

CWE

CWE-1321

Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution')

Products Affected

debian

debian_linux

openjsf

express

qs_project

{"cve": {"data_type": "CVE", "references": {"reference_data": [{"url": "https://github.com/n8tz/CVE-2022-24999", "name": "https://github.com/n8tz/CVE-2022-24999", "tags": ["Exploit", "Third Party Advisory"], "refsource": "MISC"}, {"url": "https://github.com/expressjs/express/releases/tag/4.17.3", "name": "https://github.com/expressjs/express/releases/tag/4.17.3", "tags": ["Release Notes"], "refsource": "CONFIRM"}, {"url": "https://github.com/ljharb/qs/pull/428", "name": "https://github.com/ljharb/qs/pull/428", "tags": ["Issue Tracking", "Patch"], "refsource": "CONFIRM"}, {"url": "https://lists.debian.org/debian-lts-announce/2023/01/msg00039.html", "name": "[debian-lts-announce] 20230130 [SECURITY] [DLA 3299-1] node-qs security update", "tags": ["Mailing List", "Third Party Advisory"], "refsource": "MLIST"}]}, "data_format": "MITRE", "description": {"description_data": [{"lang": "en", "value": "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)."}]}, "problemtype": {"problemtype_data": [{"description": [{"lang": "en", "value": "CWE-1321"}]}]}, "data_version": "4.0", "CVE_data_meta": {"ID": "CVE-2022-24999", "ASSIGNER": "cve@mitre.org"}}, "impact": {"baseMetricV3": {"cvssV3": {"scope": "UNCHANGED", "version": "3.1", "baseScore": 7.5, "attackVector": "NETWORK", "baseSeverity": "HIGH", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H", "integrityImpact": "NONE", "userInteraction": "NONE", "attackComplexity": "LOW", "availabilityImpact": "HIGH", "privilegesRequired": "NONE", "confidentialityImpact": "NONE"}, "impactScore": 3.6, "exploitabilityScore": 3.9}}, "publishedDate": "2022-11-26T22:15Z", "configurations": {"nodes": [{"children": [], "operator": "OR", "cpe_match": [{"cpe23Uri": "cpe:2.3:a:qs_project:qs:*:*:*:*:*:node.js:*:*", "cpe_name": [], "vulnerable": true, "versionEndExcluding": "6.3.3", "versionStartIncluding": "6.3.0"}, {"cpe23Uri": "cpe:2.3:a:qs_project:qs:6.4.0:*:*:*:*:node.js:*:*", "cpe_name": [], "vulnerable": true}, {"cpe23Uri": "cpe:2.3:a:qs_project:qs:*:*:*:*:*:node.js:*:*", "cpe_name": [], "vulnerable": true, "versionEndExcluding": "6.5.3", "versionStartIncluding": "6.5.0"}, {"cpe23Uri": "cpe:2.3:a:qs_project:qs:6.6.0:*:*:*:*:node.js:*:*", "cpe_name": [], "vulnerable": true}, {"cpe23Uri": "cpe:2.3:a:qs_project:qs:*:*:*:*:*:node.js:*:*", "cpe_name": [], "vulnerable": true, "versionEndExcluding": "6.7.3", "versionStartIncluding": "6.7.0"}, {"cpe23Uri": "cpe:2.3:a:qs_project:qs:*:*:*:*:*:node.js:*:*", "cpe_name": [], "vulnerable": true, "versionEndExcluding": "6.8.3", "versionStartIncluding": "6.8.0"}, {"cpe23Uri": "cpe:2.3:a:qs_project:qs:*:*:*:*:*:node.js:*:*", "cpe_name": [], "vulnerable": true, "versionEndExcluding": "6.9.7", "versionStartIncluding": "6.9.0"}, {"cpe23Uri": "cpe:2.3:a:qs_project:qs:*:*:*:*:*:node.js:*:*", "cpe_name": [], "vulnerable": true, "versionEndExcluding": "6.10.3", "versionStartIncluding": "6.10.0"}, {"cpe23Uri": "cpe:2.3:a:qs_project:qs:*:*:*:*:*:node.js:*:*", "cpe_name": [], "vulnerable": true, "versionEndExcluding": "6.2.4"}]}, {"children": [], "operator": "OR", "cpe_match": [{"cpe23Uri": "cpe:2.3:a:openjsf:express:*:*:*:*:*:node.js:*:*", "cpe_name": [], "vulnerable": true, "versionEndExcluding": "4.17.3"}]}, {"children": [], "operator": "OR", "cpe_match": [{"cpe23Uri": "cpe:2.3:o:debian:debian_linux:10.0:*:*:*:*:*:*:*", "cpe_name": [], "vulnerable": true}]}], "CVE_data_version": "4.0"}, "lastModifiedDate": "2023-02-16T19:19Z"}

7.5 /10