CVE-2022-24999

HIGHNVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 16% (96th percentile of EPSS-scored CVEs). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Elevated
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 16%CVSS: 7.5Exploit: Elevated riskExposed services: Not assessed

A fix is available — apply it.

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: [email protected]" in its release description, is not vulnerable).

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
65
EG Risk 65/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity75% × 45%
Exploitation40% × 40%
Automatability100% × 15%
CISA SSVC: Track at low or medium mission impact; Attend at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
16%
EPSS %ILE
96th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

November 26, 2022

Last Modified

April 29, 2025

References (10)

Vendor Advisories for CVE-2022-24999(12)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(11)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntunode-qs (6.9.1+ds-1ubuntu0.1~esm1) @ focal2026-05-25ubuntu
redhatopenshift-service-mesh/prometheus-rhel8:2.2.7-72023-06-15redhat
redhatodf4/mcg-core-rhel8:v4.12.3-42023-05-23redhat
redhatnodejs:14-8060020230306170237.ad008a3a2023-04-12redhat
redhatnodejs:14-8040020230306170312.522a0ee42023-03-30redhat
redhatrhmtc/openshift-migration-ui-rhel8:v1.7.8-52023-03-23redhat
redhatopenshift-logging/logging-view-plugin-rhel8:v5.6.3-52023-03-08redhat
redhatopenshift-logging/logging-view-plugin-rhel8:v5.5.8-32023-03-08redhat
redhatmta/mta-ui-rhel8:6.0.1-102023-02-28redhat
redhatrh-nodejs14-nodejs-nodemon-0:2.0.20-2.el72023-02-06redhat
redhatnodejs:14-8070020221212161539.bd1311ed2023-01-09redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(6 across 6 ecosystems)
Debian:10(1)
PackageVulnerable rangeFix by version rangeDependents
node-qs6.5.2-1
  • every version up to 6.5.2-1+deb10u1: fixed in 6.5.2-1+deb10u1
—
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
node-qs6.9.4+ds-1
  • every version up to 6.9.4+ds-1+deb11u1: fixed in 6.9.4+ds-1+deb11u1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
node-qs—
  • every version up to 6.10.3+ds+~6.9.7-1: fixed in 6.10.3+ds+~6.9.7-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
node-qs—
  • every version up to 6.10.3+ds+~6.9.7-1: fixed in 6.10.3+ds+~6.9.7-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
node-qs—
  • every version up to 6.10.3+ds+~6.9.7-1: fixed in 6.10.3+ds+~6.9.7-1
—
npm(1)
PackageVulnerable rangeFix by version rangeDependents
qs—
  • 6.10.0 up to 6.10.3: fixed in 6.10.3
  • 6.9.0 up to 6.9.7: fixed in 6.9.7
  • 6.8.0 up to 6.8.3: fixed in 6.8.3
  • 6.7.0 up to 6.7.3: fixed in 6.7.3
  • 6.6.0 up to 6.6.1: fixed in 6.6.1
  • 6.5.0 up to 6.5.3: fixed in 6.5.3
  • 6.4.0 up to 6.4.1: fixed in 6.4.1
  • 6.3.0 up to 6.3.3: fixed in 6.3.3
  • every version up to 6.2.4: fixed in 6.2.4
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(1)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 8× in last 7d / 24× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 157 total refreshes for this CVE.

  1. 2026-10-09 20:04 UTCEPSS rescore
  2. 2026-10-08 16:40 UTCEPSS rescore
  3. 2026-10-07 23:45 UTCEPSS rescore
  4. 2026-10-06 15:14 UTCEPSS rescore
  5. 2026-10-05 17:40 UTCEPSS rescore
  6. 2026-10-04 23:19 UTCEPSS rescore
  7. 2026-10-03 14:23 UTCEPSS rescore
  8. 2026-10-03 14:22 UTCEPSS rescore
  9. 2026-09-30 15:51 UTCEG score recompute
  10. 2026-09-30 15:00 UTCEPSS rescore
  11. 2026-09-29 15:15 UTCEPSS rescore
  12. 2026-09-27 13:41 UTCEPSS rescore
  13. 2026-09-26 00:22 UTCEPSS rescore
  14. 2026-09-24 14:00 UTCEPSS rescore
  15. 2026-09-24 05:15 UTCOSV refresh
  16. 2026-09-23 13:45 UTCEPSS rescore
  17. 2026-09-20 20:13 UTCEPSS rescore
  18. 2026-09-17 19:23 UTCEPSS rescore
  19. 2026-09-16 14:05 UTCEPSS rescore
  20. 2026-09-15 03:06 UTCEPSS rescore
  21. 2026-09-13 16:43 UTCEPSS rescore
  22. 2026-09-12 14:57 UTCEPSS rescore
  23. 2026-09-11 14:49 UTCEPSS rescore
  24. 2026-09-11 09:33 UTCEPSS rescore
  25. 2026-09-08 21:57 UTCEPSS rescore
