[Snyk] Upgrade mongodb from 3.1.8 to 6.5.0 #13
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Snyk has created this PR to upgrade mongodb from 3.1.8 to 6.5.0. See this package in npm: mongodb See this project in Snyk: https://app.snyk.io/org/baby636/project/fefe9db8-be6b-42fb-b0e1-4bb92c24795c?utm_source=github&utm_medium=referral&page=upgrade-pr
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR was automatically created by Snyk using the credentials of a real user.
Snyk has created this PR to upgrade mongodb from 3.1.8 to 6.5.0.
ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.
Warning: This is a major version upgrade, and may be a breaking change.
The recommended version is 178 versions ahead of your current version.
The recommended version was released 2 months ago, on 2024-03-11.
The recommended version fixes:
SNYK-JS-LODASH-608086
Why? Proof of Concept exploit, CVSS 5.3
SNYK-JS-LODASH-6139239
Why? Proof of Concept exploit, CVSS 5.3
SNYK-JS-LODASHTEMPLATE-1088054
Why? Proof of Concept exploit, CVSS 5.3
SNYK-JS-MICROMATCH-6838728
Why? Proof of Concept exploit, CVSS 5.3
SNYK-JS-BSON-6056525
Why? Proof of Concept exploit, CVSS 5.3
SNYK-JS-DECODEURICOMPONENT-3149970
Why? Proof of Concept exploit, CVSS 5.3
SNYK-JS-ACORN-559469
Why? Proof of Concept exploit, CVSS 5.3
SNYK-JS-AJV-584908
Why? Proof of Concept exploit, CVSS 5.3
SNYK-JS-BL-608877
Why? Proof of Concept exploit, CVSS 5.3
SNYK-JS-ELLIPTIC-571484
Why? Proof of Concept exploit, CVSS 5.3
SNYK-JS-BRACES-6838727
Why? Proof of Concept exploit, CVSS 5.3
SNYK-JS-BSON-561052
Why? Proof of Concept exploit, CVSS 5.3
SNYK-JS-SEMVER-3247795
Why? Proof of Concept exploit, CVSS 5.3
SNYK-JS-URLREGEX-569472
Why? Proof of Concept exploit, CVSS 5.3
SNYK-JS-PATHPARSE-1077067
Why? Proof of Concept exploit, CVSS 5.3
SNYK-JS-BABELTRAVERSE-5962462
Why? Proof of Concept exploit, CVSS 5.3
SNYK-JS-ESLINTUTILS-460220
Why? Proof of Concept exploit, CVSS 5.3
SNYK-JS-SIMPLEGET-2361683
Why? Proof of Concept exploit, CVSS 5.3
SNYK-JS-Y18N-1021887
Why? Proof of Concept exploit, CVSS 5.3
SNYK-JS-MONGODB-473855
Why? Proof of Concept exploit, CVSS 5.3
SNYK-JS-INI-1048974
Why? Proof of Concept exploit, CVSS 5.3
SNYK-JS-IP-6240864
Why? Proof of Concept exploit, CVSS 5.3
SNYK-JS-JSYAML-174129
Why? Proof of Concept exploit, CVSS 5.3
SNYK-JS-LODASH-1040724
Why? Proof of Concept exploit, CVSS 5.3
SNYK-JS-LODASH-450202
Why? Proof of Concept exploit, CVSS 5.3
SNYK-JS-LODASH-567746
Why? Proof of Concept exploit, CVSS 5.3
SNYK-JS-GLOBPARENT-1016905
Why? Proof of Concept exploit, CVSS 5.3
SNYK-JS-GLOBPARENT-1016905
Why? Proof of Concept exploit, CVSS 5.3
SNYK-JS-DECOMPRESS-557358
Why? Proof of Concept exploit, CVSS 5.3
SNYK-JS-DECOMPRESS-557358
Why? Proof of Concept exploit, CVSS 5.3
SNYK-JS-DOTPROP-543489
Why? Proof of Concept exploit, CVSS 5.3
SNYK-JS-ELLIPTIC-1064899
Why? Proof of Concept exploit, CVSS 5.3
SNYK-JS-ELLIPTIC-511941
Why? Proof of Concept exploit, CVSS 5.3
SNYK-JS-BROWSERSLIST-1090194
Why? Proof of Concept exploit, CVSS 5.3
SNYK-JS-YARGSPARSER-560381
Why? Proof of Concept exploit, CVSS 5.3
npm:tunnel-agent:20170305
Why? Proof of Concept exploit, CVSS 5.3
SNYK-JS-MINIMATCH-3050818
Why? Proof of Concept exploit, CVSS 5.3
SNYK-JS-MINIMIST-559764
Why? Proof of Concept exploit, CVSS 5.3
SNYK-JS-MINIMIST-559764
Why? Proof of Concept exploit, CVSS 5.3
SNYK-JS-JSON5-3182856
Why? Proof of Concept exploit, CVSS 5.3
SNYK-JS-JSYAML-173999
Why? Proof of Concept exploit, CVSS 5.3
SNYK-JS-LODASH-1018905
Why? Proof of Concept exploit, CVSS 5.3
npm:braces:20180219
Why? Proof of Concept exploit, CVSS 5.3
npm:debug:20170905
Why? Proof of Concept exploit, CVSS 5.3
npm:debug:20170905
Why? Proof of Concept exploit, CVSS 5.3
SNYK-JS-MINIMIST-2429795
Why? Proof of Concept exploit, CVSS 5.3
SNYK-JS-MINIMIST-2429795
Why? Proof of Concept exploit, CVSS 5.3
SNYK-JS-KINDOF-537849
Why? Proof of Concept exploit, CVSS 5.3
(*) Note that the real score may have changed since the PR was raised.
Release notes
Package name: mongodb
6.5.0 (2024-03-11)
The MongoDB Node.js team is pleased to announce version 6.5.0 of the
mongodbpackage!Release Notes
Bulk Write Operations Generate Ids using
pkFactoryWhen performing inserts, the driver automatically generates
_ids for each document if there is no_idpresent. By default, the driver generatesObjectIds. An option,pkFactory, can be used to configure the driver to generate_ids that are not object ids.For a long time, only
Collection.insertandCollection.insertManyactually used thepkFactory, if configured. Notably,Collection.bulkWrite(),Collection.initializeOrderedBulkOp()andCollection.initializeOrderedBulkOp()always generatedObjectIds, regardless of what was configured on collection.The driver always generates
_ids for inserted documents using thepkFactory.Caution
If you are using a
pkFactoryand performing bulk writes, you may have inserted data into your database that does not have_ids generated by thepkFactory.Fixed applying read preference to commands depending on topology
When connecting to a secondary in a replica set with a direct connection, if a read operation is performed, the driver attaches a read preference of
primaryPreferredto the command.Fixed memory leak in Connection layer
The Connection class has recently been refactored to operate on our socket operations using promises. An oversight how we made async network operations interruptible made new promises for every operation. We've simplified the approach and corrected the leak.
Query SRV and TXT records in parallel
When connecting using a convenient SRV connection string (
mongodb+srv://) hostnames are obtained from an SRV dns lookup and some configuration options are obtained from a TXT dns query. Those DNS operations are now performed in parallel to reduce first-time connection latency.Container and Kubernetes Awareness
The Node.js driver now keeps track of container metadata in the
client.env.containerfield of the handshake document.If space allows, the following metadata will be included in
client.env.container:Note: If neither Kubernetes nor Docker is present,
client.envwill not have thecontainerproperty.Add property
errorResponseto MongoServerErrorThe MongoServer error maps keys from the error document returned by the server on to itself. There are some use cases where the original error document is desirable to obtain in isolation. So now, the
mongoServerError.errorResponseproperty stores a reference to the error document returned by the server.Deprecated unused
CloseOptionsinterfaceThe
CloseOptionsinterface was unintentionally made public and was only intended for use in the driver's internals. Due to recent refactoring (NODE-5915), this interface is no longer used in the driver. Since it was marked public, out of an abundance of caution we will not be removing it outside of a major version, but we have deprecated it and will be removing it in the next major version.Features
Bug Fixes
CERT_HAS_EXPIRED(#4014) (057c223)Connectionclass (#4022) (69de253)Performance Improvements
Documentation
We invite you to try the
mongodblibrary immediately, and report any issues to the NODE project.6.4.0 (2024-02-29)
The MongoDB Node.js team is pleased to announce version 6.4.0 of the
mongodbpackage!Release Notes
Server selection will use a different Mongos on retry
When retrying reads or writes on a sharded cluster, the driver will attempt to select a different mongos for the retry if multiple are present. This should heuristically avoid encountering the original error that caused the need to retry the operation.
Caching AWS credentials provider per client
Instead of creating a new AWS provider for each authentication, we cache the AWS credentials provider per client to prevent overwhelming the auth endpoint and ensure that cached credentials are not shared with other clients.
BSON upgraded to
^6.4.0BSON has had a number of performance increases in the last two releases (6.3.0 and 6.4.0). Small basic latin (ASCII) only strings, small memory allocations (ObjectId and Decimal128) and numeric parsing operations (int32, doubles, and longs) have all had optimizations applied to them.
For details check out the release notes here: BSON 6.3.0 and BSON 6.4.0 🐎
ExceededTimeLimit was made a retryable reads error
Read operations will be retried after receiving an error with the
ExceededTimeLimitlabel.Fixed unresolved request issue in KMS requester
Internal to the field-level encryption machinery is a helper that opens a TLS socket to the KMS provider endpoint and submits a KMS request. The code neglected to add a
'close'event listener to the socket, which had the potential to improperly leave the promise pending indefinitely if no error was encountered.The base64 padding is now preserved in the saslContinue command
The authentication was rejected by the saslContinue command from mongosh due to missing "=" padding from the client. We fixed the way we parse payload to preserve trailing "="s.
countDocumentsnow types the filter using the collection SchemaPreviously,
countDocumentshad a weakly typedDocumenttype for the filter allowing any JS object as input. The filter is now typed asFilter<Schema>to enable autocompletion, and, hopefully, catch minor bugs.Thank you to @ pashok88895 for contributing to this improvement.
The type error with
$addToSetinbulkWritewas fixedPreviously the following code sample would show a type error:
It happened because the driver's
Documenttype falls back toany, and internally we could not distinguish whether or not this assignment was intentional and should be allowed.After this change, users can extend their types from
Document/any, or use properties ofanytype and we skip the$addToSetvalidation in those cases.Fixed heartbeat duration including socket creation
The ServerHeartbeatSucceeded and ServerHeartbeatFailed event have a duration property that represents the time it took to perform the
hellohandshake with MongoDB. The Monitor responsible for issuing heartbeats mistakenly included the time it took to create the socket in this field, which inflates the value with the time it takes to perform a DNS lookup, TCP, and TLS handshakes.Errors on cursor transform streams are now properly propagated.
These were previously swallowed and now will be emitted on the
errorevent:The AWS token is now optional
Users may provide an
AWS_SESSION_TOKENas a client option or AWS configuration in addition to a username and password. But if the token is not provided, the driver won't throw an exception and let AWS SDK handle the request.Features
^6.4.0(#4007) (90f2f70)^6.3.0(#3983) (9401d09)Bug Fixes
Performance Improvements
Documentation
We invite you to try the
mongodblibrary immediately, and report any issues to the NODE project.6.3.0 (2023-11-15)
The MongoDB Node.js team is pleased to announce version 6.3.0 of the
mongodbpackage!Release Notes
New client option
serverMonitoringModeFor users that want to control the behaviour of the monitoring connection between each node in the topology, a new option,
serverMonitoringMode, has been added. This defaults toautobut can be forced into a specific mode by providing a value ofpollorstream. When the setting isautothe monitoring mode will be determined by the environment the driver is running in, specifically, FaaS environments prefer "polling" mode and all others prefer "streaming".A polling monitor periodically issues a
hellocommand to the node at an interval ofheartbeatFrequencyMS. A streaming monitor sends an initialhelloand then will automatically get a response from the Node when a change in server configuration occurs or at a maximum time ofheartbeatFrequencyMS. The value of that option defaults to 10000 milliseconds.This new option can be provided in the connection string or as an option to the
MongoClient.new MongoClient('mongodb://127.0.0.1:27017/?serverMonitoringMode=stream');
// In the options
new MongoClient('mongodb://127.0.0.1:27017/', { serverMonitoringMode: 'stream' });
Fix connection leak when
serverApiis enabledWhen enabling
serverApithe driver's RTT measurement logic (used to determine the closest node) still sent the legacy hello command "isMaster" causing the server to return an error. Unfortunately, the error handling logic did not correctly destroy the socket which would cause a leak.Both sending the correct hello command and the error handling connection clean-up logic are fixed in this change.
GridFS fields deprecated
The GridFS
contentTypeandaliasesoptions are deprecated. According to the GridFS spec, applications wishing to storecontentTypeandaliasesshould add a corresponding field to themetadatadocument instead.Remove deprecation warning about punycode
The
mongodb-connection-string-urlpackage which parses connection strings relied on Node's punycode module, the package now imports the community package removing the deprecation warning on Node.js 20+.Features
Bug Fixes
Documentation
We invite you to try the
mongodblibrary immediately and report any issues to the NODE project.6.2.0 (2023-10-19)
The MongoDB Node.js team is pleased to announce version 6.2.0 of the
mongodbpackage!Release Notes
Updated to BSON 6.2.0
BSON now prints in full color! 🌈 🚀
See our release notes for BSON 6.2.0 here for more examples!
insertedIdsin bulk write now contain only successful insertionsPrior to this fix, the bulk write error's
result.insertedIdsproperty contained the_idof each attempted insert in a bulk operation.Now, when a
bulkwrite()or aninsertMany()operation rejects one or more inserts, throwing an error, the error'sresult.insertedIdsproperty will only contain the_idfields of successfully inserted documents.Fixed edge case leak in
findOne()When running a
findOneagainst a time series collection, the driver left the implicit session for the cursor un-ended due to the way the server returns the resulting cursor information. Now the cursor will always be cleaned up regardless of the outcome of the find operation.Removed client-side collection and database name validation
Database and collection name checking will now be in sync with the MongoDB server's naming restrictions. Specifically, users can now create collections that start or end with the '.' character.
Features
awaitedfield to SDAM heartbeat events (#3895) (b50aadc)Bug Fixes
Documentation
We invite you to try the
mongodblibrary immediately, and report any issues to the NODE project.5.9.2 (2023-11-16)
The MongoDB Node.js team is pleased to announce version 5.9.2 of the
mongodbpackage!Release Notes
Fix connection leak when serverApi is enabled
When enabling serverApi the driver's RTT mesurment logic (used to determine the closest node) still sent the legacy hello command "isMaster" causing the server to return an error. Unfortunately, the error handling logic did not correctly destroy the socket which would cause a leak.
Both sending the correct hello command and the error handling connection clean up logic are fixed in this change.
Bug Fixes
Documentation
We invite you to try the
mongodblibrary ...