CVE-2019-10745GHSA-66RH-8FW6-59Q6
assign-deep is vulnerable to Prototype Pollution in versions before 0.4.8 and version 1.0.0.
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 0.4.8, 1.0.1
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
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.
Timeline
- CVE published
- Record last updated
Affected versions
- n/a assign-deep
Version range not reported
- assign-deepnpm
fixed in 0.4.8
- assign-deepnpm
From 1.0.0 · fixed in 1.0.1