npmWorst: Critical3 advisories

uglify-js: known vulnerabilities

uglify-js has 3 reviewed security advisories in the GitHub Advisory Database — 1 critical, 2 high. The most recent was published 2018-10-09. Each one below lists the affected version range, the release that fixes it, its CVE and severity. SkyShield matches these against the uglify-js versions running across your servers, containers and images, and ranks what to patch first.

How to fix uglify-js

Upgrade uglify-js to a release at or above the fixed version shown for each advisory below. For npm:

npm install uglify-js@2.4.24 (or run npm audit fix)

SkyShield checks the installed version on every machine and container, so you can see which hosts are still on an affected release after you roll the fix out.

Advisories (3)

High severity vulnerability that affects uglify-js High — Affected: before 2.4.24. Fixed in 2.4.24. Published 2018-10-09. GHSA-g6f4-j6c2-w3p3
Regular Expression Denial of Service in uglify-js High 7.5 CWE-1333 — Affected: before 2.6.0. Fixed in 2.6.0. Published 2017-10-24. GHSA-c9f4-xj24-8jqx · CVE-2015-8858
Incorrect Handling of Non-Boolean Comparisons During Minification in uglify-js Critical 9.8 CWE-1254 CWE-670 — Affected: before 2.4.24. Fixed in 2.4.24. Published 2017-01-23. GHSA-34r7-q49f-h37c · CVE-2015-8857

Find uglify-js across your fleet

Install one agent per server and connect your cloud. SkyShield matches your packages and images against GHSA, CISA KEV and EPSS and shows the fix per machine. Free for one server, then from $49 per server a month. Start free.