Skip to content

Prototype Pollution in minimist

Moderate severity GitHub Reviewed Published Apr 3, 2020 to the GitHub Advisory Database • Updated Feb 13, 2024

Package

npm minimist (npm)

Affected versions

< 0.2.1
>= 1.0.0, < 1.2.3

Patched versions

0.2.1
1.2.3

Description

Affected versions of minimist 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 --__proto__.y=Polluted adds a y property with value Polluted to all objects. The argument --__proto__=Polluted raises and uncaught error and crashes the application.
This is exploitable if attackers have control over the arguments being passed to minimist.

Recommendation

Upgrade to versions 0.2.1, 1.2.3 or later.

References

Published by the National Vulnerability Database Mar 11, 2020
Reviewed Apr 3, 2020
Published to the GitHub Advisory Database Apr 3, 2020
Last updated Feb 13, 2024

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
Network
Attack complexity
High
Privileges required
None
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:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L

EPSS score

0.139%
(50th percentile)

Weaknesses

CVE ID

CVE-2020-7598

GHSA ID

GHSA-vh95-rmgr-6w4m

Source code

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