{"answers":{"affected":"2 open source packages ship an affected version, including qs. It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-15284 in the wild and no public exploit code.","fix":"Upgrade qs to 6.14.1 or later.","what":"CVE-2025-15284 is a medium-severity denial of service vulnerability in qs_project:qs, published on 29 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-15284 and fix it if it is affected.\n\nWhat it is: CVE-2025-15284 is a medium-severity denial of service vulnerability in qs_project:qs, published on 29 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-15284 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- qs (npm): affected all versions; fixed in 6.14.1\n- qs (npm): affected all versions; fixed in 6.14.1\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-15284/ (Markdown: https://insights.sbomify.com/CVE-2025-15284/index.md)","id":"CVE-2025-15284","markdown":"https://insights.sbomify.com/CVE-2025-15284/index.md","name":"CVE-2025-15284","record":{"aliases":["AZL-73316","AZL-73319","AZL-73353","AZL-73359","CLEANSTART-2026-BM16290","CLSA-2026-1773274548","CLSA-2026-1776299673","CLSA-2026-1791626635","CLSA-2026-1791806891","CLSA-2026-1792160905","DEBIAN-CVE-2025-15284","ECHO-d529-47d7-7d1b","GHSA-6rw7-vpxm-498p","MINI-2hjr-5wc7-g7x4","MINI-4p8v-g6w4-63hj","MINI-53mj-xjgj-7c68","MINI-5j8v-8jp9-mw2g","MINI-5m3r-m39q-v7jg","MINI-65p2-m2xq-gjv2","MINI-9cwv-g765-fcw6","MINI-9g82-6ghp-7pc5","MINI-c9gj-h97c-9hqm","MINI-g7w3-rhxj-c862","MINI-gqwv-8r9g-8w5c","MINI-hx84-p2g2-85h6","MINI-m5p3-6j3g-4jf4","MINI-m86x-x9mq-fh43","MINI-m8vr-h9h6-wj2x","MINI-mx53-6gx4-hxmj","MINI-qgj5-jhr3-pg47","MINI-rgp7-jgf9-54jg","MINI-v26j-4xp8-852f","ROOT-APP-NPM-CVE-2025-15284","UBUNTU-CVE-2025-15284"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":true,"product_category":"JavaScript query string parser","requires_auth":"none","summary":"Attackers can cause memory exhaustion via bracket notation if parameterLimit is increased, bypassing arrayLimit checks in the qs library.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"harborist","cpe":[{"product":"qs","vendor":"qs_project"}],"cvss":{"score":6.3,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:L","version":"4.0"},"cwes":[{"id":"CWE-20","name":"Improper Input Validation"}],"description":"Improper Input Validation vulnerability in qs (parse modules) allows HTTP DoS.This issue affects qs: \u003c 6.14.1.\n\nSummary\n\nThe arrayLimit option in qs did not enforce limits for bracket notation (a[]=1\u0026a[]=2), only for indexed notation (a[0]=1). This is a consistency bug; arrayLimit should apply uniformly across all array notations.\n\nNote: The default parameterLimit of 1000 effectively mitigates the DoS scenario originally described. With default options, bracket notation cannot produce arrays larger than parameterLimit regardless of arrayLimit, because each a[]=valueconsumes one parameter slot. The severity has been reduced accordingly.\n\nDetails\n\nThe arrayLimit option only checked limits for indexed notation (a[0]=1\u0026a[1]=2) but did not enforce it for bracket notation (a[]=1\u0026a[]=2).\n\nVulnerable code (lib/parse.js:159-162):\n\nif (root === '[]' \u0026\u0026 options.parseArrays) {\n    obj = utils.combine([], leaf);  // No arrayLimit check\n}\n\nWorking code (lib/parse.js:175):\n\nelse if (index \u003c= options.arrayLimit) {  // Limit checked here\n    obj = [];\n    obj[index] = leaf;\n}\n\nThe bracket notation handler at line 159 uses utils.combine([], leaf) without validating against options.arrayLimit, while indexed notation at line 175 checks index \u003c= options.arrayLimit before creating arrays.\n\nPoC\n\nconst qs = require('qs');\nconst result = qs.parse('a[]=1\u0026a[]=2\u0026a[]=3\u0026a[]=4\u0026a[]=5\u0026a[]=6', { arrayLimit: 5 });\nconsole.log(result.a.length);  // Output: 6 (should be max 5)\n\nNote on parameterLimit interaction: The original advisory's \"DoS demonstration\" claimed a length of 10,000, but parameterLimit (default: 1000) caps parsing to 1,000 parameters. With default options, the actual output is 1,000, not 10,000.\n\nImpact\n\nConsistency bug in arrayLimit enforcement. With default parameterLimit, the practical DoS risk is negligible since parameterLimit already caps the total number of parsed parameters (and thus array elements from bracket notation). The risk increases only when parameterLimit is explicitly set to a very high value.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"arrayLimit bypass in bracket notation allows DoS via memory exhaustion","id":"CVE-2025-15284","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"denial_of_service","year":"2025"},"n_packages":2,"n_references":2,"next":{"headline":"SEO Flow by LupsOnline \u003c= 2.2.1 - Unauthenticated Arbitrary Post/Category Modification","id":"CVE-2025-15285"},"packages":[{"ecosystem":"npm","fixed":["6.14.1"],"introduced":["0"],"last_affected":[],"package":"qs","purl":null,"source":"GHSA-6rw7-vpxm-498p"},{"ecosystem":"npm","fixed":["6.14.1"],"introduced":["0"],"last_affected":[],"package":"qs","purl":"pkg:npm/qs","source":"GHSA-6rw7-vpxm-498p"}],"prev":{"headline":"Name Directory \u003c= 1.30.3 - Unauthenticated Stored Cross-Site Scripting via Multiple Parameters","id":"CVE-2025-15283"},"products":["qs_project:qs"],"published":"2025-12-29","related":[{"cvss_score":7.5,"headline":"Denial-of-Service Extended Event Loop Blocking in qs","id":"CVE-2014-10064","kev_date_added":null,"published":"2018-05-31"},{"cvss_score":7.5,"headline":"Prototype Pollution Protection Bypass in qs","id":"CVE-2017-1000048","kev_date_added":null,"published":"2017-07-13"},{"cvss_score":6.3,"headline":"qs's arrayLimit bypass in comma parsing allows denial of service","id":"CVE-2026-2391","kev_date_added":null,"published":"2026-02-12"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-02-10","vendors":["qs_project"]},"summary":"Attackers can cause memory exhaustion via bracket notation if parameterLimit is increased, bypassing arrayLimit checks in the qs library.","url":"https://insights.sbomify.com/CVE-2025-15284/"}