Code Injection in pac-resolver
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.1Every release on a timeline
Not affected
7.0.0 – 7.0.2
3 releases, latest
Affected
3.0.0
1 release
Fixed
3.0.1 – 3.0.4
4 releases
Affected
2.0.0 – 2.2.0
7 releases
Affected
1.0.0 – 1.0.4
5 releases
Affected
0.0.1 – 0.0.4
4 releases
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.0Every release on a timeline
Not affected
9.0.0 – 9.0.2
3 releases, latest
Affected
4.0.0 – 4.2.0
4 releases
Affected
3.0.0
1 release
Affected
2.0.0
1 release
Affected
1.0.0 – 1.3.0
10 releases
Affected
0.0.1 – 0.0.2
2 releases
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.