🚨 [security] Upgrade mpath: 0.6.0 → 0.8.4 (major)

[depfu]

---

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 upgrade. Please take a good look at what changed and the test results before merging this pull request.

What changed?

✳️ mpath (0.6.0 → 0.8.4) · Repo · Changelog

Security Advisories 🚨

🚨 Type confusion in mpath

This affects the package mpath before 0.8.4. A type confusion vulnerability can lead to a bypass of CVE-2018-16490. In particular, the condition ignoreProperties.indexOf(parts[i]) !== -1 returns -1 if parts[i] is ['proto']. This is because the method that has been called if the input is an array is Array.prototype.indexOf() and not String.prototype.indexOf(). They behave differently depending on the type of the input.

Release Notes

0.8.4 (from changelog)

• fix: throw error if parts contains an element that isn't a string or number #13

0.8.3 (from changelog)

• fix: use var instead of let/const for Node.js 4.x support

0.8.2 (from changelog)

• fix(stringToParts): fall back to legacy treatment for square brackets if square brackets contents aren't a number Automattic/mongoose#9640
• chore: add eslint

0.8.1 (from changelog)

• fix(stringToParts): handle empty string and trailing dot the same way that split() does for backwards compat

0.8.0 (from changelog)

• feat: support square bracket indexing for get(), set(), has(), and unset()

0.7.0 (from changelog)

• BREAKING CHANGE: remove component.json #9 AlexeyGrigorievBoost

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

Commits

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

• chore: release 0.8.4
• fix: throw error if `parts` contains an element that isn't a string or number
• chore: add basic SECURITY.md file
• chore: release 0.8.3
• fix: use var instead of let/const for Node.js 4.x support
• chore: release 0.8.2
• chore: add lint
• fix(stringToParts): fall back to legacy treatment for square brackets if square brackets contents aren't a number
• chore: release 0.8.1
• fix(stringToParts): handle empty string and trailing dot the same way that `split()` does for backwards compat
• chore: release 0.8.0
• feat: support square bracket indexing for `get()`, `set()`, `has()`, and `unset()`
• chore: release 0.7.0
• Merge pull request #9 from AlexeyGrigorievBoost/component_json_removal
• Component.json removal

🆕 rimraf (added, 3.0.2)

---

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 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)