Skip to content

Prototype Pollution in merge-deep

High severity GitHub Reviewed Published Jul 26, 2018 to the GitHub Advisory Database • Updated Sep 7, 2023

Package

npm merge-deep (npm)

Affected versions

< 3.0.1

Patched versions

3.0.1

Description

Versions of merge-deep before 3.0.1 are vulnerable to prototype pollution via merging functions.

Recommendation

Update to version 3.0.1 or later.

References

Published to the GitHub Advisory Database Jul 26, 2018
Reviewed Jun 16, 2020
Last updated Sep 7, 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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
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.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

EPSS score

0.106%
(44th percentile)

Weaknesses

CVE ID

CVE-2018-3722

GHSA ID

GHSA-9g9w-hmvj-5h57

Source code

No known source code
Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.