CriticalGHSA-jf85-cpcp-j695CVE-2019-10744SNYK-JS-LODASH-450202
Prototype Pollution in lodash
Published 10 Jul 2019 · Updated 10 Sept 2026
Affected packages
lodashnpm
- Affected
- <4.17.12
- Fixed in
- 4.17.12
Update to the fixed version for your release line, for example:
npm install lodash@4.17.12lodash-esnpm
- Affected
- <4.17.14
- Fixed in
- 4.17.14
Update to the fixed version for your release line, for example:
npm install lodash-es@4.17.14lodash-amdnpm
- Affected
- <4.17.13
- Fixed in
- 4.17.13
Update to the fixed version for your release line, for example:
npm install lodash-amd@4.17.13- Affected
- <4.6.1
- Fixed in
- 4.6.1
Update to the fixed version for your release line, for example:
npm install lodash.defaultsdeep@4.6.1Details
Versions of lodash before 4.17.12 are vulnerable to Prototype Pollution. The function defaultsDeep allows a malicious user to modify the prototype of Object via {constructor: {prototype: {...}}} causing the addition or modification of an existing property that will exist on all objects.
Recommendation
Update to version 4.17.12 or later.
Is GHSA-jf85-cpcp-j695 in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected lodash, and gives you the command that fixes it.
References
- Advisorynvd.nist.gov/vuln/detail/CVE-2019-10744
- Linkgithub.com/lodash/lodash/pull/4336
- Linkaccess.redhat.com/errata/RHSA-2019:3024
- Linkgithub.com/rubysec/ruby-advisory-db/blob/master/gems/lodash-rails/CVE-2019-10744.yml
- Linksecurity.netapp.com/advisory/ntap-20191004-0005
- Linksnyk.io/vuln/SNYK-JS-LODASH-450202
- Linksupport.f5.com/csp/article/K47105354?utm_source=f5support&%3Butm_medium=RSS
- Linksupport.f5.com/csp/article/K47105354?utm_source=f5support&utm_medium=RSS
- Linkwww.oracle.com/security-alerts/cpujan2021.html
- Linkwww.oracle.com/security-alerts/cpuoct2020.html
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.