Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
📦 npm

GHSA-fwr7-v2mv-hh25

HIGH

GHSA-fwr7-v2mv-hh25 is a high-severity (CVSS 7.8) CWE-1321 vulnerability in async. 1 public exploit reference exists, so weaponization risk is real. O3 Security confirms whether GHSA-fwr7-v2mv-hh25 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Prototype Pollution in async

Also known asCVE-2021-43138
Published
Apr 7, 2022
Updated
Jun 24, 2024
Affected
2 pkgs
Patched
2 / 2
Exploits
1 known

Blast Radius

2 pkgs affected

Weekly download volume for affected packages — a proxy for how broadly this vulnerability is deployed.

asyncnpm
102.6Mdownloads / week

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.

Affected Packages

2 total 2 fixed
EcosystemPackageVulnerable rangeFix
📦npmasync3.0.0&&< 3.2.23.2.2
📦npmasync2.0.0&&< 2.6.42.6.4
Exploits & PoCs
1

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for async. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Fix

    Update async to 3.2.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-fwr7-v2mv-hh25 is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 pinpoints whether GHSA-fwr7-v2mv-hh25 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-fwr7-v2mv-hh25. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

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.
O3 Security · Impact-Aware SCA

Is GHSA-fwr7-v2mv-hh25 in your dependencies?

O3 detects GHSA-fwr7-v2mv-hh25 across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.