Bumps lodash from 4.17.4 to 4.17.11. This update includes security fixes.
Vulnerabilities fixed
*Sourced from [The Node Security Working Group](https://github.com/nodejs/security-wg/blob/master/vuln/npm/368.json).*
> **lodash prototype pollution**
> lodash node module before 4.17.5 suffers from a prototype pollution 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.
>
> Affected versions: <4.17.5
Commits
- [`0843bd4`](https://github.com/lodash/lodash/commit/0843bd46ef805dd03c0c8d804630804f3ba0ca3c) Bump to v4.17.11.
- [`3ac4b26`](https://github.com/lodash/lodash/commit/3ac4b261e4a920a07673d49edfb84bd317f449f7) Rebuild lodash and docs.
- [`eaa9f36`](https://github.com/lodash/lodash/commit/eaa9f36e912a97bfc95f6bdd28ea07e0a62b82e9) Commit package-lock.json.
- [`552f94a`](https://github.com/lodash/lodash/commit/552f94a7db34a8036689d6aae6c67c789e4e79a6) Lint nits.
- [`d8ddc1a`](https://github.com/lodash/lodash/commit/d8ddc1a15f8ac3f9ac952818cc7f7b3d049b41ef) Add test for indirectly merging `Object` properties.
- [`e5f9af5`](https://github.com/lodash/lodash/commit/e5f9af54189ce714f5e53084337f54e2fea1de8d) Remove prototype property check in safeGet().
- [`2de676f`](https://github.com/lodash/lodash/commit/2de676fe76bc68fb279ac84c1c87d59511ced8cc) Ensure placeholder properties are set for fp.convert() results. [closes #3440]
- [`278c6dd`](https://github.com/lodash/lodash/commit/278c6dd33dfc7040b37c7148a645416f7c97e9ea) Cleanup _.merge tests for function properties.
- [`79b9d20`](https://github.com/lodash/lodash/commit/79b9d20a912118bf06acd093071902ed972daf4e) Fix inconsistent merging of multiple sources to function property
- [`6e62e1e`](https://github.com/lodash/lodash/commit/6e62e1e8df7b907beaa37a3182752d310314589f) Cleanup ReDoS test.
- Additional commits viewable in [compare view](https://github.com/lodash/lodash/compare/4.17.4...4.17.11)
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it
- `@dependabot merge` will merge this PR after your CI passes on it
- `@dependabot cancel merge` will cancel a previously requested merge
- `@dependabot reopen` will reopen this PR if it is closed
- `@dependabot ignore this [patch|minor|major] version` will close this PR and stop Dependabot creating any more for this minor/major version (unless you reopen the PR or upgrade to it yourself)
- `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
- `@dependabot use these labels` will set the current labels as the default for future PRs for this repo and language
- `@dependabot use these reviewers` will set the current reviewers as the default for future PRs for this repo and language
- `@dependabot use these assignees` will set the current assignees as the default for future PRs for this repo and language
- `@dependabot use this milestone` will set the current milestone as the default for future PRs for this repo and language
- `@dependabot badge me` will comment on this PR with code to add a "Dependabot enabled" badge to your readme
Additionally, you can set the following in your Dependabot [dashboard](https://app.dependabot.com):
- Update frequency (including time of day and day of week)
- Automerge options (never/patch/minor, and dev/runtime dependencies)
- Pull request limits (per update run and/or open at any time)
- Out-of-range updates (receive only lockfile updates, if desired)
- Security updates (receive only security updates, if desired)
Finally, you can contact us by mentioning @dependabot.
Bumps lodash from 4.17.4 to 4.17.11. This update includes security fixes.
Vulnerabilities fixed
*Sourced from [The Node Security Working Group](https://github.com/nodejs/security-wg/blob/master/vuln/npm/368.json).* > **lodash prototype pollution** > lodash node module before 4.17.5 suffers from a prototype pollution 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. > > Affected versions: <4.17.5Commits
- [`0843bd4`](https://github.com/lodash/lodash/commit/0843bd46ef805dd03c0c8d804630804f3ba0ca3c) Bump to v4.17.11. - [`3ac4b26`](https://github.com/lodash/lodash/commit/3ac4b261e4a920a07673d49edfb84bd317f449f7) Rebuild lodash and docs. - [`eaa9f36`](https://github.com/lodash/lodash/commit/eaa9f36e912a97bfc95f6bdd28ea07e0a62b82e9) Commit package-lock.json. - [`552f94a`](https://github.com/lodash/lodash/commit/552f94a7db34a8036689d6aae6c67c789e4e79a6) Lint nits. - [`d8ddc1a`](https://github.com/lodash/lodash/commit/d8ddc1a15f8ac3f9ac952818cc7f7b3d049b41ef) Add test for indirectly merging `Object` properties. - [`e5f9af5`](https://github.com/lodash/lodash/commit/e5f9af54189ce714f5e53084337f54e2fea1de8d) Remove prototype property check in safeGet(). - [`2de676f`](https://github.com/lodash/lodash/commit/2de676fe76bc68fb279ac84c1c87d59511ced8cc) Ensure placeholder properties are set for fp.convert() results. [closes #3440] - [`278c6dd`](https://github.com/lodash/lodash/commit/278c6dd33dfc7040b37c7148a645416f7c97e9ea) Cleanup _.merge tests for function properties. - [`79b9d20`](https://github.com/lodash/lodash/commit/79b9d20a912118bf06acd093071902ed972daf4e) Fix inconsistent merging of multiple sources to function property - [`6e62e1e`](https://github.com/lodash/lodash/commit/6e62e1e8df7b907beaa37a3182752d310314589f) Cleanup ReDoS test. - Additional commits viewable in [compare view](https://github.com/lodash/lodash/compare/4.17.4...4.17.11)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase
.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot ignore this [patch|minor|major] version` will close this PR and stop Dependabot creating any more for this minor/major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) - `@dependabot use these labels` will set the current labels as the default for future PRs for this repo and language - `@dependabot use these reviewers` will set the current reviewers as the default for future PRs for this repo and language - `@dependabot use these assignees` will set the current assignees as the default for future PRs for this repo and language - `@dependabot use this milestone` will set the current milestone as the default for future PRs for this repo and language - `@dependabot badge me` will comment on this PR with code to add a "Dependabot enabled" badge to your readme Additionally, you can set the following in your Dependabot [dashboard](https://app.dependabot.com): - Update frequency (including time of day and day of week) - Automerge options (never/patch/minor, and dev/runtime dependencies) - Pull request limits (per update run and/or open at any time) - Out-of-range updates (receive only lockfile updates, if desired) - Security updates (receive only security updates, if desired) Finally, you can contact us by mentioning @dependabot.