CVE-2022-24999: High severity Qs Project Qs Node.js vulnerability

Published Nov 26, 2022
·
Updated

A flaw was found in the express.js npm package of nodejs:14 module stream. Express.js Express is vulnerable to a denial of service caused by a prototype pollution flaw in qs. By adding or modifying properties of Object.prototype using a proto or constructor payload, a remote attacker can cause a denial of service.

Other sources

Express.js Express is vulnerable to a denial of service, caused by a prototype pollution flaw in qs. By adding or modifying properties of Object.prototype using a proto or constructor payload, a remote attacker could exploit this vulnerability to cause a denial of service condition.

— IBM

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.

— GitHub

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).

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.7" in its release description, is not vulnerable).

— Red Hat

Affected Software

32 affected componentsFixes available
redhat/rh-nodejs14-nodejs<0:14.21.1-3.el7
0:14.21.1-3.el7
redhat/rh-nodejs14-nodejs-nodemon<0:2.0.20-2.el7
0:2.0.20-2.el7
redhat/qs<4.17.3
4.17.3
redhat/qs<6.9.7
6.9.7
redhat/qs<6.8.3
6.8.3
redhat/qs<6.7.3
6.7.3
redhat/qs<6.6.1
6.6.1
redhat/qs<6.5.3
6.5.3
redhat/qs<6.4.1
6.4.1
redhat/qs<6.3.3
6.3.3
redhat/qs<6.2.4
6.2.4
redhat/qs<6.10.3
6.10.3
Qs Project Qs Node.js<6.2.4
Qs Project Qs Node.js>=6.3.0<6.3.3
Qs Project Qs Node.js>=6.5.0<6.5.3
Qs Project Qs Node.js>=6.7.0<6.7.3
Qs Project Qs Node.js>=6.8.0<6.8.3
Qs Project Qs Node.js>=6.9.0<6.9.7
Qs Project Qs Node.js>=6.10.0<6.10.3
Qs Project Qs Node.js=6.4.0
Qs Project Qs Node.js=6.6.0
Openjsf Express Node.js<4.17.3
Debian Debian Linux=10.0
npm/qs<6.2.4
6.2.4
npm/qs>=6.3.0<6.3.3
6.3.3
npm/qs>=6.4.0<6.4.1
6.4.1
npm/qs>=6.5.0<6.5.3
6.5.3
npm/qs>=6.6.0<6.6.1
6.6.1
npm/qs>=6.7.0<6.7.3
6.7.3
npm/qs>=6.8.0<6.8.3
6.8.3
npm/qs>=6.9.0<6.9.7
6.9.7
npm/qs>=6.10.0<6.10.3
6.10.3

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade redhat/rh-nodejs14-nodejs to a version that resolves this vulnerability.

    Fixed in 0:14.21.1-3.el7
  2. Upgrade

    Upgrade redhat/rh-nodejs14-nodejs-nodemon to a version that resolves this vulnerability.

    Fixed in 0:2.0.20-2.el7
  3. Upgrade

    Upgrade npm/qs to a version that resolves this vulnerability.

    Fixed in 6.2.4
  4. Upgrade

    Upgrade npm/qs to a version that resolves this vulnerability.

    Fixed in 6.3.3
  5. Upgrade

    Upgrade npm/qs to a version that resolves this vulnerability.

    Fixed in 6.4.1
  6. Upgrade

    Upgrade npm/qs to a version that resolves this vulnerability.

    Fixed in 6.5.3
  7. Upgrade

    Upgrade npm/qs to a version that resolves this vulnerability.

    Fixed in 6.6.1
  8. Upgrade

    Upgrade npm/qs to a version that resolves this vulnerability.

    Fixed in 6.7.3
  9. Upgrade

    Upgrade npm/qs to a version that resolves this vulnerability.

    Fixed in 6.8.3
  10. Upgrade

    Upgrade npm/qs to a version that resolves this vulnerability.

    Fixed in 6.9.7
  11. Upgrade

    Upgrade npm/qs to a version that resolves this vulnerability.

    Fixed in 6.10.3
  12. Upgrade

    Upgrade redhat/qs to a version that resolves this vulnerability.

    Fixed in 4.17.3
  13. Upgrade

    Upgrade redhat/qs to a version that resolves this vulnerability.

    Fixed in 6.9.7
  14. Upgrade

    Upgrade redhat/qs to a version that resolves this vulnerability.

    Fixed in 6.8.3
  15. Upgrade

    Upgrade redhat/qs to a version that resolves this vulnerability.

    Fixed in 6.7.3
  16. Upgrade

    Upgrade redhat/qs to a version that resolves this vulnerability.

    Fixed in 6.6.1
  17. Upgrade

    Upgrade redhat/qs to a version that resolves this vulnerability.

    Fixed in 6.5.3
  18. Upgrade

    Upgrade redhat/qs to a version that resolves this vulnerability.

    Fixed in 6.4.1
  19. Upgrade

    Upgrade redhat/qs to a version that resolves this vulnerability.

    Fixed in 6.3.3
  20. Upgrade

    Upgrade redhat/qs to a version that resolves this vulnerability.

    Fixed in 6.2.4
  21. Upgrade

    Upgrade redhat/qs to a version that resolves this vulnerability.

    Fixed in 6.10.3
  22. Upgrade

    Upgrade qs to a version that resolves this vulnerability.

    Fixed in 6.10.3
  23. Upgrade

    Upgrade qs to a version that resolves this vulnerability.

    Fixed in 6.9.7
  24. Upgrade

    Upgrade qs to a version that resolves this vulnerability.

    Fixed in 6.8.3
  25. Upgrade

    Upgrade qs to a version that resolves this vulnerability.

    Fixed in 6.7.3
  26. Upgrade

    Upgrade qs to a version that resolves this vulnerability.

    Fixed in 6.6.1
  27. Upgrade

    Upgrade qs to a version that resolves this vulnerability.

    Fixed in 6.5.3
  28. Upgrade

    Upgrade qs to a version that resolves this vulnerability.

    Fixed in 6.4.1
  29. Upgrade

    Upgrade qs to a version that resolves this vulnerability.

    Fixed in 6.3.3
  30. Upgrade

    Upgrade qs to a version that resolves this vulnerability.

    Fixed in 6.2.4
  31. Upgrade

    Upgrade Express to a version that resolves this vulnerability.

    Fixed in 4.17.3

Event History

Nov 26, 2022
CVE Published
via MITRE·12:00 AM
Data Sourced
via MITRE·12:00 AM
Description
Nov 27, 2022
Advisory Published
via GitHub·12:30 AM
Dec 2, 2022
Data Sourced
via Red Hat·02:05 PM
DescriptionSeverityAffected Software
Aug 15, 2025
Data Sourced
via IBM·03:29 PM
DescriptionAffected Software

Parent advisories

This vulnerability appears in the following advisories.

Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is CVE-2022-24999?

CVE-2022-24999 is a vulnerability in Express.js caused by a prototype pollution flaw in the qs library.

2

How severe is CVE-2022-24999?

CVE-2022-24999 has a severity rating of high, with a severity value of 7.

3

How does CVE-2022-24999 affect Express.js applications?

CVE-2022-24999 allows an unauthenticated remote attacker to cause a denial of service by hanging the Node process for an Express application.

4

Which versions of Express.js are affected by CVE-2022-24999?

Versions of Express.js before 4.17.3 are affected by CVE-2022-24999.

5

How can I fix CVE-2022-24999?

To fix CVE-2022-24999, update Express.js to version 4.17.3 or newer.

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203