| Package | Affected versions | Patched versions |
|---|---|---|
| express | < 4.17.3 | 4.17.3 |
| qs | = 6.4.0= 6.6.0≥ 6.10.0, < 6.10.3≥ 6.3.0, < 6.3.3≥ 6.5.0, < 6.5.3≥ 6.7.0, < 6.7.3≥ 6.8.0, < 6.8.3≥ 6.9.0, < 6.9.7< 6.2.4 | 6.10.36.3.36.5.36.7.36.8.36.9.76.2.4 |
| qs | ≥ 6.10.0, < 6.10.3≥ 6.3.0, < 6.3.3≥ 6.4.0, < 6.4.1≥ 6.5.0, < 6.5.3≥ 6.6.0, < 6.6.1≥ 6.7.0, < 6.7.3≥ 6.8.0, < 6.8.3≥ 6.9.0, < 6.9.7< 6.2.4 | 6.10.36.3.36.4.16.5.36.6.16.7.36.8.36.9.76.2.4 |
qs before 6.10.3 allows attackers to cause a Node process hang because an __ proto__ key can be used. In many typical web framework 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.
Running one of these products? Scan your site to see whether it exposes a vulnerable version.
Scan my site free