GHSA-jjv7-qpx3-h62q CVE-2014-7191
Denial-of-Service Memory Exhaustion in qs
High
npm
- Severity
- High
- The publisher's own rating, not a CVSS score
- Exploit chance (EPSS)
- 8.31%
- Chance of exploitation in the next 30 days. Higher than 94.93% of scored vulnerabilities.
- Known exploited
- No
- Not in CISA's catalog
- Weakness
- CWE-400 Uncontrolled Resource Consumption
- Fix
1.0.0- Upgrade qs to this version or later
Description
Versions prior to 1.0 of qs are affected by a denial of service condition. This condition is triggered by parsing a crafted string that deserializes into very large sparse arrays, resulting in the process running out of memory and eventually crashing.
Recommendation
Update to version 1.0.0 or later.
Affected versions
npm
| Package | Vulnerable | Fixed in |
|---|---|---|
| qs | < 1.0.0 |
1.0.0 |
How to fix
Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.
qs npm → 1.0.0
- npm
npm install qs@1.0.0- yarn
yarn add qs@1.0.0- pnpm
pnpm add qs@1.0.0
Weakness
CWE-400: Uncontrolled Resource Consumption
The product does not properly control the allocation and maintenance of a limited resource.
How to prevent it
- Architecture and Design: Design throttling mechanisms into the system architecture. The best protection is to limit the amount of resources that an unauthorized user can cause to be expended. A strong authentication and access control model will help prevent such attacks from occurring in the first place. The login application should be protected against DoS attacks as much as possible. Limiting the database access, perhaps by caching result sets, can help minimize the resources expended. To further limit the potential for a DoS attack, consider tracking the rate of requests received from users and blocking requests that exceed a defined rate threshold.
- Architecture and Design: Mitigation of resource exhaustion attacks requires that the target system either: recognizes the attack and denies that user further access for a given amount of time, or uniformly throttles all requests in order to make it more difficult to consume resources more quickly than they can again be freed. The first of these solutions is an issue in itself though, since it may allow attackers to prevent the use of the system by a particular valid user. If the attacker impersonates the valid user, they may be able to prevent the user from accessing the server in question. The second solution is simply difficult to effectively institute -- and even when properly done, it does not provide a full solution. It simply makes the attack require more resources on the part of the attacker.
- Architecture and Design: Ensure that protocols have specific limits of scale placed on them.
- Implementation: Ensure that all failures in resource allocation place the system into a safe posture.
References
Advisories
Packages
Other links
- github.com/visionmedia/node-querystring/issues/104
- github.com/raymondfeng/node-querystring/commit/43a604b7847e56bba49d0ce3e222fe89…
- access.redhat.com/errata/RHSA-2016:1380
- exchange.xforce.ibmcloud.com/vulnerabilities/96729
- npmjs.com/advisories/29
- secunia.com/advisories/60026
- secunia.com/advisories/62170
- www-01.ibm.com/support/docview.wss
- www-01.ibm.com/support/docview.wss
- www-01.ibm.com/support/docview.wss
Timeline
- Published
- Last updated by the source
- Latest EPSS score
Related advisories
| Advisory | Severity | Why it's related |
|---|---|---|
| GHSA-6pq8-jhm2-2vcw qs : qs.stringify with arrayFormat 'comma' throws an uncaught TypeError on array elements carrying a non-callable own toString (DoS) | Medium | Also affects qs |
| GHSA-x5fp-wj9c-mxmx qs array-limit bypass via bracket-key comma parsing | Medium | Also affects qs |
| GHSA-4mjr-xmp4-gh2g qs: Denial of Service via Attacker Controlled isBuffer | Medium | Also affects qs |
| GHSA-q8mj-m7cp-5q26 qs has a remotely triggerable DoS: qs.stringify crashes with TypeError on null/undefined entries in comma-format arrays when encodeValuesOnly is set | Medium | Also affects qs |
| GHSA-w7fw-mjwx-w883 qs's arrayLimit bypass in comma parsing allows denial of service | Medium | Also affects qs |
| GHSA-6rw7-vpxm-498p qs's arrayLimit bypass in its bracket notation allows DoS via memory exhaustion | Medium | Also affects qs |
| GHSA-hrpp-h998-j3pp qs vulnerable to Prototype Pollution | High | Also affects qs |
| GHSA-gqgv-6jq5-jjj9 Prototype Pollution Protection Bypass in qs | High | Also affects qs |
MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.
Check your repos with MergeHarbor