CVE-2019-10744 — lodash
CRITICALCVE-2019-10744 is a critical-severity (CVSS 9.1) CWE-1321 vulnerability in lodash. 1 public exploit reference exists, so weaponization risk is real. A fix is available for lodash — see the affected versions and patch details below.
Prototype Pollution in lodash
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
CVE-2019-10744 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 377,333 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.
lodashnpmlodash-esnpmlodash-amdnpmDescription
Versions of lodash lower than 4.17.12 are vulnerable to Prototype Pollution. The function defaultsDeep could be tricked into adding or modifying properties of Object.prototype using a constructor payload.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | lodash | all versions | 4.17.12npm install lodash@4.17.12 |
| 📦npm | lodash-es | all versions | 4.17.14npm install lodash-es@4.17.14 |
| 📦npm | lodash-amd | all versions | 4.17.13npm install lodash-amd@4.17.13 |
| 📦npm | lodash.defaultsdeep | all versions | 4.6.1npm install lodash.defaultsdeep@4.6.1 |
| 💎RubyGems | lodash-rails | all versions | 4.17.12bundle update lodash-rails --conservative |
Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for lodash, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update lodash to 4.17.12 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2019-10744 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2019-10744 can be triaged on real exposure rather than presence alone.
Tailored to CVE-2019-10744. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
The lodash dependency is included in OpenShift Container Platform (OCP) by Kibana in the aggregated logging stack. Elastic have issued a security advisory (ESA-2019-10) for Kibana for this vulnerability, and in that advisory stated that no exploit vectors had been identified in Kibana. Therefore we rate this issue as…
| Product | Fixed in | Advisory |
|---|---|---|
| Jaeger-1.17 | distributed-tracing/jaeger-all-in-one-rhel7:1.17.2-3 | RHSA-2020:2819 |
| Openshift Service Mesh 1.0 | jaeger-0:v1.13.1.redhat7-1.el7 | RHSA-2020:2362 |
| Red Hat AMQ 7.10.0 | nodejs-lodash | RHSA-2022:5101 |
| Red Hat Fuse 7.10 | nodejs-lodash | RHSA-2021:5134 |
| Red Hat Virtualization Engine 4.3 | ovirt-web-ui-0:1.6.0-1.el7ev | RHSA-2019:3024 |
Frequently Asked Questions
Is CVE-2019-10744 in your dependencies?
O3 Security finds CVE-2019-10744 across npm, RubyGems dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.