Skip to content
KitploitKITPLOIT
ToolsExploitsBlog
Log in
Submit
ToolsExploitsBlog
Submit

Hacking, PenTest, and Cybersecurity Tools for Your Security Arsenal!

Kitploit is a directory of hacking, cybersecurity, and pentesting tools. Discover the latest project updates to find vulnerabilities, analyze systems, automate testing, and strengthen your security.

FeedsContactPrivacy© 2026 Kitploit

Tool Directory

Categories

View all categories
Loading categories
CVE-2022-24999 — "qs" prototype poisoning vulnerability ( CVE-2022-24999 ) | Kitploit
Tools/GitHubGitHub/9pings/cve-2022-24999
Payload GenerationVulnerability AnalysisExploitationWeb Application ExploitationWeb Security
GitHub9pings/cve-2022-24999

CVE-2022-24999

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

View Repository
83171 year agoNot yet reviewed
Share

CVE-2022-24999

This repository contain exploits samples of the vulnerability we found in the JS library "qs" in december 2021.

  • This vulnerability was fixed in express v4.17.3 & qs v6.10.3 v6.9.7, v6.8.3, v6.7.3, v6.6.1, v6.5.3, v6.4.1, v6.3.3, and v6.2.4.

qs Array & String Bombs

Vulnerable versions of "qs" allow creating "proto" properties on the output JS objects.

By setting an Array in the “__ proto__” property, we’ve been able to create “array-like” objects.

As the resulting Objects inherit the “Array” prototype, they expose the native Array functions.

But as they still are Objects, “qs” allow setting the “length” property on them.

As an example, the following payload will create this kind of “evil” array :

categories[_proto__]&categories[_proto__]&categories[length]=100000000

Thus, setting an unreasonable "length" value on them will freeze the node process as soon as it tries to convert them to string values or by calling most native Array functions.

This exposes any Node application using a vulnerable version of "qs", with the default Express configuration and without a strong validation system to applicative DOS attacks.

Here an example logs of the poc in ./express-qs-string-bomb :

Send payload :  someString[_proto__]&someString[_proto__]&someString[length]=100000000
[server] Received params  { someString: Array { length: '100000000' } }
[server] Run someString + 0
[server] someString + 0 : 6.364s
[server] Run someString == "123" 
[server] someString == "123" : 6.387s
[server] just write `Got ${someString}`
[server] just write `Got ${someString}` : 6.397s

Others exploitable behaviors

Our analysis also allowed us to see that other modes of exploitation were possible.

We describe some of them in the ./qs-vulns directory.

Credits

BRAUN Nathanael & BRISSAUD Johan
For EY Security, France

Download Tool

Most Popular

View all →

Discover the most used tools by our community.

  • 1

    OsintHunter

    letox4/osinthunter

    🎯 The ultimate OSINT toolkit: investigation graph, confidence scoring, alias families, map, timeline and reports. 49 modules, 400+ sites, no API keys required.

    795
  • 2

    ghostlock-app

    yukonga/ghostlock-app

    GhostLock One-Tap Execution App (CVE-2026-43499)

    520
  • 3

    ARTEX

    baarai/artex

    LLM multi-agent autonomous penetration testing platform with planner/worker agents, asset and exploration graphs, MITM traffic recording, and vulnerability retesting.

    439
  • 4

    redforge

    cybersecurity91/redforge

    Browser-side red team toolkit with 102 offline tools for recon, payload generation, credential attacks, crypto, encoding and engagement reporting.

    346
  • 5

    looking-glass

    anonghosty/looking-glass

    CSIRT platform that ingests Shadowserver reports into MongoDB and replays them as interactive maps, analysis, findings, advisories and executive dashboards.

    267
  • 6

    CyberStrikeAI

    ed1s0nz/cyberstrikeai

    The system of action for AI-native cybersecurity—where intent becomes governed execution, evidence becomes operational memory, and every operation improves the next.

    264

Explore all tools

Browse our collection of tools

View all tools →