Skip to content

Prototype Pollution Protection Bypass in qs

High severity GitHub Reviewed Published Apr 30, 2020 to the GitHub Advisory Database • Updated Jan 9, 2023

Package

npm qs (npm)

Affected versions

< 6.0.4
>= 6.1.0, < 6.1.2
>= 6.2.0, < 6.2.3
>= 6.3.0, < 6.3.2

Patched versions

6.0.4
6.1.2
6.2.3
6.3.2

Description

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.

Recommendation

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

References

Reviewed Apr 30, 2020
Published to the GitHub Advisory Database Apr 30, 2020
Last updated Jan 9, 2023

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

EPSS score

0.126%
(48th percentile)

Weaknesses

CVE ID

CVE-2017-1000048

GHSA ID

GHSA-gqgv-6jq5-jjj9

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.