🚨 [security] Update mongodb 3.6.6 → 3.6.12 (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?

✳️ mongodb (3.6.6 → 3.6.12) · Repo · Changelog

Security Advisories 🚨

🚨 MongoDB Driver may publish events containing authentication-related data

Some MongoDB Drivers may erroneously publish events containing authentication-related data to a command listener configured by an application. The published events may contain security-sensitive data when specific authentication-related commands are executed.

Without due care, an application may inadvertently expose this sensitive information, e.g., by writing it to a log file. This issue only arises if an application enables the command listener feature (this is not enabled by default).

This issue affects the MongoDB C Driver 1.0.0 prior to 1.17.7, MongoDB PHP Driver 1.0.0 prior to 1.9.2, MongoDB Swift Driver 1.0.0 prior to 1.1.1, MongoDB Node.js Driver 3.6 prior to 3.6.10, MongoDB Node.js Driver 4.0 prior to 4.17.0 and MongoDB Node.js Driver 5.0 prior to 5.8.0. This issue also affects users of the MongoDB C++ Driver dependent on the C driver 1.0.0 prior to 1.17.7 (C++ driver prior to 3.7.0).

Release Notes

3.6.12

The MongoDB Node.js team is pleased to announce version 3.6.12 of the mongodb package!

Bug Fixes

• NODE-3487: check for nullish aws mechanism property (#2957) (5902b4c)
• NODE-3528: add support for snappy v7 (#2947) (54f5c2d)

Documentation

• Reference: https://docs.mongodb.com/drivers/node/current/
• API: https://mongodb.github.io/node-mongodb-native/3.6/api/
• Changelog: https://github.com/mongodb/node-mongodb-native/blob/v3.6.12/HISTORY.md

We invite you to try the mongodb library immediately, and report any issues to the NODE project.

3.6.10

The MongoDB Node.js team is pleased to announce version 3.6.10 of the mongodb package!

Release Highlights

This patch addresses a few bugs listed below. Notably the bsonRegExp option is now respected by the underlying BSON library, you can use this to decode regular expressions that contain syntax not permitted in native JS RegExp objects. Take a look at this example:

await collection.insertOne({ a: new BSONRegExp('(?-i)AA_') })
await collection.findOne({ a: new BSONRegExp('(?-i)AA_') }, { bsonRegExp: true })
// { _id: ObjectId,  a: BSONRegExp { pattern: '(?-i)AA_', options: '' } }

Also there was an issue with Cursor.forEach where user defined forEach callbacks that throw errors incorrectly handled catching errors. Take a look at the comments in this example:

collection.find({}).forEach(doc => {
    if(doc.bad) throw new Error('bad document!');
}).catch(error => {
    // now this is called! and error is `bad document!`
})
// before this fix the `bad document!` error would be thrown synchronously
// and have to be caught with try catch out here

Bug Fixes

• NODE-2035: Exceptions thrown from awaited cursor forEach do not propagate (#2852) (a917dfa)
• NODE-3150: added bsonRegExp option for v3.6 (#2843) (e4a9a57)
• NODE-3358: Command monitoring objects hold internal state references (#2858) (750760c)
• NODE-3380: perform retryable write checks against server (#2861) (621677a)
• NODE-3397: report more helpful error with unsupported authMechanism in initial handshake (#2876) (3ce148d)

Documentation

• Reference: https://docs.mongodb.com/drivers/node/current/
• API: http://mongodb.github.io/node-mongodb-native/3.6/api
• Changelog: https://github.com/mongodb/node-mongodb-native/blob/3.6/HISTORY.md

We invite you to try the mongodb package immediately, and report any issues to the NODE project.

3.6.9

The MongoDB Node.js team is pleased to announce version 3.6.9 of the driver!

Release Highlights

This release fixes a major performance bug in bulk write operations, which was inadvertently introduced by an incomplete code change in the previous release. The bug resulted in redundant array iterations and caused exponential increases in bulk operation completion times. Thank you Jan Schwalbe for bringing this to our attention!

Bug Fixes

• NODE-3309: remove redundant iteration of bulk write result (#2815) (fac9610)
• NODE-3234: fix url parsing for a mongodb+srv url that has commas in the database name (#2789) (58c4e69)

Documentation

• Reference: https://docs.mongodb.com/drivers/node/current/
• API: http://mongodb.github.io/node-mongodb-native/3.6/api
• Changelog: https://github.com/mongodb/node-mongodb-native/blob/3.6/HISTORY.md

We invite you to try the mongodb package immediately, and report any issues to the NODE project.

3.6.8

The MongoDB Node.js team is pleased to announce version 3.6.8 of the mongodb package!

Release Highlights

Thanks to the quick adoption of the previous new patch by the mongoose package (Automattic/mongoose#10265) a small bug was identified when connections to mongodb would timeout causing unnecessary clean up operations to run. Thank you @vkarpov15!

Bug Fixes

• NODE-3305: undo flipping of beforeHandshake flag for timeout errors (#2813) (6e3bab3)

Documentation

• Reference: https://docs.mongodb.com/drivers/node/current/
• API: http://mongodb.github.io/node-mongodb-native/3.6/api
• Changelog: https://github.com/mongodb/node-mongodb-native/blob/3.6/HISTORY.md

We invite you to try the mongodb package immediately, and report any issues to the NODE project.

3.6.7

The MongoDB Node.js team is pleased to announce version 3.6.7 of the driver

Release Highlights

This patch addresses a number of bug fixes. Notably, there was an interesting javascript related issue with sorting documents. It only impacts users using numerical keys in their documents.

> { a: 'asc', [23]: 'asc' }
{ [23]: 'asc', a: 'asc' } // numbers come first

In javascript, numerical keys are always iterated first when looping over the keys of an object followed by the chronological specification of each string key. This effectively changes the ordering of a sort document sent to mongodb. However our driver does accept sort specification in a variety of ways and one way to avoid this problem is passing an array of tuples:

[['a', 'asc'], ['23', 'asc']]

This ensures that mongodb is sent the 'a' key as the first sort key and '23' as the second.

Bug Fixes

• NODE-3159: removing incorrect apm docs (#2793) (971259a)
• NODE-3173: Preserve sort key order for numeric string keys (#2790) (730f43a)
• NODE-3176: handle errors from MessageStream (#2774) (f1afcc4)
• NODE-3192: check clusterTime is defined before access (#2806) (6ceace6)
• NODE-3252: state transistion from DISCONNECTED (#2807) (5d8f649)
• NODE-3219: topology no longer causes close event (#2791) (16e7064)
• invalid case on writeconcern makes skip check fail (#2773) (b1363c2)

Documentation

• Reference: http://mongodb.github.io/node-mongodb-native/3.6
• API: http://mongodb.github.io/node-mongodb-native/3.6/api
• Changelog: https://github.com/mongodb/node-mongodb-native/blob/3.6/HISTORY.md

We invite you to try the driver 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 44 commits:

• chore(release): 3.6.12
• chore(NODE-3408): test against mongod 5.0 (#2958)
• fix(NODE-3487): check for nullish aws mechanism property (#2957)
• fix(NODE-3528): add support for snappy v7 (#2947)
• docs(NODE-3481): deprecate unref (#2936)
• chore(release): 3.6.11
• fix(NODE-3199): unable to bundle driver due to uncaught require (#2903)
• fix(NODE-1843): bulk operations ignoring provided sessions [PORT] (#2898)
• chore(NODE-3316): add author info and update bug url in package.json (#2887)
• test(NODE-3381): command monitoring redaction tests (#2873)
• chore(release): 3.6.10
• refactor(NODE-3324): bump max wire version to 13 (#2875)
• fix(NODE-3397): report more helpful error with unsupported authMechanism in initial handshake (#2876)
• test(NODE-3307): unified runner does not assert identical keys (#2867)
• fix(NODE-3380): perform retryable write checks against server (#2861)
• fix(NODE-3150): added bsonRegExp option for v3.6 (#2843)
• fix(NODE-3358): Command monitoring objects hold internal state references (#2858)
• fix(NODE-2035): Exceptions thrown from awaited cursor forEach do not propagate (#2852)
• refactor(NODE-3356): Update command monitoring logging (#2853)
• test(NODE-2856): ensure defaultTransactionOptions get used from session (#2845)
• fix(NODE-3356): update redaction logic for command monitoring events (#2847)
• test(NODE-3357): extend timeout for atlas connectivity (#2846)
• test(NODE-3288): sync command-monitoring spec tests to 3.6 (#2838)
• docs: change links to use https (#2836)
• refactor(NODE-2752): deprecate strict option for Db.collection (#2819)
• chore(release): 3.6.9
• fix(NODE-3309): remove redundant iteration of bulk write result (#2815)
• fix: fix url parsing for a mongodb+srv url that has commas in the database name (#2789)
• chore(release): 3.6.8
• fix(cmap): undo flipping of `beforeHandshake` flag for timeout errors (#2813)
• chore(release): 3.6.7
• fix(NODE-3192): check clusterTime is defined before access (#2806)
• test(NODE-3187): port unified test runner (#2783)
• fix(NODE-3252): state transistion from DISCONNECTED (#2807)
• refactor(NODE-1812): Deprecate returnOriginal in favor of returnDocument (#2808)
• refactor: deprecate remove, removeOne, insertMany bulk operations (#2797)
• chore(NODE-3198): bump optional-require for yarn v2 pnp support (#2781)
• fix(NODE-3173): Preserve sort key order for numeric string keys (#2790)
• fix(sdam): topology no longer causes close event (#2791)
• fix(docs): removing incorrect apm docs (#2793)
• Remove callback from Collection.initializeOrderedBulkOp() (#2782)
• chore(NODE-3186): ensure all aws tests are run (#2776)
• fix(NODE-3176): handle errors from MessageStream (#2774)
• fix: invalid case on writeconcern makes skip check fail (#2773)

---

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]

Sorry, but the merge failed with:

Waiting on code owner review from Skn0tt. You're not authorized to push to this branch. Visit https://docs.github.com/articles/about-protected-branches/ for more information.

[depfu]

Sorry, but the merge failed with:

Waiting on code owner review from Skn0tt. You're not authorized to push to this branch. Visit https://docs.github.com/articles/about-protected-branches/ for more information.