Show 75 more
  1. 2026-09-07 15:58 UTCEPSS rescore
  2. 2026-09-06 13:45 UTCEPSS rescore
  3. 2026-09-05 15:25 UTCEPSS rescore
  4. 2026-09-04 22:29 UTCOSV refresh
  5. 2026-09-04 13:57 UTCEPSS rescore
  6. 2026-09-04 05:04 UTCEPSS rescore
  7. 2026-09-02 14:09 UTCEPSS rescore
  8. 2026-09-01 13:51 UTCEPSS rescore
  9. 2026-08-30 19:14 UTCEPSS rescore
  10. 2026-08-30 01:19 UTCEPSS rescore
  11. 2026-08-28 21:38 UTCEPSS rescore
  12. 2026-08-27 14:22 UTCEPSS rescore
  13. 2026-08-26 14:43 UTCEPSS rescore
  14. 2026-08-25 13:46 UTCEPSS rescore
  15. 2026-08-25 13:46 UTCEPSS rescore
  16. 2026-08-24 14:13 UTCEPSS rescore
  17. 2026-08-21 23:46 UTCEPSS rescore
  18. 2026-08-20 22:52 UTCEPSS rescore
  19. 2026-08-19 17:01 UTCEPSS rescore
  20. 2026-08-18 13:45 UTCEPSS rescore
  21. 2026-08-18 09:52 UTCOSV refresh
  22. 2026-08-16 14:53 UTCEPSS rescore
  23. 2026-08-16 02:11 UTCEPSS rescore
  24. 2026-08-15 01:27 UTCEPSS rescore
  25. 2026-08-13 21:57 UTCEPSS rescore
  26. 2026-08-12 13:48 UTCEPSS rescore
  27. 2026-08-09 13:44 UTCEPSS rescore
  28. 2026-08-08 16:34 UTCEPSS rescore
  29. 2026-08-07 16:24 UTCEPSS rescore
  30. 2026-08-06 13:44 UTCEPSS rescore
  31. 2026-08-05 19:15 UTCEPSS rescore
  32. 2026-08-04 10:34 UTCEPSS rescore
  33. 2026-08-03 04:57 UTCOSV refresh
  34. 2026-08-01 04:13 UTCEPSS rescore
  35. 2026-07-30 16:25 UTCEPSS rescore
  36. 2026-07-30 01:28 UTCEPSS rescore
  37. 2026-07-28 15:33 UTCEPSS rescore
  38. 2026-07-26 14:52 UTCEPSS rescore
  39. 2026-07-26 14:52 UTCEPSS rescore
  40. 2026-07-25 14:15 UTCEPSS rescore
  41. 2026-07-24 14:15 UTCEPSS rescore
  42. 2026-07-23 14:16 UTCEPSS rescore
  43. 2026-07-23 02:09 UTCEG score recompute
  44. 2026-07-22 22:56 UTCEG score recompute
  45. 2026-07-22 14:06 UTCEPSS rescore
  46. 2026-07-22 14:06 UTCEPSS rescore
  47. 2026-07-21 15:22 UTCEPSS rescore
  48. 2026-07-21 15:22 UTCEPSS rescore
  49. 2026-07-20 17:05 UTCEPSS rescore
  50. 2026-07-19 02:27 UTCEPSS rescore
  51. 2026-07-18 10:02 UTCEPSS rescore
  52. 2026-07-18 10:02 UTCEPSS rescore
  53. 2026-07-16 17:00 UTCEPSS rescore
  54. 2026-07-16 17:00 UTCEPSS rescore
  55. 2026-07-16 14:19 UTCOSV refresh
  56. 2026-07-15 16:56 UTCEPSS rescore
  57. 2026-07-15 16:56 UTCEPSS rescore
  58. 2026-07-15 01:58 UTCEPSS rescore
  59. 2026-07-15 01:58 UTCEPSS rescore
  60. 2026-07-13 22:27 UTCEPSS rescore
  61. 2026-07-12 05:44 UTCEPSS rescore
  62. 2026-07-11 08:25 UTCEPSS rescore
  63. 2026-07-09 19:07 UTCEPSS rescore
  64. 2026-07-08 15:12 UTCEPSS rescore
  65. 2026-07-07 13:44 UTCEPSS rescore
  66. 2026-07-05 02:28 UTCEPSS rescore
  67. 2026-07-04 06:29 UTCEPSS rescore
  68. 2026-07-04 06:29 UTCEPSS rescore
  69. 2026-07-01 15:04 UTCEPSS rescore
  70. 2026-06-29 14:04 UTCEPSS rescore
  71. 2026-06-29 14:04 UTCEPSS rescore
  72. 2026-06-28 14:06 UTCEPSS rescore
  73. 2026-06-28 12:49 UTCOSV refresh
  74. 2026-06-28 04:54 UTCEPSS rescore
  75. 2026-06-28 04:54 UTCEPSS rescore

Publicly available exploits

(2 references)

Working exploit code is in the public domain (2 GitHub PoCs). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • GitHub PoC9pings/CVE-2022-24999
    First seen Apr 18, 2022

    "qs" prototype poisoning vulnerability ( CVE-2022-24999 )

    Open source ↗
  • GitHub PoCn8tz/CVE-2022-24999
    First seen Apr 18, 2022

    "qs" prototype poisoning vulnerability ( CVE-2022-24999 )

    Open source ↗

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2022-24999?
CVE-2022-24999 is a high vulnerability published on November 26, 2022. 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…
When was CVE-2022-24999 disclosed?
CVE-2022-24999 was first published on November 26, 2022, with the most recent update on April 29, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2022-24999 actively exploited?
CVE-2022-24999 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 16% probability of exploitation in the next 30 days (96th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2022-24999?
CVE-2022-24999 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2022-24999?
A fix for CVE-2022-24999 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2022-24999 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2022-24999

Explore →

Is Your Infrastructure Affected by CVE-2022-24999?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs