Packages / async / Security

HighVulnerabilityGHSA-fwr7-v2mv-hh25CVE-2021-43138Published 7 Apr 2022

Prototype Pollution in async

Your version

Affected releases · async

  • 3.x3.0.0 – 3.2.1Fixed in 3.2.2
  • 2.x2.0.0 – 2.6.3Fixed in 2.6.4

On 3.x, the newest line:

npm install async@3.2.2
Every release on a timeline
3.x
  1. Affected

    3.0.0 – 3.2.1

    6 releases

  2. Fixed

    3.2.2 – 3.2.6

    5 releases, latest

2.x
  1. Affected

    2.0.0 – 2.6.3

    16 releases

  2. Fixed

    2.6.4

    1 release

86 stable releases of async, oldest to newest, one row per major.

What happens

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.

A whole project to check? Paste its package.json in the dependency check: every deprecated, outdated or vulnerable dependency, with what to upgrade to. Free, no account.