🚨 [security] Update mongoose 5.9.27 → 5.13.22 (minor) #138

depfu · 2024-04-23T00:06:46Z

🚨 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.9.27 → 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.

↗️ bson (indirect, 1.1.4 → 1.1.6) · Repo · Changelog

Release Notes

1.1.6

The MongoDB Node.js team is pleased to announce version 1.1.6 of the bson module!

The BSON library was written prior to the invention of the BigInt type in Javascript ecosystem.
As a result the library was not able to serialize the type properly and silently failed to correctly maintain the bigint value.
With this update, the library will now throw an error if it detects a bigint value.
However, we've also added to/fromBigInt helper methods to the long class, please note that numbers will be clamped to int64 bit width.
const bytes = BSON.serialize({ myBigNumber: Long.fromBigInt(23n) })
const doc = BSON.deserialize(bytes)
doc.myBigNumber.toBigInt() === 23n // true
New Feature

[NODE-2378] - Return error when failing to serialize bigint type and add Long class helpers

Documentation

API: https://github.com/mongodb/js-bson#readme

Changelog: https://github.com/mongodb/js-bson/blob/master/HISTORY.md#change-log

We invite you to try the bson library immediately, and report any issues to the NODE project.
Thanks very much to all the community members who contributed to this release!

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

Commits

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

↗️ denque (indirect, 1.4.1 → 1.5.1) · Repo · Changelog

Release Notes

1.5.1 (from changelog)

perf: minor performance tweak when growing queue size (#29)

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

Commits

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

↗️ kareem (indirect, 2.3.1 → 2.3.2) · Repo · Changelog

Commits

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

↗️ mongodb (indirect, 3.5.10 → 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.7.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()

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

Commits

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

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

Security Advisories 🚨

🚨 Code Injection in mquery

lib/utils.js in mquery before 3.2.3 allows a pollution attack because a special property (e.g., proto) can be copied during a merge or clone operation.

Release Notes

3.2.5 (from changelog)

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

3.2.4 (from changelog)

fix(utils): make clone() only copy own properties Automattic/mongoose#9876

3.2.3 (from changelog)

fix(utils): avoid copying special properties like __proto__ when merging and cloning

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

Commits

See the full diff on Github. The new version differs by 12 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.

🆕 @types/bson (added, 4.0.5)

🆕 @types/mongodb (added, 3.6.20)

🆕 @types/node (added, 20.12.7)

🆕 optional-require (added, 1.0.3)

🆕 require-at (added, 1.0.6)

🆕 undici-types (added, 5.26.5)

🗑️ require_optional (removed)

🗑️ resolve-from (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)

Update mongoose to version 5.13.22

320104c

depfu bot added the depfu label Apr 23, 2024

depfu bot mentioned this pull request Apr 23, 2024

🚨 [security] Update mongoose 5.9.27 → 5.13.20 (minor) #131

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

🚨 [security] Update mongoose 5.9.27 → 5.13.22 (minor) #138

🚨 [security] Update mongoose 5.9.27 → 5.13.22 (minor) #138

depfu bot commented Apr 23, 2024

🚨 [security] Update mongoose 5.9.27 → 5.13.22 (minor) #138

Are you sure you want to change the base?

🚨 [security] Update mongoose 5.9.27 → 5.13.22 (minor) #138

Conversation

depfu bot commented Apr 23, 2024

What changed?

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

🚨 Mongoose Prototype Pollution vulnerability

🚨 Mongoose Vulnerable to Prototype Pollution in Schema Object

Description

Proof of Concept

Impact

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

↗️ bson (indirect, 1.1.4 → 1.1.6) · Repo · Changelog

1.1.6

New Feature

Documentation

↗️ denque (indirect, 1.4.1 → 1.5.1) · Repo · Changelog

1.5.1 (from changelog)

↗️ kareem (indirect, 2.3.1 → 2.3.2) · Repo · Changelog

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

↗️ mpath (indirect, 0.7.0 → 0.8.4) · Repo · Changelog

🚨 Type confusion in mpath

0.8.4 (from changelog)

0.8.3 (from changelog)

0.8.2 (from changelog)

0.8.1 (from changelog)

0.8.0 (from changelog)

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

🚨 Code Injection in mquery

3.2.5 (from changelog)

3.2.4 (from changelog)

3.2.3 (from changelog)

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

12.0.0 (from changelog)

11.0.0 (from changelog)

10.0.0 (from changelog)

9.0.0 (from changelog)

8.5.1 (from changelog)

8.5.0 (from changelog)

8.4.0 (from changelog)

8.3.2 (from changelog)

8.0.0 (from changelog)

🆕 @​types/bson (added, 4.0.5)

🆕 @​types/mongodb (added, 3.6.20)

🆕 @​types/node (added, 20.12.7)

🆕 optional-require (added, 1.0.3)

🆕 require-at (added, 1.0.6)

🆕 undici-types (added, 5.26.5)

🗑️ require_optional (removed)

🗑️ resolve-from (removed)

🆕 @types/bson (added, 4.0.5)

🆕 @types/mongodb (added, 3.6.20)

🆕 @types/node (added, 20.12.7)