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.

Sign up for GitHub

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

Jump to bottom

🚨 [security] Update mongoose 5.11.8 → 5.13.22 (minor) #71

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

🚨 [security] Update mongoose 5.11.8 → 5.13.22 (minor) #71

wants to merge 1 commit into from

Conversation

depfu[bot]
Copy link

@depfu depfu bot commented Apr 23, 2024

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?

✳️ mongoose (5.11.8 → 5.13.22) · Repo · Changelog

Security Advisories 🚨

🚨 Mongoose Prototype Pollution vulnerability

Prototype Pollution in GitHub repository automattic/mongoose prior to 7.3.3, 6.11.3, and 5.13.20.

🚨 Mongoose Vulnerable to Prototype Pollution in Schema Object

Description

Mongoose is a MongoDB object modeling tool designed to work in an asynchronous environment.

Affected versions of this package are vulnerable to Prototype Pollution. The Schema.path() function is vulnerable to prototype pollution when setting the schema object. This vulnerability allows modification of the Object prototype and could be manipulated into a Denial of Service (DoS) attack.

Proof of Concept

// poc.js
const mongoose = require('mongoose');
const schema = new mongoose.Schema();

malicious_payload = 'proto.toString'


schema.path(malicious_payload, [String])


x = {}

console.log(x.toString()) // crashed (Denial of service (DoS) attack)

Impact

This vulnerability can be manipulated to exploit other types of attacks, such as Denial of service (DoS), Remote Code Execution, or Property Injection.

🚨 automattic/mongoose vulnerable to Prototype pollution via Schema.path

Mongoose is a MongoDB object modeling tool designed to work in an asynchronous environment. Affected versions of this package are vulnerable to Prototype Pollution. The Schema.path() function is vulnerable to prototype pollution when setting the schema object. This vulnerability allows modification of the Object prototype and could be manipulated into a Denial of Service (DoS) attack.

Release Notes

Too many releases to show here. View the full release notes.

✳️ @​sapphire/framework (1.0.0-alpha.5 → 1.0.2) · Repo · Changelog

Release Notes

1.0.2

1.0.2 (2021-05-02)

Bug Fixes

  • drop the www. from the SapphireJS URL (e9ed4e8)
  • update all the SapphireJS URLs from .com to .dev (4d0c8ea)

1.0.1

1.0.1 (2021-04-21)

