Skip to content

yargs-parser Vulnerable to Prototype Pollution

Moderate severity GitHub Reviewed Published Sep 4, 2020 to the GitHub Advisory Database • Updated Jan 27, 2023

Package

npm yargs-parser (npm)

Affected versions

>= 6.0.0, < 13.1.2
>= 14.0.0, < 15.0.1
<= 5.0.0
>= 16.0.0, < 18.1.1

Patched versions

13.1.2
15.0.1
5.0.1
18.1.1

Description

Affected versions of yargs-parser are vulnerable to prototype pollution. Arguments are not properly sanitized, allowing an attacker to modify the prototype of Object, causing the addition or modification of an existing property that will exist on all objects.
Parsing the argument --foo.__proto__.bar baz' adds a bar property with value baz to all objects. This is only exploitable if attackers have control over the arguments being passed to yargs-parser.

Recommendation

Upgrade to versions 13.1.2, 15.0.1, 18.1.1 or later.

References

Published by the National Vulnerability Database Mar 16, 2020
Reviewed Aug 31, 2020
Published to the GitHub Advisory Database Sep 4, 2020
Last updated Jan 27, 2023

Severity

Moderate

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
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

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.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L

EPSS score

0.044%
(15th percentile)

Weaknesses

CVE ID

CVE-2020-7608

GHSA ID

GHSA-p9pc-299p-vxgp

Source code

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