CVE-2022-24999

Exp

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

Published: 2022-11-26 Last update: 2025-04-29 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2022-24999 is rated High Exploit Risk (73.9/100): CVSS High severity, with medium exploitation likelihood (EPSS 1.54%). 1 public exploit reference(s) are indexed (Exploit-DB). Public exploits are available—assess exposure, apply mitigations, and prioritize patching.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Public exploit references (Exploit-DB) for CVE-2022-24999

EDB-ID Source Kind Published Link
— nvd_ref exploit_tag Exploit-DB ↗

Exploit prediction scoring system (EPSS) score for CVE-2022-24999

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-05-03 1.14% 1.54% +0.40%
2 2026-04-21 1.54% 1.14% -0.40%
3 2026-04-09 — 1.54% —

Full EPSS history (85 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2022-24999

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
7.5 3.1 HIGH
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 3.9 3.6 [email protected]
7.5 3.1 HIGH
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 3.9 3.6 134c704f-9b21-4f2e-91b3-4a467353bcc0

Weakness enumeration for CVE-2022-24999

GitHub Security Advisory for CVE-2022-24999

GHSA-hrpp-h998-j3pp · Severity: high · Ecosystem: npm — qs vulnerable to Prototype Pollution

OS Trackers for CVE-2022-24999

vendor priority summary link
debian not yet assigned CVE-2022-24999 not yet assigned priority: Debian including 1 source packages (node-qs), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5. https://security-tracker.debian.org/tracker/CVE-2022-24999
redhat medium — https://access.redhat.com/security/cve/CVE-2022-24999
ubuntu medium CVE-2022-24999 medium priority: Ubuntu including 2 source packages (node-express, node-qs), 21 status rows across 12 suites (bionic, focal, jammy, kinetic, lunar, mantic, noble, oracular, plucky, trusty, upstream, xenial): not-affected 13, ignored 4, needs-triage 2, released 2. https://ubuntu.com/security/CVE-2022-24999

Affected software / configurations for CVE-2022-24999

Vendor Product Version Raw CPE
qs_project qs < 6.2.4 cpe:2.3:a:qs_project:qs:*:*:*:*:*:node.js:*:*
qs_project qs >= 6.3.0, < 6.3.3 cpe:2.3:a:qs_project:qs:*:*:*:*:*:node.js:*:*
qs_project qs >= 6.5.0, < 6.5.3 cpe:2.3:a:qs_project:qs:*:*:*:*:*:node.js:*:*
qs_project qs >= 6.7.0, < 6.7.3 cpe:2.3:a:qs_project:qs:*:*:*:*:*:node.js:*:*
qs_project qs >= 6.8.0, < 6.8.3 cpe:2.3:a:qs_project:qs:*:*:*:*:*:node.js:*:*
qs_project qs >= 6.9.0, < 6.9.7 cpe:2.3:a:qs_project:qs:*:*:*:*:*:node.js:*:*
qs_project qs >= 6.10.0, < 6.10.3 cpe:2.3:a:qs_project:qs:*:*:*:*:*:node.js:*:*
qs_project qs 6.4.0 cpe:2.3:a:qs_project:qs:6.4.0:*:*:*:*:node.js:*:*
qs_project qs 6.6.0 cpe:2.3:a:qs_project:qs:6.6.0:*:*:*:*:node.js:*:*
openjsf express < 4.17.3 cpe:2.3:a:openjsf:express:*:*:*:*:*:node.js:*:*
debian debian_linux 10.0 cpe:2.3:o:debian:debian_linux:10.0:*:*:*:*:*:*:*

References for CVE-2022-24999

cvelogic Threat Intelligence