Skip to content

Prototype Pollution in x-assign

High severity GitHub Reviewed Published Oct 21, 2021 to the GitHub Advisory Database • Updated Jan 27, 2023

Package

npm x-assign (npm)

Affected versions

<= 0.1.4

Patched versions

None

Description

This vulnerability affects all versions of package x-assign. The global proto object can be polluted using the proto object.

References

Published by the National Vulnerability Database Oct 20, 2021
Reviewed Oct 21, 2021
Published to the GitHub Advisory Database Oct 21, 2021
Last updated Jan 27, 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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
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:L/PR:N/UI:N/S:U/C:H/I:L/A:L

EPSS score

0.404%
(74th percentile)

Weaknesses

CVE ID

CVE-2021-23452

GHSA ID

GHSA-4mvj-rq4v-2fxw

Source code

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