Service interruption via unenforced concurrency limits
Published Oct 20, 2021 · Updated Aug 4, 2024
Uncontrolled resource consumption in modern-async before 1.0.4 allows attackers to interrupt dependent services through unbounded concurrency. The forEachLimit callback wrapper invokes iteratee without await, so mapLimit sees each wrapper resolve immediately and starts later work beyond the supplied limit. Exploitation requires a consuming application to pass attacker-driven work to forEachLimit or forEachSeries; the consequence is a service interruption in that application.
Summary
What happened
Uncontrolled resource consumption in modern-async before 1.0.4 allows attackers to interrupt dependent services through unbounded concurrency. The forEachLimit callback wrapper invokes iteratee without await, so mapLimit sees each wrapper resolve immediately and starts later work beyond the supplied limit. Exploitation requires a consuming application to pass attacker-driven work to forEachLimit or forEachSeries; the consequence is a service interruption in that application.
The record
- CVE
- CVE-2021-41167
- Published
- Oct 20, 2021
- Updated
- Aug 4, 2024
- Vendor
- Nicolas Vanhoren
- Product
- modern-async
- Classifications
- CWE-770, CWE-400, T1499
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 20, 2021CVE publishedPublication date reported by the CVE source.
- Aug 4, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 1.0.4
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- forEachLimit concurrency reproductionproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo