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(package): Update dependency lodash to 4.17.21 [SECURITY] - abandoned #22

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

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Mar 4, 2021

Mend Renovate

This PR contains the following updates:

Package Change
lodash 4.17.11 -> 4.17.21

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.


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.

@renovate renovate bot changed the title chore(package): Update dependency lodash to 4.17.19 [SECURITY] chore(package): Update dependency lodash to 4.17.21 [SECURITY] May 9, 2021
@renovate renovate bot force-pushed the renovate/npm-lodash-vulnerability branch 3 times, most recently from d36ff10 to db16c04 Compare June 7, 2021 03:58
@renovate renovate bot changed the title chore(package): Update dependency lodash to 4.17.21 [SECURITY] chore(package): Update dependency lodash to 4.17.21 [SECURITY] - autoclosed Jun 10, 2021
@renovate renovate bot closed this Jun 10, 2021
@renovate renovate bot deleted the renovate/npm-lodash-vulnerability branch June 10, 2021 02:44
@renovate renovate bot changed the title chore(package): Update dependency lodash to 4.17.21 [SECURITY] - autoclosed chore(package): Update dependency lodash to 4.17.21 [SECURITY] Jun 10, 2021
@renovate renovate bot reopened this Jun 10, 2021
@renovate renovate bot restored the renovate/npm-lodash-vulnerability branch June 10, 2021 03:52
@renovate renovate bot force-pushed the renovate/npm-lodash-vulnerability branch from db16c04 to 05eb7ff Compare June 10, 2021 04:00
@renovate renovate bot force-pushed the renovate/npm-lodash-vulnerability branch from 05eb7ff to 736cc97 Compare June 10, 2021 04:54
@renovate renovate bot changed the title chore(package): Update dependency lodash to 4.17.21 [SECURITY] chore(package): Update dependency lodash to 4.17.21 [SECURITY] - abandoned Mar 24, 2023
@renovate
Copy link
Contributor Author

renovate bot commented Mar 25, 2023

Autoclosing Skipped

This PR has been flagged for autoclosing. However, it is being skipped due to the branch being already modified. Please close/delete it manually or report a bug if you think this is in error.

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.

1 participant