Skip to content

Uncontrolled Resource Consumption in fun-map

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

Package

npm fun-map (npm)

Affected versions

<= 3.3.1

Patched versions

None

Description

fun-map through 3.3.1 is vulnerable to Prototype Pollution. The function assocInM could be tricked into adding or modifying properties of 'Object.prototype' using a 'proto' payload.

References

Published by the National Vulnerability Database Apr 28, 2020
Reviewed May 25, 2021
Published to the GitHub Advisory Database Dec 10, 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
High
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:H/PR:N/UI:N/S:U/C:H/I:H/A:H

EPSS score

0.705%
(80th percentile)

CVE ID

CVE-2020-7644

GHSA ID

GHSA-p33m-7w7f-gmj8

Source code

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