Bug 1671878 (CVE-2018-16487) - CVE-2018-16487 lodash: Prototype pollution in utilities function
Summary: CVE-2018-16487 lodash: Prototype pollution in utilities function
Keywords:
Status: CLOSED ERRATA
Alias: CVE-2018-16487
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL:
Whiteboard:
Depends On: 1671880 1671879 1692352 1849514 1849515
Blocks: 1671882
TreeView+ depends on / blocked
 
Reported: 2019-02-01 23:15 UTC by Laura Pardo
Modified: 2021-10-25 09:51 UTC (History)
27 users (show)

Fixed In Version: nodejs-lodash 4.17.11
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-10-25 09:51:46 UTC
Embargoed:

Attachments (Terms of Use)

Description Laura Pardo 2019-02-01 23:15:28 UTC 
A prototype pollution vulnerability was found in lodash <4.17.11 where the functions merge, mergeWith, and defaultsDeep can be tricked into adding or modifying properties of Object.prototype.


References:
https://hackerone.com/reports/380873

Upstream Patch:
https://github.com/lodash/lodash/commit/90e6199a161b6445b01454517b40ef65ebecd2ad
Comment 1 Laura Pardo 2019-02-01 23:15:45 UTC 
Created lodash tracking bugs for this issue:

Affects: fedora-all [bug 1671879]


Created nodejs-lodash tracking bugs for this issue:

Affects: epel-all [bug 1671880]
Comment 3 Riccardo Schirone 2019-03-25 12:35:38 UTC 
rh-nodejs8-nodejs does not install modules that export the vulnerable functions, however they may be used internally.
Comment 6 Jason Shepherd 2019-08-08 05:50:08 UTC 
This vulnerability is out of security support scope for the following product:

 * Red Hat Mobile Application Platform

 Please refer to https://access.redhat.com/support/policy/updates/rhmap for more details
Comment 8 Sam Fowler 2020-06-22 06:18:29 UTC 
In OpenShift Container Platform, only the kibana package includes a vulnerable version, other containers include a version higher than 4.17.11 so are not affected.
Note You need to log in before you can comment on or make changes to this bug.