Skip to content
Fencer Intel
medium 6.5

CVE-2018-3721 json

Prototype Pollution in lodash

published 8y ago modified 4mo ago also GHSA-fvqr-27wr-82fm , EUVD-2018-0265

cvss
6.5
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
2.3%
EPSS 2.3% chance of exploitation in 30 days, percentile 83%
public exploits
0
none known

Summary

lodash node module before 4.17.5 suffers from a Modification of Assumed-Immutable Data (MAID) vulnerability via defaultsDeep, merge, and mergeWith functions, which allows a malicious user to modify the prototype of "Object" via __proto__, causing the addition or modification of an existing property that will exist on all objects.

Patch / fix

  • npm lodash 4.17.5
  • rubygems lodash-rails 4.17.5
  • lodash lodash 4.17.5
  • node-lodash Debian 14, Debian 13, Debian 12 4.17.11+dfsg-1

debian advisories DEBIAN-CVE-2018-3721

Is CVE-2018-3721 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2018-3721 updated cvss 2.9

lodash: Prototype pollution in utilities function

  • Red Hat CloudForms Management Engine 5 lodash-rails Red Hat OpenShift Enterprise 3 nodejs-lodash
    affected: no fix planned “Will not fix”
  • Red Hat Virtualization 4 ovirt-engine-dashboard
    affected: no fix planned “Out of support scope”
  • Red Hat Quay v3 quay/quay-rhel8 v3.6.0-62
    fixed: vendor fix RHSA-2021:3917
  • Red Hat Quay v3 quay/clair-rhel8 v3.6.0-70, quay/quay-builder-rhel8 v3.6.0-44, quay/quay-operator-rhel8 v3.6.0-43, quay/quay-operator-bundle v3.6.0-48, quay/quay-bridge-operator-rhel8 v3.6.0-40, quay/quay-bridge-operator-bundle v3.6.0-35, +3 more Red Hat Mobile Application Platform 4 nodejs-lodash Red Hat Virtualization 4 ovirt-engine-api-explorer, ovirt-engine-ui-extensions
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

2.35% chance of exploitation in the next 30 days, higher than 83% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • hackerone.com https://hackerone.com/reports/310443 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 3.1 6.5 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N
NVD 2.0 4.0 AV:N/AC:L/Au:S/C:N/I:P/A:N
GitHub 3.1 6.5 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N

Affected packages

ecosystem package affected fixed in
npm lodash
<4.17.5
4.17.5
rubygems lodash-rails
<4.17.5
4.17.5

Affected products

  • HackerOne lodash node module

Classification

Weakness
  • CWE-471 Modification of Assumed-Immutable Data (MAID)
  • CWE-1321 Improperly Controlled Modification of Object Prototype Attributes

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.