Packages / fsevents / Security

CriticalVulnerabilityGHSA-8r6j-v8pm-fqw3CVE-2023-45311Published 6 Oct 2023

Code injection in fsevents

Your version

Affected releases · fsevents

  • 1.x1.0.0 – 1.2.10Fixed in 1.2.11
  • 0.3.x and older0.1.1 – 0.3.8No fix, no longer updated

On 1.x, the newest line:

npm install fsevents@1.2.11
Every release on a timeline
2.x
  1. Not affected

    2.0.0 – 2.3.3

    18 releases, latest

1.x
  1. Affected

    1.0.0 – 1.2.10

    32 releases

  2. Fixed

    1.2.11 – 1.2.13

    3 releases

0.x
  1. Affected

    0.1.1 – 0.3.8

    15 releases

68 stable releases of fsevents, oldest to newest, one row per major.

What happens

fsevents before 1.2.11 depends on the fsevents-binaries.s3-us-west-2.amazonaws.com URL, which might allow an adversary to execute arbitrary code if any JavaScript project (that depends on fsevents) distributes code that was obtained from that URL at a time when it was controlled by an adversary.

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.