Skip to content

Prototype Pollution in async

High severity GitHub Reviewed Published Apr 7, 2022 to the GitHub Advisory Database • Updated Jun 24, 2024

Package

npm async (npm)

Affected versions

>= 3.0.0, < 3.2.2
>= 2.0.0, < 2.6.4

Patched versions

3.2.2
2.6.4

Description

A vulnerability exists in Async through 3.2.1 for 3.x and through 2.6.3 for 2.x (fixed in 3.2.2 and 2.6.4), which could let a malicious user obtain privileges via the mapValues() method.

References

Published by the National Vulnerability Database Apr 6, 2022
Published to the GitHub Advisory Database Apr 7, 2022
Reviewed Apr 7, 2022
Last updated Jun 24, 2024

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
Local
Attack complexity
Low
Privileges required
None
User interaction
Required
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:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

EPSS score

0.175%
(56th percentile)

Weaknesses

CVE ID

CVE-2021-43138

GHSA ID

GHSA-fwr7-v2mv-hh25

Source code

Credits

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