qs vulnerable to Prototype Pollution

Description

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.

Recommendation

Update the qs package to the latest compatible version. Followings are version details:

• Affected version(s): **< 6.2.4

  >= 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.10.0, < 6.10.3**

• Patched version(s): **6.2.4

  6.3.3

  6.4.1

  6.5.3

  6.6.1

  6.7.3

  6.8.3

  6.9.7

  6.10.3**

References

• GHSA-hrpp-h998-j3pp
• lists.debian.org
• security.netapp.com
• CVE-2022-24999
• CWE-1321
• CAPEC-310
• OWASP 2021-A6

Related Issues

• steal vulnerable to Prototype Pollution - CVE-2022-37258
• steal vulnerable to Prototype Pollution via alias variable - CVE-2022-37265
• steal vulnerable to Prototype Pollution via key variable in babel.js - CVE-2022-37266
• steal vulnerable to Prototype Pollution via requestedVersion variable - CVE-2022-37257

You might also like:

How to Secure your NodeJs Express Javascript Application - part 1

How to Secure your NodeJs Express Javascript Application - part 2

10 Secure Coding Best Practices to Follow in Every Project

Tags:

npm

qs