🚨 [security] Update lodash 4.17.19 → 4.17.23 (patch)

[depfu]

---

🚨 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.19 → 4.17.23) · Repo · Changelog

Security Advisories 🚨

🚨 Lodash has Prototype Pollution Vulnerability in `_.unset` and `_.omit` functions

Impact

Lodash versions 4.0.0 through 4.17.22 are vulnerable to prototype pollution in the _.unset and _.omit functions. An attacker can pass crafted paths which cause Lodash to delete methods from global prototypes.

The issue permits deletion of properties but does not allow overwriting their original behavior.

Patches

This issue is patched on 4.17.23.

🚨 Regular Expression Denial of Service (ReDoS) in lodash

All versions of package lodash prior to 4.17.21 are vulnerable to Regular Expression Denial of Service (ReDoS) via the toNumber, trim and trimEnd functions.

Steps to reproduce (provided by reporter Liyuan Chen):

var lo = require('lodash');
function build_blank(n) {

var ret = "1"

for (var i = 0; i < n; i++) {

ret += " "

}

return ret + "1";

}

var s = build_blank(50000) var time0 = Date.now();

lo.trim(s)

var time_cost0 = Date.now() - time0;

console.log("time_cost0: " + time_cost0);

var time1 = Date.now();

lo.toNumber(s) var time_cost1 = Date.now() - time1;

console.log("time_cost1: " + time_cost1);

var time2 = Date.now();

lo.trimEnd(s);

var time_cost2 = Date.now() - time2;

console.log("time_cost2: " + time_cost2);

🚨 Command Injection in lodash

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

Commits

See the full diff on Github. The new version differs by 30 commits:

• Bump main to v4.17.23 (#6088)
• fix: setCacheHas JSDoc return type should be boolean (#6071)
• jsdoc: Add -0 and BigInt zeros to _.compact falsey values list (#6062)
• Prevent prototype pollution on baseUnset function
• doc: fix autoLink function, conversion of source links (#6056)
• chore: remove `yarn.lock` file (#6053)
• ci: remove legacy configuration files (#6052)
• feat: add renovate setup (#6039)
• ci: add pipeline for Bun (#6023)
• docs: update links related to Open JS Foundation (#5968)
• Add contributors section to README
• fix: linting issues (#6033)
• Add CI pipeline for Node (#6022)
• security: Include a threat model (#6026)
• feat: add CodeQL (#6032)
• docs: add an IRP (#6028)
• feat: add scorecard reporting (#6030)
• docs: add security escalation policy (#6025)
• ci: add pipeline to run tests on browsers (#6021)
• ci: add ci pipeline for documentation (#6020)
• add security.md from afcd5bc (#5946)
• Bump to v4.17.21
• Improve performance of `toNumber`, `trim` and `trimEnd` on large input strings
• Prevent command injection through `_.template`'s `variable` option
• Bump to v4.17.20.
• Documentation fixes.
• test.js: Remove trailing comma.
• Temporarily use a custom fork of `lodash-cli`.
• Re-enable Travis tests on `4.17` branch.
• Remove `/npm-package`.

✳️ duti (0.15.2 → 0.15.3) · Repo · Changelog

Release Notes

0.15.3 (from changelog)

• Update all mentions of futil-js to futil

Does any of this look wrong? Please let us know.

↗️ core-js (indirect, 2.6.11 → 2.6.12) · Repo · Changelog

Release Notes

2.6.12

• Added code points / code units explicit feature detection in String#at for preventing breakage code which use obsolete String#at proposal polyfill
• Added OPEN_SOURCE_CONTRIBUTOR detection in postinstall
• Added Drone CI detection in postinstall

Does any of this look wrong? Please let us know.

↗️ regenerator-runtime (indirect, 0.10.5 → 0.13.11) · Repo

Sorry, we couldn't find anything useful about this release.

↗️ underscore.string (indirect, 3.3.5 → 3.3.6) · Repo · Changelog

Release Notes

3.3.6 (from changelog)

• Rebuild all assets for the release packages

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by 7 commits:

• fixup! Prepare for 3.3.6
• Prepare for 3.3.6
• Compile dist
• Bump version in manifests to current
• Add lock file and pin node.js
• Disable broken eslint rules for now
• Update deps

🆕 @​babel/polyfill (added, 7.12.1)

🆕 futil (added, 1.76.4)

🗑️ babel-polyfill (removed)

🗑️ babel-runtime (removed)

🗑️ futil-js (removed)

---

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

@​depfu rebase

Rebases against your default branch and redoes this update

@​depfu recreate

Recreates this PR, overwriting any edits that you've made to it

@​depfu merge

Merges this PR once your tests are passing and conflicts are resolved

@​depfu cancel merge

Cancels automatic merging of this PR

@​depfu close

Closes this PR and deletes the branch

@​depfu reopen

Restores the branch and reopens this PR (if it's closed)

@​depfu pause

Ignores all future updates for this dependency and closes this PR

@​depfu pause [minor|major]

Ignores all future minor/major updates for this dependency and closes this PR

@​depfu resume

Future versions of this dependency will create PRs again (leaves this PR as is)