Description
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).
Remediation
References
https://github.com/expressjs/express/releases/tag/4.17.3
https://github.com/ljharb/qs/pull/428
https://github.com/n8tz/CVE-2022-24999
https://lists.debian.org/debian-lts-announce/2023/01/msg00039.html
https://security.netapp.com/advisory/ntap-20230908-0005/
Related Vulnerabilities
CVE-2017-8439 Vulnerability in npm package kibana
CVE-2021-32855 Vulnerability in npm package vditor
CVE-2022-35961 Vulnerability in npm package @openzeppelin/contracts-upgradeable
CVE-2020-14968 Vulnerability in maven package org.webjars.bowergithub.kjur:jsrsasign
CVE-2022-0272 Vulnerability in maven package io.gitlab.arturbosch.detekt:detekt-core