Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(deps): update dependency lodash to v4.17.21 [security] #4

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jul 13, 2019

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
lodash (source) 4.17.11 -> 4.17.21 age adoption passing confidence

GitHub Vulnerability Alerts

CVE-2019-10744

Versions of lodash before 4.17.12 are vulnerable to Prototype Pollution. The function defaultsDeep allows 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.12 or later.

CVE-2021-23337

lodash versions prior to 4.17.21 are vulnerable to Command Injection via the template function.

CVE-2020-8203

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.


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


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 this update again.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

@coveralls
Copy link

coveralls commented Jul 13, 2019

Pull Request Test Coverage Report for Build 96

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage remained the same at 100.0%

Totals Coverage Status
Change from base Build 18: 0.0%
Covered Lines: 31
Relevant Lines: 31

💛 - Coveralls

@renovate renovate bot force-pushed the renovate/npm-lodash-vulnerability branch from 9b4ac2a to b54b89a Compare July 19, 2019 02:33
@renovate renovate bot changed the title chore(deps): update dependency lodash to v4.17.13 [security] chore(deps): update dependency lodash to v4.17.12 [security] Dec 14, 2019
@renovate renovate bot force-pushed the renovate/npm-lodash-vulnerability branch from b54b89a to 7137406 Compare August 24, 2020 23:55
@renovate renovate bot changed the title chore(deps): update dependency lodash to v4.17.12 [security] chore(deps): update dependency lodash to v4.17.19 [security] Aug 24, 2020
@renovate renovate bot force-pushed the renovate/npm-lodash-vulnerability branch from 7137406 to 3346691 Compare April 26, 2021 17:41
@renovate renovate bot changed the title chore(deps): update dependency lodash to v4.17.19 [security] chore(deps): update dependency lodash to v4.17.21 [security] May 9, 2021
@renovate renovate bot force-pushed the renovate/npm-lodash-vulnerability branch from 3346691 to b74fc59 Compare April 24, 2022 20:23
@renovate
Copy link
Contributor Author

renovate bot commented Mar 24, 2023

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants