🚨 [security] Update lodash: 4.17.15 → 4.17.20 (patch)

[depfu]

---

🚨 Your current dependencies have known security vulnerabilities 🚨

This dependency update fixes known security vulnerabilities. Please see the details below and assess their impact carefully. We recommend to merge and deploy this as soon as possible!

---

Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request.

What changed?

✳️ lodash (4.17.15 → 4.17.20) · Repo · Changelog

Security Advisories 🚨

🚨 Prototype Pollution in lodash

Versions of lodash prior to 4.17.19 are vulnerable to Prototype Pollution. The function zipObjectDeep allows a malicious user to modify the prototype of Object if the property identifiers are user-supplied. Being affected by this issue requires zipping objects based on user-provided property arrays.

This vulnerability causes the addition or modification of an existing property that will exist on all objects and may lead to Denial of Service or Code Execution under specific circumstances.

Commits

See the full diff on Github. The new version differs by 19 commits:

• Bump to v4.17.20.
• Documentation fixes.
• test.js: Remove trailing comma.
• Temporarily use a custom fork of `lodash-cli`.
• Re-enable Travis tests on `4.17` branch.
• Remove `/npm-package`.
• Bump to v4.17.19
• Add npm-package
• Bump to v4.17.18
• Bump to v4.17.17
• Rebuild lodash and docs
• Bump to v4.17.16
• fix(zipObjectDeep): prototype pollution (#4759)
• Sanitize sourceURL so it cannot affect evaled code (#4518)
• Fix lodash.isEqual for circular references (#4320) (#4515)
• Document matches* shorthands for over* methods (#4510) (#4514)
• Ensure `orderBy` will accept iteratee path arrays #4438 (#4513)
• (4.17) Short circuit sortedIndexBy methods for empty arrays (#4497)
• change documentation, show clearly how sortBy work with two iteratees (#4467)

---

Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with @depfu rebase.

All Depfu comment commands

@​depfu rebase

Rebases against your default branch and redoes this update

@​depfu recreate

Recreates this PR, overwriting any edits that you've made to it

@​depfu merge

Merges this PR once your tests are passing and conflicts are resolved

@​depfu close

Closes this PR and deletes the branch

@​depfu reopen

Restores the branch and reopens this PR (if it's closed)

@​depfu pause

Ignores all future updates for this dependency and closes this PR

@​depfu pause [minor|major]

Ignores all future minor/major updates for this dependency and closes this PR

@​depfu resume

Future versions of this dependency will create PRs again (leaves this PR as is)

[commit-lint]

Contributors

@depfu[bot]

Commit-Lint commands

You can trigger Commit-Lint actions by commenting on this PR:

• @Commit-Lint merge patch will merge dependabot PR on "patch" versions (X.X.Y - Y change)
• @Commit-Lint merge minor will merge dependabot PR on "minor" versions (X.Y.Y - Y change)
• @Commit-Lint merge major will merge dependabot PR on "major" versions (Y.Y.Y - Y change)
• @Commit-Lint merge disable will desactivate merge dependabot PR
• @Commit-Lint review will approve dependabot PR
• @Commit-Lint stop review will stop approve dependabot PR

[depfu]

Closed in favor of #47.