Packages

HighVulnerabilityGHSA-9j49-mfvp-vmhmCVE-2021-23406Published 2 Sep 2021

Code Injection in pac-resolver

Your version of degenerator

Affected releases · degenerator

  • 3.x3.0.0Fixed in 3.0.1
  • 2.x and older0.0.1 – 2.2.0No fix, no longer updated

On 3.x, the newest line:

npm install degenerator@3.0.1
Every release on a timeline
7.x
  1. Not affected

    7.0.0 – 7.0.2

    3 releases, latest

3.x
  1. Affected

    3.0.0

    1 release

  2. Fixed

    3.0.1 – 3.0.4

    4 releases

2.x
  1. Affected

    2.0.0 – 2.2.0

    7 releases

1.x
  1. Affected

    1.0.0 – 1.0.4

    5 releases

0.x
  1. Affected

    0.0.1 – 0.0.4

    4 releases

32 stable releases of degenerator, oldest to newest, one row per major.
Your version of pac-resolver

Affected releases · pac-resolver

  • 4.x and older0.0.1 – 4.2.0No fix, no longer updated

4.x has no fix yet; the newest fixed line:

npm install pac-resolver@5.0.0
Every release on a timeline
9.x
  1. Not affected

    9.0.0 – 9.0.2

    3 releases, latest

4.x
  1. Affected

    4.0.0 – 4.2.0

    4 releases

3.x
  1. Affected

    3.0.0

    1 release

2.x
  1. Affected

    2.0.0

    1 release

1.x
  1. Affected

    1.0.0 – 1.3.0

    10 releases

0.x
  1. Affected

    0.0.1 – 0.0.2

    2 releases

29 stable releases of pac-resolver, oldest to newest, one row per major.

What happens

This affects the package pac-resolver before 5.0.0. This can occur when used with untrusted input, due to unsafe PAC file handling. NOTE: The fix for this vulnerability is applied in the node-degenerator library, a dependency written by the same maintainer.

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.