npmWorst: High2 advisories

assign-deep: known vulnerabilities

assign-deep has 2 reviewed security advisories in the GitHub Advisory Database — 2 high. The most recent was published 2019-08-20. Each one below lists the affected version range, the release that fixes it, its CVE and severity. SkyShield matches these against the assign-deep versions running across your servers, containers and images, and ranks what to patch first.

How to fix assign-deep

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

npm install assign-deep@1.0.1 (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 (2)

assign-deep Vulnerable to Prototype Pollution High 7.5 CWE-1321 CWE-20 CWE-915 — Affected: from 1.0.0 up to 1.0.1. Fixed in 1.0.1. Published 2019-08-20. GHSA-66rh-8fw6-59q6 · CVE-2019-10745
Prototype Pollution in assign-deep High 8.8 CWE-1321 CWE-471 — Affected: before 0.4.7. Fixed in 0.4.7. Published 2018-06-07. GHSA-xcvv-84j5-jw9h · CVE-2018-3720

Find assign-deep 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.