CVE-2017-1000048

Affected version of qs are vulnerable to Prototype Pollution because it is possible to bypass the protection. The qs.parse function fails to properly prevent an object's prototype to be altered when parsing arbitrary input. Input containing [ or ] may bypass the prototype pollution protection and alter the Object prototype. This allows attackers to override properties that will exist in all objects, which may lead to Denial of Service or Remote Code Execution in specific circumstances.

The application does not adequately validate input before processing it, allowing unexpected values to reach sensitive code paths. Typical impact: varies by context: data corruption, logic bypass, or denial of service.

CVE-2017-1000048 has a CVSS score of 7.5 (High). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (6.0.4, 6.1.2, 6.2.3, 6.3.2); upgrading removes the vulnerable code path.

Kodem intelligence

Upgrade to 6.0.4, 6.1.2, 6.2.3, 6.3.2 or later.

1. What is CVE-2017-1000048? CVE-2017-1000048 is a high-severity improper input validation vulnerability in qs (npm), affecting versions < 6.0.4. It is fixed in 6.0.4, 6.1.2, 6.2.3, 6.3.2. The application does not adequately validate input before processing it, allowing unexpected values to reach sensitive code paths.
2. How severe is CVE-2017-1000048? CVE-2017-1000048 has a CVSS score of 7.5 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of qs are affected by CVE-2017-1000048? qs (npm) versions < 6.0.4 is affected.
4. Is there a fix for CVE-2017-1000048? Yes. CVE-2017-1000048 is fixed in 6.0.4, 6.1.2, 6.2.3, 6.3.2. Upgrade to this version or later.
5. Is CVE-2017-1000048 exploitable, and should I be worried? Whether CVE-2017-1000048 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2017-1000048 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2017-1000048?
   • Upgrade qs to 6.0.4 or later
   • Upgrade qs to 6.1.2 or later
   • Upgrade qs to 6.2.3 or later
   • Upgrade qs to 6.3.2 or later