CVE-2022-24999: 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…
Noroxi assessment
Priority: Monitor (action score 35/100)
- Public proof-of-concept code exists (GitHub); there is no record of exploitation in the wild.
- Probability of exploitation in the next 30 days: 15.6% (FIRST EPSS); higher than 96.9% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- According to CISA the attack is automatable: targets can be found by mass scanning.
- Fixed version: nodejs (AlmaLinux:8) 1:14.21.1-2.module_el8.7.0+3373+a4c18c43; nodejs-devel (AlmaLinux:8) 1:14.21.1-2.module_el8.7.0+3373+a4c18c43; nodejs-docs (AlmaLinux:8) 1:14.21.1-2.module_el8.7.0+3373+a4c18c43.
Low priority for now. Upgrade to nodejs (AlmaLinux:8) 1:14.21.1-2.module_el8.7.0+3373+a4c18c43; nodejs-devel (AlmaLinux:8) 1:14.21.1-2.module_el8.7.0+3373+a4c18c43; nodejs-docs (AlmaLinux:8) 1:14.21.1-2.module_el8.7.0+3373+a4c18c43 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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).
- Published
- Nov 26, 2022
- Updated
- Jun 17, 2026
- EPSS
- 15.6% · 96th percentile
- CWE
- CWE-1321
Report tools
Action score
35
Low priority for now.
- CVSS
- 30 / 40 · 7.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 5 / 30 · 15.6%
CISA SSVC decision
- Exploitation
- proof of concept
- Automatable
- yes
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- Proof of concept exists, no weaponized module
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| qs project | qs | cpe:2.3:a:qs_project:qs |
| openjsf | express | cpe:2.3:a:openjsf:express |
| debian | debian linux | cpe:2.3:o:debian:debian_linux |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- debian debian linux10.0
- openjsf expressbefore 4.17.3
- qs project qs6.5.0 and later · before 6.5.3
- qs project qs6.7.0 and later · before 6.7.3
- qs project qs6.8.0 and later · before 6.8.3
- qs project qsbefore 6.2.4
- qs project qs6.10.0 and later · before 6.10.3
- qs project qs6.9.0 and later · before 6.9.7
+3 more rows
- qs project qs6.3.0 and later · before 6.3.3
- qs project qs6.4.0
- qs project qs6.6.0
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| AlmaLinux:8 | nodejs | before 1:14.21.1-2.module_el8.7.0+3373+a4c18c43 | 1:14.21.1-2.module_el8.7.0+3373+a4c18c43 |
| AlmaLinux:8 | nodejs-devel | before 1:14.21.1-2.module_el8.7.0+3373+a4c18c43 | 1:14.21.1-2.module_el8.7.0+3373+a4c18c43 |
| AlmaLinux:8 | nodejs-docs | before 1:14.21.1-2.module_el8.7.0+3373+a4c18c43 | 1:14.21.1-2.module_el8.7.0+3373+a4c18c43 |
| AlmaLinux:8 | nodejs-full-i18n | before 1:14.21.1-2.module_el8.7.0+3373+a4c18c43 | 1:14.21.1-2.module_el8.7.0+3373+a4c18c43 |
| AlmaLinux:8 | nodejs-nodemon | before 2.0.20-2.module_el8.7.0+3373+a4c18c43 | 2.0.20-2.module_el8.7.0+3373+a4c18c43 |
| AlmaLinux:8 | nodejs-packaging | before 23-3.module_el8.4.0+2522+3bd42762 | 23-3.module_el8.4.0+2522+3bd42762 |
| AlmaLinux:8 | npm | before 1:6.14.17-1.14.21.1.2.module_el8.7.0+3373+a4c18c43 | 1:6.14.17-1.14.21.1.2.module_el8.7.0+3373+a4c18c43 |
| Debian:10 | node-qs | before 6.5.2-1+deb10u1 | 6.5.2-1+deb10u1 |
| Debian:12 | node-qs | before 6.10.3+ds+~6.9.7-1 | 6.10.3+ds+~6.9.7-1 |
| npm | qs | from 6.10.0 · before 6.10.3 | 6.10.3 |
| npm | qs | from 6.3.0 · before 6.3.3 | 6.3.3 |
| npm | qs | from 6.4.0 · before 6.4.1 | 6.4.1 |
| npm | qs | from 6.5.0 · before 6.5.3 | 6.5.3 |
| npm | qs | from 6.6.0 · before 6.6.1 | 6.6.1 |
| npm | qs | from 6.7.0 · before 6.7.3 | 6.7.3 |
| npm | qs | from 6.8.0 · before 6.8.3 | 6.8.3 |
| npm | qs | from 6.9.0 · before 6.9.7 | 6.9.7 |
| npm | qs | before 6.2.4 | 6.2.4 |
| Red Hat:enterprise_linux:8::appstream | nodejs | before 1:14.21.1-2.module+el8.7.0+17528+a329cd47 | 1:14.21.1-2.module+el8.7.0+17528+a329cd47 |
| Red Hat:enterprise_linux:8::appstream | nodejs-debuginfo | before 1:14.21.1-2.module+el8.7.0+17528+a329cd47 | 1:14.21.1-2.module+el8.7.0+17528+a329cd47 |
| Red Hat:enterprise_linux:8::appstream | nodejs-debugsource | before 1:14.21.1-2.module+el8.7.0+17528+a329cd47 | 1:14.21.1-2.module+el8.7.0+17528+a329cd47 |
| Red Hat:enterprise_linux:8::appstream | nodejs-devel | before 1:14.21.1-2.module+el8.7.0+17528+a329cd47 | 1:14.21.1-2.module+el8.7.0+17528+a329cd47 |
| Red Hat:enterprise_linux:8::appstream | nodejs-docs | before 1:14.21.1-2.module+el8.7.0+17528+a329cd47 | 1:14.21.1-2.module+el8.7.0+17528+a329cd47 |
| Red Hat:enterprise_linux:8::appstream | nodejs-full-i18n | before 1:14.21.1-2.module+el8.7.0+17528+a329cd47 | 1:14.21.1-2.module+el8.7.0+17528+a329cd47 |
+31
Same product
qs project: all recordsOther highest-scoring records for the same primary product.
- CVE-2017-1000048the web framework using ljharb's qs module older than v6.3.2, v6.2.3, v6.1.2, and v6.0.4 is vulnerable to a DoS.31Monitor
- CVE-2014-10064The qs module before 1.0.0 does not have an option or default for specifying object depth and when parsing a string representing a deeply…30Monitor
- CVE-2026-2391qs's arrayLimit bypass in comma parsing allows denial of service25Monitor
Published before and after this one in the same product
- Later →CVE-2025-15284Dec 29, 2025 · arrayLimit bypass in bracket notation allows DoS via memory exhaustion25Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| almalinux:nodejs | 1:14.21.1-2.module_el8.7.0+3373+a4c18c43 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:nodejs-devel | 1:14.21.1-2.module_el8.7.0+3373+a4c18c43 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:nodejs-docs | 1:14.21.1-2.module_el8.7.0+3373+a4c18c43 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:nodejs-full-i18n | 1:14.21.1-2.module_el8.7.0+3373+a4c18c43 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:nodejs-nodemon | 2.0.20-2.module_el8.7.0+3373+a4c18c43 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:nodejs-packaging | 23-3.module_el8.4.0+2522+3bd42762 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:npm | 1:6.14.17-1.14.21.1.2.module_el8.7.0+3373+a4c18c43 · AlmaLinux:8 | Package registry (OSV) |
| debian:node-qs | 6.10.3+ds+~6.9.7-1 · Debian:12 | Package registry (OSV) |
| npm:qs | 6.10.3 | Package registry (OSV) |
| npm:qs | 6.2.4 | Package registry (OSV) |
| npm:qs | 6.3.3 | Package registry (OSV) |
| npm:qs | 6.4.1 | Package registry (OSV) |
| npm:qs | 6.5.3 | Package registry (OSV) |
| npm:qs | 6.6.1 | Package registry (OSV) |
| npm:qs | 6.7.3 | Package registry (OSV) |
| npm:qs | 6.8.3 | Package registry (OSV) |
| npm:qs | 6.9.7 | Package registry (OSV) |
| red hat:nodejs | 1:14.21.1-2.module+el8.7.0+17528+a329cd47 · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| red hat:nodejs-debuginfo | 1:14.21.1-2.module+el8.7.0+17528+a329cd47 · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| red hat:nodejs-debugsource | 1:14.21.1-2.module+el8.7.0+17528+a329cd47 · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| red hat:nodejs-devel | 1:14.21.1-2.module+el8.7.0+17528+a329cd47 · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| red hat:nodejs-docs | 1:14.21.1-2.module+el8.7.0+17528+a329cd47 · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| red hat:nodejs-full-i18n | 1:14.21.1-2.module+el8.7.0+17528+a329cd47 · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| red hat:nodejs-nodemon | 0:2.0.20-2.module+el8.7.0+17528+a329cd47 · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| red hat:nodejs-packaging | 0:23-3.module+el8.3.0+6519+9f98ed83 · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| red hat:npm | 1:6.14.17-1.14.21.1.2.module+el8.7.0+17528+a329cd47 · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| red hat:rh-nodejs14-nodejs | 0:14.21.1-3.el7 · Red Hat:rhel_software_collections:3::el7 | Package registry (OSV) |
| red hat:rh-nodejs14-nodejs-debuginfo | 0:14.21.1-3.el7 · Red Hat:rhel_software_collections:3::el7 | Package registry (OSV) |
| red hat:rh-nodejs14-nodejs-devel | 0:14.21.1-3.el7 · Red Hat:rhel_software_collections:3::el7 | Package registry (OSV) |
| rocky linux:nodejs | 1:14.21.1-2.module+el8.7.0+1116+bd2a84b4 · Rocky Linux:8 | Package registry (OSV) |
+2
Exploit status
Proof of concept available
A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.
Evidence
- Proof-of-concept repository on GitHub ×1
Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.
| Source | Kind | Date |
|---|---|---|
| Proof-of-concept repository on GitHub | stars:8 | 2022-04-18 |
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
- First PoC-223 d
- Published
- TodayNov 16, 2026+1451 d
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Not on record for this CVE: researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-1321 · Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution')CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (3 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.