Bug Fixes

  • dependencies: update in semver scope dependencies (ca9a2c1)
  • change all Sapphire URLs from "project"->"community" & use our domain where applicable 👨‍🌾🚜 (#192) (650260e)

1.0.0

1.0.0 (2021-03-16)

Features

Bug Fixes

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

Commits

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

✳️ @​sapphire/pieces (1.2.1 → 1.2.5) · Repo · Changelog

Release Notes

1.2.5

1.2.5 (2021-05-02)

Bug Fixes

  • drop the www. from the SapphireJS URL (e87e50e)
  • update all the SapphireJS URLs from .com to .dev (0a9c1b3)

1.2.4

1.2.4 (2021-04-21)

Bug Fixes

  • change all Sapphire URLs from "project"->"community" & use our domain where applicable 👨‍🌾🚜 (#69) (fc55625)

1.2.3

1.2.3 (2021-03-16)

Bug Fixes

  • add tslib as dependency (a7d9695)
  • update packages, ship with tslib (f7b76c2)

1.2.2

1.2.2 (2021-02-12)

Bug Fixes

  • docs: tsdoc has been improved (c9ee146)

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

Commits

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

↗️ @​sapphire/discord.js-utilities (indirect, 1.4.0 → 1.6.0) · Repo · Changelog

Release Notes

Too many releases to show here. View the full release notes.

↗️ @​sapphire/ratelimits (indirect, 1.1.4 → 1.2.5) · Repo · Changelog

Release Notes

1.2.5 (from changelog)

Note: Version bump only for package @sapphire/ratelimits

1.2.3 (from changelog)

Bug Fixes

  • remove peer deps, update dev deps, update READMEs (#124) (67256ed)

1.2.2 (from changelog)

Bug Fixes

  • ratelimits: mark package as side effect free (22334e1)

1.2.1 (from changelog)

Bug Fixes

  • drop the www. from the SapphireJS URL (494d89f)
  • update all the SapphireJS URLs from .com to .dev (f59b46d)

1.2.0 (from changelog)

Features

1.1.8 (from changelog)

Bug Fixes

  • change all Sapphire URLs from "project"->"community" & use our domain where applicable 👨‍🌾🚜 (#102) (835b408)

1.1.7 (from changelog)

Note: Version bump only for package @sapphire/ratelimits

1.1.6 (from changelog)

Bug Fixes

1.1.5 (from changelog)

Note: Version bump only for package @sapphire/ratelimits

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

↗️ @​sapphire/utilities (indirect, 1.4.4 → 1.7.0) · Repo · Changelog

Release Notes

1.7.0 (from changelog)

Features

  • utilities: add 3 new helper methods (4ebcd43)

1.6.1 (from changelog)

Note: Version bump only for package @sapphire/utilities

1.6.0 (from changelog)

Features

  • utilities: update utilities with more stuff (#122) (5dfb668)

1.5.3 (from changelog)

Bug Fixes

  • remove peer deps, update dev deps, update READMEs (#124) (67256ed)

1.5.2 (from changelog)

Bug Fixes

  • utilities: mark package as side effect free (73cbabd)

1.5.1 (from changelog)

Bug Fixes

  • drop the www. from the SapphireJS URL (494d89f)
  • update all the SapphireJS URLs from .com to .dev (f59b46d)

1.5.0 (from changelog)

Bug Fixes

  • utilities: resolve lgtm error (eb5f4e6)

Features

1.4.8 (from changelog)

Bug Fixes

  • change all Sapphire URLs from "project"->"community" & use our domain where applicable 👨‍🌾🚜 (#102) (835b408)

1.4.7 (from changelog)

Note: Version bump only for package @sapphire/utilities

1.4.6 (from changelog)

Bug Fixes

1.4.5 (from changelog)

Note: Version bump only for package @sapphire/utilities

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

↗️ mongodb (indirect, 3.6.3 → 3.7.4) · Repo · Changelog

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ mpath (indirect, 0.8.1 → 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

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

Commits

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

↗️ mquery (indirect, 3.2.3 → 3.2.5) · Repo · Changelog

Release Notes

3.2.5 (from changelog)

  • fix(utils): make mergeClone() skip special properties like __proto__ #121 zpbrent

3.2.4 (from changelog)

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

Commits

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

↗️ sift (indirect, 7.0.1 → 13.5.2) · Repo · Changelog

Release Notes

12.0.0 (from changelog)

  • Fix bug where $elemMatch tested objects: e.g: sift({a: {$elemMatch: 1}})({ a: { b: 1}}). $elemMatch now expects arrays based on Mongodb syntax. E.g: sift({a: {$elemMatch: 1}})({ a: { b: 1}})

11.0.0 (from changelog)

  • new custom operations syntax (see API readme)
  • null & undefined are not treated equally (change has been added to keep spec as functionality as possible to MongoDB)
  • select option has been removed
  • compare option now expects boolean return value instead of an integer
  • nested queries are no-longer supported
  • expressions option is now operations
  • operations parameter now expects new operations API

10.0.0 (from changelog)

  • new custom operations syntax (see API readme)
  • null & undefined are not treated equally (change has been added to keep spec as functionality as possible to MongoDB)
  • select option is not supported anymore
  • compare option now expects boolean return value
  • nested queries are no-longer supported

9.0.0 (from changelog)

  • (behavior change) toJSON works for vanilla objects.

8.5.1 (from changelog)

  • Fix dependency vulnerability
  • Fix #158

8.5.0 (from changelog)

  • Added comparable option (fix #156)

8.4.0 (from changelog)

  • Added compare option (fix #155)

8.3.2 (from changelog)

  • Query properties now excpect exact object shape (based on #152). E.g: [{a: { b: 1}}, {a: { b: 1, c: 2}}]].filter(sift({ a: { b: 1} })) === [{a: {b: 1}], and [{a: 1, b: 1}, {a: 1}]].filter(sift({ a: 1 })) === [{a: 1, b: 1}, {a: 1}].

8.0.0 (from changelog)

  • DEPRECATED indexOf in favor of array.findIndex(sift(query))
  • second param is now options instead of select function. E.g: sift(query, { expressions: customExpressions, select: selectValue })
  • DEPRECATED sift(query, array). You must now use array.filter(sift(query))
  • Queries now expect exact object shape (based on #117). E.g: [{a: 1, b: 1}, {a: 1}]].filter(sift({ a: 1 })) === [{a: 1}]

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

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ tslib (indirect, 2.1.0 → 2.6.2) · Repo

Release Notes

2.6.2

What's Changed

Full Changelog: v2.6.1...v2.6.2

2.6.1

What's Changed

Full Changelog: 2.6.0...v2.6.1

2.6.0

What's Changed

Full Changelog: v2.5.3...2.6.0

2.5.3

What's Changed

Full Changelog: 2.5.2...v2.5.3

2.5.2

This release explicitly re-exports helpers to work around TypeScript's incomplete symbol resolution for tslib.

2.5.1

This release of tslib provides fixes for two issues.

First, it reverses the order of init hooks provided by decorators to correctly reflect proposed behavior.

Second, it corrects the exports field of tslib's package.json and provides accurate declaration files so that it may be consumed under the node16 and bundler settings for moduleResolution.

2.5.0

What's New

  • Fix asyncDelegator reporting done too early by @apendua in #187
  • Add support for TypeScript 5.0's __esDecorate and related helpers by @rbuckton in #193

Full Changelog: 2.4.1...2.5.0

2.4.1

This release contains fixes for early returns and throws invoked on generators.

2.4.0

This release includes the __classPrivateFieldIn helper as well as an update to __createBinding to reduce indirection between multiple re-exports.

2.3.1

This release updates the __spreadArray helper for TypeScript 4.4 to correctly operate on collections that are not "concat-spreadable" such as the DOM's NodeLists and HTMLCollections.

2.3.0

This release updates tslib to use TypeScript 4.4's upcoming __spreadArray helper which correctly preserves sparse array inputs (e.g. arrays containing "missing" elements like [1, 2, , 4]). This new version of __spreadArray is backwards-compatible and is often also faster. See #151 for more details.

2.2.0

This release supports TypeScript 4.3's new functionality for ECMAScript private methods and accessors, and private static class members.

It does so by expanding the scope of __classPrivateFieldGet and __classPrivateFieldSet. See #146 for more details.

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

Commits

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

🆕 discord-api-types (added, 0.36.3)

🆕 optional-require (added, 1.0.3)

🆕 require-at (added, 1.0.6)

Depfu Status

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)

@depfu depfu bot added the depfu label Apr 23, 2024
@depfu depfu bot requested a review from Nytelife26 April 23, 2024 00:08
@depfu depfu bot mentioned this pull request Apr 23, 2024
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@Nytelife26 Nytelife26 Awaiting requested review from Nytelife26

Assignees

@Nytelife26 Nytelife26

Labels
depfu
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

None yet
1 participant
@Nytelife26