fix(deps): update dependency lodash to v4.17.21 [security] #4
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
^3.10.1
->^4.0.0
4.17.4
->4.17.21
GitHub Vulnerability Alerts
CVE-2018-3721
Versions of
lodash
before 4.17.5 are vulnerable to prototype pollution.The vulnerable functions are 'defaultsDeep', 'merge', and 'mergeWith' which allow 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.Recommendation
Update to version 4.17.5 or later.
CVE-2018-16487
Versions of
lodash
before 4.17.5 are vulnerable to prototype pollution.The vulnerable functions are 'defaultsDeep', 'merge', and 'mergeWith' which allow 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.11 or later.
CVE-2019-10744
Versions of
lodash
before 4.17.12 are vulnerable to Prototype Pollution. The functiondefaultsDeep
allows a malicious user to modify the prototype ofObject
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.
CVE-2019-1010266
lodash prior to 4.7.11 is affected by: CWE-400: Uncontrolled Resource Consumption. The impact is: Denial of service. The component is: Date handler. The attack vector is: Attacker provides very long strings, which the library attempts to match using a regular expression. The fixed version is: 4.7.11.
CVE-2021-23337
lodash
versions prior to 4.17.21 are vulnerable to Command Injection via the template function.Release Notes
lodash/lodash
v4.17.21
Compare Source
v4.17.20
Compare Source
v4.17.16
Compare Source
v4.17.15
Compare Source
v4.17.14
Compare Source
v4.17.13
Compare Source
v4.17.12
Compare Source
v4.17.11
Compare Source
v4.17.10
Compare Source
v4.17.9
Compare Source
v4.17.5
Compare Source
v4.17.4
Compare Source
v4.17.3
Compare Source
v4.17.2
Compare Source
v4.17.1
Compare Source
v4.17.0
Compare Source
v4.16.6
Compare Source
v4.16.5
Compare Source
v4.16.4
Compare Source
v4.16.3
Compare Source
v4.16.2
Compare Source
v4.16.1
Compare Source
v4.16.0
Compare Source
v4.15.0
Compare Source
v4.14.2
Compare Source
v4.14.1
Compare Source
v4.14.0
Compare Source
v4.13.1
Compare Source
v4.13.0
Compare Source
v4.12.0
Compare Source
v4.11.2
Compare Source
v4.11.1
Compare Source
v4.11.0
Compare Source
v4.10.0
Compare Source
v4.9.0
Compare Source
v4.8.2
Compare Source
v4.8.1
Compare Source
v4.8.0
Compare Source
v4.7.0
Compare Source
v4.6.1
Compare Source
v4.6.0
Compare Source
v4.5.1
Compare Source
v4.5.0
Compare Source
v4.4.0
Compare Source
v4.3.0
Compare Source
v4.2.1
Compare Source
v4.2.0
Compare Source
v4.1.0
Compare Source
v4.0.1
Compare Source
v4.0.0
Compare Source
lodash v4.0.0
2015 was big year! Lodash became the most depended on npm package, passed 1 billion downloads, & its v3 release saw massive adoption!
The year was also one of collaboration, as discussions began on merging Lodash & Underscore. Much of Lodash v4 is proofing out the ideas from those discussions. Lodash v4 would not be possible without the collaboration & contributions of the Underscore core team. In the spirit of merging our teams have blended with several members contributing to both libraries.
For 2016 & lodash v4.0.0 we wanted to cut loose, push forward, & take things up a notch!
Modern only
With v4 we’re breaking free from old projects, old environments, & dropping old IE < 9 support!
4 kB Core
Lodash’s kitchen-sink size will continue to grow as new methods & functionality are added. However, we now offer a 4 kB (gzipped) core build that’s compatible with Backbone v1.2.4 for folks who want Lodash without lugging around the kitchen sink.
More ES6
We’ve continued to embrace ES6 with methods like _.isSymbol, added support for cloning & comparing array buffers, maps, sets, & symbols, converting iterators to arrays, & iterable
_(…)
.In addition, we’ve published an es-build & pulled babel-plugin-lodash into core to make tree-shaking a breeze.
More Modular
Pop quiz! 📣
What category path does the
bindAll
method belong to? Is itA)
require('lodash/function/bindAll')
B)
require('lodash/utility/bindAll')
C)
require('lodash/util/bindAll')
Don’t know? Well, with v4 it doesn’t matter because now module paths are as simple as
We’ve also reduced module complexity making it easier to create smaller bundles. This has helped Lodash adoption with libraries like Async & Redux!
1st Class FP
With v3 we introduced lodash-fp. We learned a lot & with v4 we decided to pull it into core.
Now you can get immutable, auto-curried, iteratee-first, data-last methods as simply as
Chakra Optimized
Well actually, while we’re excited about Chakra, Lodash is optimized for great performance across all engines. Unlike many libraries, we don’t favor a single engine so we can deliver solid performance & support regardless of engine.
With v4 we’ve continued our commitment to performance; expanding support for lazy evaluation & improving the performance of core functionality like circular reference detection.
Emojis
Taking things up a notch Lodash v4 has added support for emojis! Includes things like
astral symbols, unicode modifiers, variation selector characters, zero-width joiners, & regional indicator symbols.
Breaking changes
We’ve introduced more breaking changes in this release than any other so be sure to check out the changelog for a full rundown of changes & give lodash-migrate a spin to help migrate older Lodash code to the latest release.
If you dig Lodash don’t forget to star the repo or
npm star lodash
!Configuration
📅 Schedule: Branch creation - "" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about these updates again.
This PR has been generated by Mend Renovate. View repository job log here.