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

• Grunt-karma vulnerable to prototype pollution - CVE-2022-37602
• thlorenz browserify-shim vulnerable to prototype pollution - browserify-shim - CVE-2022-37621
• thlorenz browserify-shim vulnerable to prototype pollution - CVE-2022-37617
• Parse Server is vulnerable to Prototype Pollution via Cloud Code Webhooks - CVE-2022-41879

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