Skip to content

modern-async's `forEachSeries` and `forEachLimit` functions do not limit the number of requests

High severity GitHub Reviewed Published Oct 20, 2021 in nicolas-van/modern-async • Updated Jan 27, 2023

Package

npm modern-async (npm)

Affected versions

< 1.0.4

Patched versions

1.0.4

Description

Impact

This is a bug affecting two of the functions in this library: forEachSeries and forEachLimit. They should limit the concurrency of some actions but, in practice, they don't. Any code calling these functions will be written thinking they would limit the concurrency but they won't. This could lead to potential security issues in other projects.

Patches

The problem has been patched in 1.0.4.

Workarounds

There is no workaround aside from upgrading to 1.0.4.

References

@nicolas-van nicolas-van published to nicolas-van/modern-async Oct 20, 2021
Reviewed Oct 20, 2021
Published by the National Vulnerability Database Oct 20, 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
None
Integrity
None
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:N/I:N/A:H

EPSS score

0.242%
(65th percentile)

Weaknesses

CVE ID

CVE-2021-41167

GHSA ID

GHSA-3pcq-34w5-p4g2

Source code

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