🚨 [security] Update lodash: 4.17.4 → 4.17.19 (patch)#22
Closed
depfu[bot] wants to merge 1 commit intomasterfrom
Closed
🚨 [security] Update lodash: 4.17.4 → 4.17.19 (patch)#22depfu[bot] wants to merge 1 commit intomasterfrom
depfu[bot] wants to merge 1 commit intomasterfrom
Conversation
Author
|
Closed in favor of #27. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Welcome to Depfu 👋
This is one of the first three pull requests with dependency updates we've sent your way. We tried to start with a few easy patch-level updates. Hopefully your tests will pass and you can merge this pull request without too much risk. This should give you an idea how Depfu works in general.
After you merge your first pull request, we'll send you a few more. We'll never open more than seven PRs at the same time so you're not getting overwhelmed with updates.
Let us know if you have any questions. Thanks so much for giving Depfu a try!
🚨 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.4 → 4.17.19) · Repo · Changelog
Security Advisories 🚨
🚨 Prototype Pollution in lodash
🚨 Moderate severity vulnerability that affects lodash
🚨 High severity vulnerability that affects lodash, lodash-es, lodash-amd, lodash.template, lodash.merge, lodash.mergewith, and lodash.defaultsdeep
🚨 Critical severity vulnerability that affects lodash, lodash-es, lodash-amd, lodash.template, lodash.merge, lodash.mergewith, and lodash.defaultsdeep
🚨 Low severity vulnerability that affects lodash
🚨 High severity vulnerability that affects lodash
Commits
See the full diff on Github. The new version differs by 74 commits:
Bump to v4.17.19Add npm-packageBump to v4.17.18Bump to v4.17.17Rebuild lodash and docsBump to v4.17.16fix(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)Bump to v4.17.15.Rebuild lodash and docs.Bump to v4.17.14.Rebuild lodash and docs.Bump to v4.17.13.Rebuild lodash and docs.Bump to v4.17.12.Rebuild lodash and docs.Update OpenJS references.Fix minified build.Fix test bootstrap for core build.Fix tests in older browsers.Fix style:test lint nits.Update deps.Format nit.Use nativeIsFinite() instead of Number.isFinite().Whitespace nit.Revert "perf(toNumber): use +value to convert binary/octal/hexadecimal string (#4230)"Prevent prototype pollution chaining to code execution via _.template (#4355)fix: prototype pollution in _.defaultsDeep (#4336)Fixes issue with Object prototype and the chaining syntax. [closes #4247]Round Infinity with a precision argument returns Infinity (#4272)mergeWith: stack passed to customizer should always be defined (#4244)perf(toNumber): use +value to convert binary/octal/hexadecimal string (#4230)cancel old timer (#4139)Update wording of fp wiki template for method spread rule exceptions.Revert "Ensure _.pick paths aren't interpolated twice. [closes #3952]"Ensure _.pick paths aren't interpolated twice. [closes #3952]Ensure map and set clones contain custom properties of source values. [closes #3951]Bump to v4.17.11.Rebuild lodash and docs.Commit package-lock.json.Lint nits.Add test for indirectly merging `Object` properties.Remove prototype property check in safeGet().Ensure placeholder properties are set for fp.convert() results. [closes #3440]Cleanup _.merge tests for function properties.Fix inconsistent merging of multiple sources to function propertyCleanup ReDoS test.Prevent ReDoSEnsure Object.prototype is not augmented by _.merge.Bump to v4.17.10.Rebuild lodash and docs.Bump to v4.17.9.Rebuild lodash and docs.Use util.types to migrate DEP0103 in Node.js.Bump to v4.17.5.Rebuild lodash and docs.Fix style nits.Make _.defaults avoid accessing property values it doesn't need to. [closes #2983]Avoid using the values toString method in _.invert if it’s not a function. [closes #3260]Add 4.17.5 branch to travis.Enable _.words to detect ordinals in compound words. [closes #3561]Replacing a regex in `stringToPath` with a quick character code check. (#3308)Avoid shadowing `result` in `remainingWait`. (#3280)stringToPath: avoid shadowing variable. (#3226)Support symbols in property paths of `set`. [closes #3189]Use `new` to create the array clone.Fix cloneDeep with circularly dependent Sets/Maps. [closes #3122]Avoid merging properties on to __proto__ objects.Ensure `cloneByPath` preserves uncloneable values. [closes #3203]👉 No CI detected
You don't seem to have any Continuous Integration service set up!
Without a service that will test the Depfu branches and pull requests, we can't inform you if incoming updates actually work with your app. We think that this degrades the service we're trying to provide down to a point where it is more or less meaningless.
This is fine if you just want to give Depfu a quick try. If you want to really let Depfu help you keep your app up-to-date, we recommend setting up a CI system:
depfu/.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