Skip to content

Prototype pollution in object-path

High severity GitHub Reviewed Published Oct 19, 2020 in mariocasciaro/object-path • Updated Nov 29, 2023

Package

npm object-path (npm)

Affected versions

< 0.11.5

Patched versions

0.11.5

Description

Impact

A prototype pollution vulnerability has been found in object-path <= 0.11.4 affecting the set() method. The vulnerability is limited to the includeInheritedProps mode (if version >= 0.11.0 is used), which has to be explicitly enabled by creating a new instance of object-path and setting the option includeInheritedProps: true, or by using the default withInheritedProps instance. The default operating mode is not affected by the vulnerability if version >= 0.11.0 is used. Any usage of set() in versions < 0.11.0 is vulnerable.

Patches

Upgrade to version >= 0.11.5

Workarounds

Don't use the includeInheritedProps: true options or the withInheritedProps instance if using a version >= 0.11.0.

References

Read more about the prototype pollution vulnerability

For more information

If you have any questions or comments about this advisory:

References

@mariocasciaro mariocasciaro published to mariocasciaro/object-path Oct 19, 2020
Reviewed Oct 19, 2020
Published to the GitHub Advisory Database Oct 19, 2020
Published by the National Vulnerability Database Oct 19, 2020
Last updated Nov 29, 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
High
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
High
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.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:H/A:H

EPSS score

0.198%
(58th percentile)

Weaknesses

CVE ID

CVE-2020-15256

GHSA ID

GHSA-cwx2-736x-mf6w

Source code

Credits

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