Denial-of-Service Memory Exhaustion in qs
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.
01
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2014-7191US | medium5.0 | — | ||
The qs module before 1.0.0 in Node.js does not call the compact function for array data, which allows remote attackers to cause a denial of service (memory consumption) by using a… | ||||
02
references
External citations — patches, advisories, analysis.
- http://secunia.com/advisories/60026WEB
- http://secunia.com/advisories/62170WEB
- http://www-01.ibm.com/support/docview.wss?uid=swg21685987WEB
- http://www-01.ibm.com/support/docview.wss?uid=swg21687263WEB
- http://www-01.ibm.com/support/docview.wss?uid=swg21687928WEB
- https://access.redhat.com/errata/RHSA-2016:1380WEB
- https://exchange.xforce.ibmcloud.com/vulnerabilities/96729WEB
- https://github.com/advisories/GHSA-jjv7-qpx3-h62qADVISORY
scry
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan