Vulnerability in modern-async (CVE-2021-41167)
Summary
Vulnerability in modern-async (CVE-2021-41167). Risk of unauthorized operations or information disclosure. Exploitable via forEachSeries. Mitigation: upgrade to 1.0.4 or later.
Original description
The description as published by the source.
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.
Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2021-41167 has been found in modern-async.
Attackers can target a specific entry point like forEachSeries over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade modern-async to 1.0.4 or later.
If unsure, ask your IT team or search "modern-async CVE-2021-41167" on the vendor's site.
CVE-2021-41167 (modern-async) — CWE-400
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: forEachSeries / forEachLimit
Patched: 1.0.4 — apply immediately
Workaround: There is no workaround aside from upgrading to 1.0.4.
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-400) exists in modern-async. Attackers reach the vulnerable code path via forEachSeries without authentication.
Check the vendor advisory for the affected versions of modern-async. Attack surface: forEachSeries / forEachLimit.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 1.0.4.
Workaround: There is no workaround aside from upgrading to 1.0.4.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'modern-async' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'modern-async' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
modern-asyncを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply temporary workaround mitigate
There is no workaround aside from upgrading to 1.0.4.パッチが適用されるまでの応急処置として、There is no workaround aside from upgrading to 1.0.4. を実施。回避策の副作用 (機能低下) を確認した上で。
-
3Apply patch patch
Upgrade modern-async to 1.0.4ステージング環境で 1.0.4 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
4Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- package github.com
- web github.com
- web github.com
- web github.com