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

fix(deps): update dependency lodash to v4.17.21 [security] #41

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

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Aug 10, 2019

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
lodash (source) 4.17.10 -> 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-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.

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

v4.17.11

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.

@renovate renovate bot changed the title fix(deps): update dependency lodash to v4.17.13 [security] fix(deps): update dependency lodash to v4.17.12 [security] Dec 14, 2019
@renovate renovate bot force-pushed the renovate/npm-lodash-vulnerability branch from b9692cd to 171147f Compare June 30, 2020 23:00
@renovate renovate bot force-pushed the renovate/npm-lodash-vulnerability branch from 171147f to 018e5a5 Compare July 10, 2020 19:51
@renovate renovate bot force-pushed the renovate/npm-lodash-vulnerability branch from 018e5a5 to 817dcc5 Compare August 27, 2020 12:57
@renovate renovate bot changed the title fix(deps): update dependency lodash to v4.17.12 [security] fix(deps): update dependency lodash to v4.17.19 [security] Aug 27, 2020
@renovate renovate bot force-pushed the renovate/npm-lodash-vulnerability branch from 817dcc5 to cf2dfff Compare April 26, 2021 14:37
@renovate renovate bot changed the title fix(deps): update dependency lodash to v4.17.19 [security] fix(deps): update dependency lodash to v4.17.21 [security] May 9, 2021
@renovate renovate bot force-pushed the renovate/npm-lodash-vulnerability branch from cf2dfff to c270fc1 Compare April 24, 2022 23:37
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.

None yet

1 participant