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).
Metrics
Affected Vendors & Products
References
History
Sun, 08 Sep 2024 18:45:00 +0000
Type | Values Removed | Values Added |
---|---|---|
First Time appeared |
Redhat acm
|
|
CPEs | cpe:/a:redhat:acm:2.6::el8 | |
Vendors & Products |
Redhat acm
|
Mon, 19 Aug 2024 22:15:00 +0000
Type | Values Removed | Values Added |
---|---|---|
CPEs | ||
Vendors & Products |
Redhat acm
|
MITRE
Status: PUBLISHED
Assigner: mitre
Published: 2022-11-26T00:00:00
Updated: 2024-08-03T04:29:01.569Z
Reserved: 2022-02-14T00:00:00
Link: CVE-2022-24999
Vulnrichment
No data.
NVD
Status : Modified
Published: 2022-11-26T22:15:10.153
Modified: 2024-11-21T06:51:31.643
Link: CVE-2022-24999
Redhat