### Summary The `arrayLimit` option in qs does not enforce limits for comma-separated values when `comma: true` is enabled, allowing attacke
위협 신호 · CVSS · EPSS · KEV
이론적 심각도 점수
30일 내 악용 확률 예측
실측 악용 기록 없음
계획된 패치 주기 내 조치(60일 이내)
CVSS 벡터 · 메트릭
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L약점 (CWE)
- CWE-20
부적절한 입력 검증 — 입력값 검증 부족으로 다양한 후속 공격에 노출.
상세 설명
Summary
The arrayLimit option in qs does not enforce limits for comma-separated values when comma: true is enabled, allowing attackers to cause denial-of-service via memory exhaustion. This is a bypass of the array limit enforcement, similar to the bracket notation bypass addressed in GHSA-6rw7-vpxm-498p (CVE-2025-15284).
Details
When the comma option is set to true (not the default, but configurable in applications), qs allows parsing comma-separated strings as arrays (e.g., ?param=a,b,c becomes ['a', 'b', 'c']). However, the limit check for arrayLimit (default: 20) and the optional throwOnLimitExceeded occur after the comma-handling logic in parseArrayValue, enabling a bypass. This permits creation of arbitrarily large arrays from a single parameter, leading to excessive memory allocation.
Vulnerable code (lib/parse.js: lines ~40-50):
1if (val && typeof val === 'string' && options.comma && val.indexOf(',') > -1) { 2 return val.split(','); 3} 4 5if (options.throwOnLimitExceeded && currentArrayLength >= options.arrayLimit) { 6 throw new RangeError('Array limit exceeded. Only ' + options.arrayLimit + ' element' + (options.arrayLimit === 1 ? '' : 's') + ' allowed in an array.'); 7} 8 9return val;The split(',') returns the array immediately, skipping the subsequent limit check. Downstream merging via utils.combine does not prevent allocation, even if it marks overflows for sparse arrays.This discrepancy allows attackers to send a single parameter with millions of commas (e.g., ?param=,,,,,,,,...), allocating massive arrays in memory without triggering limits. It bypasses the intent of arrayLimit, which is enforced correctly for indexed (a[0]=) and bracket (a[]=) notations (the latter fixed in v6.14.1 per GHSA-6rw7-vpxm-498p).
PoC
Test 1 - Basic bypass:
1npm install qs 1const qs = require('qs'); 2 3const payload = 'a=' + ','.repeat(25); // 26 elements after split (bypasses arrayLimit: 5) 4const options = { comma: true, arrayLimit: 5, throwOnLimitExceeded: true }; 5 6try { 7 const result = qs.parse(payload, options); 8 console.log(result.a.length); // Outputs: 26 (bypass successful) 9} catch (e) {10 console.log('Limit enforced:', e.message); // Not thrown11}Configuration:
comma: truearrayLimit: 5throwOnLimitExceeded: true
Expected: Throws "Array limit exceeded" error.
Actual: Parses successfully, creating an array of length 26.
Impact
Denial of Service (DoS) via memory exhaustion.
AI 심층 분석
공격 시나리오 · 재현 가능한 PoC 페이로드 · 즉시 적용 가능한 차단 패치를 한 번에 받아 보세요. 보안 운영팀이 그대로 점검·티켓팅에 쓸 수 있는 형태로 정리해 드립니다.
영향받는 제품·버전
- qs_project qs6.7.0 - 6.14.2other
영향받는 구성 (CPE) 1
- qs_project qs≥ 6.7.0 < 6.14.2cpe:2.3:a:qs_project:qs:*:*:*:*:*:node.js:*:*
참고 자료 2
- https://github.com/ljharb/qs/security/advisories/GHSA-w7fw-mjwx-w883ExploitVendor Advisory
링크 내용 불러오는 중…