Skip to content

Prototype Pollution in set-in

Critical severity GitHub Reviewed Published Mar 18, 2022 to the GitHub Advisory Database • Updated Jan 27, 2023

Package

npm set-in (npm)

Affected versions

< 2.0.3

Patched versions

2.0.3

Description

The package set-in before 2.0.3 is vulnerable to Prototype Pollution via the setIn method, as it allows an attacker to merge object prototypes into it. Note: This vulnerability derives from an incomplete fix of CVE-2020-28273

References

Published by the National Vulnerability Database Mar 17, 2022
Published to the GitHub Advisory Database Mar 18, 2022
Reviewed Mar 18, 2022
Last updated Jan 27, 2023

Severity

Critical

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

EPSS score

0.350%
(72nd percentile)

Weaknesses

CVE ID

CVE-2022-25354

GHSA ID

GHSA-6956-83fg-5wc5

Source code

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